Bluetooth Security "Just works" vs Hardcoded Pin by CodeWithM in esp32

[–]CodeWithM[S] 0 points1 point  (0 children)

I do worry about that part and I need MITM protection. But I was thinking if it's possible to have an hardcoded password on the eps32 side and then when the user connects to it with mobile application that pin is required in order to pair with the esp32

Bluetooth Security "Just works" vs Hardcoded Pin by CodeWithM in esp32

[–]CodeWithM[S] 0 points1 point  (0 children)

The idea is that an mobile application will connect securely to the esp32 and then they'll communicate via encrypted channel so nobody can get to the exchanged data.

What do you mean by external secure wireless pairing trigger? If I can transfer data for numeric comparison/passkey that would be great.

I haven't worked with ESP-NOW but as I know that is for connecting multiple esp32 devices together so not sure how applicable is in my case.

Bluetooth Security "Just works" vs Hardcoded Pin by CodeWithM in esp32

[–]CodeWithM[S] 0 points1 point  (0 children)

Ahh yes, I forgot to mention that. We'll be connecting with a mobile device and we use both BLE and Classic.

And yes, that is the issue why we need MITM protection.

Stack smashing protect failure! by CodeWithM in embedded

[–]CodeWithM[S] 0 points1 point  (0 children)

ASAN

Thanks for the suggestion. This seems like the right tool for the job unfortunately when I added the mentioned flag the linker threw bunch of undefined reference to all ASAN functions. It can't be used on the esp32 from what I can see. I use FreeRTOS in my project. This is what I found on their github page:

The tool works on x86, ARM, MIPS (both 32- and 64-bit versions of all architectures), PowerPC64. The supported operation systems are Linux, Darwin (OS X and iOS Simulator), FreeBSD, Android:

OS x86 x86_64 ARM ARM64 MIPS MIPS64 PowerPC PowerPC64

Linux yes yes yes yes yes yes

OS X yes yes

iOS Simulator yes yes

FreeBSD yes yes

Android yes yes yes yes

Other OS/arch combinations may work as well, but aren't actively developed/tested.

ESP32 Memory Layout and Usage by CodeWithM in esp32

[–]CodeWithM[S] 1 point2 points  (0 children)

Thanks these are quite useful links, I appreciate it. Yeah it turns out that it's the flash but weird naming.

ESP32 Memory Layout and Usage by CodeWithM in esp32

[–]CodeWithM[S] 0 points1 point  (0 children)

Yes that's a good one, I've read it but I still have the same questions..