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.
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...