Authentication before connection

RE: Authentication before connection

RK — Wed, 09 Mar 2016 05:32:08 GMT

so there you go - it's easy. If there are no bonds you let anyone connect - the first guy who connects and bonds is then 'the connection'. If you have a bond then you use the functions to whitelist the address and only that guy will connect.

RE: Authentication before connection

YSquare — Wed, 09 Mar 2016 03:19:44 GMT

For the first time (whitelist is empty), the peripheral should allow connection & paring if the central passes the authentication.

RE: Authentication before connection

RK — Wed, 09 Mar 2016 03:14:15 GMT

Well that's just whitelisting again and the peer manager (Nordic's library code) supports making a whitelist for bonded peripherals.

However how's that actually going to work in practice? If you can't connect unless you're bonded and you can't bond before you connect, then there's no way to get a peripheral bonded so you can connect to it the first time.

RE: Authentication before connection

YSquare — Wed, 09 Mar 2016 03:09:29 GMT

Thanks. It is also acceptable to allow/disallow central device to connect if it is not bonded before.

RE: Authentication before connection

RK — Wed, 09 Mar 2016 02:45:23 GMT

You can't. Bluetooth doesn't support that type of authentication before connection, only afterwards. However what's the problem? If no characteristics can be read before bonding, you don't have an issue.

You can whitelist by MAC address to allow/disallow device connection by address, if you know the addresses you want, but that's it, that's all you can do.