Oh, I get it now (and somehow makes sense)...
Thank you for your clarification, really helps!
A.

I'm afraid you don't get my point. To encrypt or decrypt a string using AES (e.g. CBC), you need the following: -An initialization vector (IV) , which is a random string you generate before encryption (which is sent along with the encrypted payload) -An encryption key -The payload (text) to be encry...

My point was that usually the IV is sent along with the encrypted payload, so it will be in an output string at some point. As its value is changed by the function, it means that the output will no longer be valid as the IV won't match anymore the encrypted string. That's why the function shouldn't ...

Hi, I found a bug in the implementation of AES under mbedtls (block implementation). When encrypting something using CBC by calling mbedtls_aes_crypt_cbc , you are actually calling esp_aes_crypt_cbc . Notice that the function expects the initialization vector to be given as unsigned char iv[16] (so ...

Thank you both for your answers. So, as per my understanding, that UUID is generated by iOS based on some hardware property of the BLE device (e.g. MAC address). Regarding this: Of course you can write your own code, which can generate similarly guid and create QR code with it, then you can add such...

Sorry for bringing the topic back on, but the original poster has a point: While scanning for an ESP32 Advertising device using nRF Scanner (or BLE Scanner) - on Android Phones, you indeed get the MAC address of the device. However, when you scan for it in iOS using the same apps, you don't get the ...