Optional secure pairing with a passkey#886
Conversation
Support passkey pairing when requested by the central Fix a comment and reorder warning
geekbozu
left a comment
There was a problem hiding this comment.
Looks good,
Thanks for staying on top of this!
|
work properly . thanks @evergreen22 |
| * | ||
| * Standards insist that the rand() PRNG be deterministic. | ||
| * Use the nimble TRNG here since rand() is predictable. | ||
| * Use the tinycrypt prng here since rand() is predictable. |
|
Closes #880 |
|
Thank you very much, @evergreen22! Bluetooth pairing now works exactly as expected:
Great job everyone! If I had only 1 suggestion : add a visual indicator showing if the connectivity is secured or not (ble icon with another color? another icon? something else?). |
|
Update : according to my observations, OTA is much more reliable on not bonded connections! Using my new phone, it's nearly impossible to start an OTA (it fails at 0% after a few seconds) when bonded. WIthout the bond, OTA works as expected (and a lot faster with my new phone : 12kbps). For some reason, it still works (bonded or not) on my older phone (but it's so slow... 2-3 kbps). |
|
If I had only 1 suggestion : add a visual indicator showing if the connectivity is secured or not (ble icon with another color? another icon? something else?).
A padlock icon to the left of the ble icon would be nice when the
connection is encrypted.
|
Support passkey pairing when requested by the central.
Also, fixes a comment and a reorder warning introduced by a faulty conflict resolution.