Skip to content
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

Possibility to read IO capability of initiating device #1727

Open
madidas-sudo opened this issue Mar 12, 2024 · 0 comments
Open

Possibility to read IO capability of initiating device #1727

madidas-sudo opened this issue Mar 12, 2024 · 0 comments
Assignees

Comments

@madidas-sudo
Copy link

I have an application where a peripheral is connected to via a fixed passkey. This works when the central has specified some IO capability, but if no IO capability is selected on the central a "just works" connection is established and the initiating device has read access to all characteristics.

Following
https://devzone.nordicsemi.com/f/nordic-q-a/42978/pairing-bonding-happens-even-when-the-client-s-iocap-is-no_io_caps I would presume that it should be dealt with by disconnecting the initiator if insufficient IO capability is set but I was unable to find functionality in nimBLE to do so.

I hope I did not misunderstand the problem at hand too badly...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants