BLE UART example pairing? password?

[mbates14]

I noticed when using the UART BLE Example that there is no password or pairing request to connect to and use the device. 

Everything works fine, and I even implemented my own little password thing that has to present a password over the active connection before itll start sending data over the UART connection. 

The trouble is, there is no paring password or code, or password in order to connect. I cant figure out how to fix that situation, any ideas? 

This is causing me a problem in the Denial of Service area. Someone can connect to the device, and just leave it idle and connected, preventing an authorized user from connecting. This is starting to happen to me in school situations because of nefarious students. 

[Simon]

I would recommend you to use the Peer Manager if you would like add bonding/pairing to the ble app uart example, which will prevent unauthorized users to connect to your application.

Take a look at the answer I just posted about bonding. I have also attached an example I made earlier with the BLE UART peripheral example with legacy bonding with a static passkey. Be aware that this pairing method is not really secure from attackers.

ble_app_uart_bonding_static_passkey_SDK_15.2.0.zip

Best regards,

Simon

[mbates14]

Thanks for that! I really appreciate that and now I can compare it against my version so I can port the changes over. This leaves a question though. 

I see the peer manager/binding uses the persistent storage, I am also using the persistent storage to put AT command data for the ID, etc, and even the password. 

Obviously, I dont want the two systems to occupy the same space in persistent storage and get clobbered, is there a way to define where in persistent storage the peer manager stuff sits? or? 

Thanks!