-
Notifications
You must be signed in to change notification settings - Fork 7.6k
SSP Functionality Incomplete #4622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yup :) please make the pull request :) |
One thing in the source code that I am not sure, but I changed it anyway. This is it needs to verify if it is master mode before registering the gap callback. Now I change the checking so that the gap callback will present either in master and slave mode and I need some events in the gap callback to be handled for SSP authentication. |
I have created the pull request, please review the code, thanks. |
Added authentication callbacks and example, resolves #4622.
I have tried to make use of SSP and setup ESP32 device as slave to accept binding request from smart phones, PCs, etc. However I figure out that the SSP implementation is incomplete. Normally the binding process involves the Smart Phone initiate a binding request with a key code. User can verify the code in the ESP32 device screen, and select the desire action (either accept or reject) in the ESP32 device.
However, just make use of the BluetoothSerial API cannot make the job done. The API seems missing some callbacks mechanism for the binding process.
I need to copy and modify the BluetoothSerial source code to make this works, and I think I can contribute my work to the source as a pull request. So, if I do this, is there anybody who will review the code and merge it?
The text was updated successfully, but these errors were encountered: