Info about new nRF5 SDK v17.1.0

[DimitrisP]

Hello

new nRD5 SDK v17.1.0

Can you please help me to find more about:

1.
"- NRFFOSDK-13484: Added an option in the Peer Manager to decide that a connection will not be processed by this module."

and
"2. - NRFFOSDK-13616: Updated handling of bonding events to be more sceptical of failed bonding/encryption attempts, since they can be the sign of an attack."

Dimitris

[ovrebekk]

Hi Dimitris

I will check internally if we have some more information regarding these changes, and get back to you. 

Best regards
Torbjørn

[DimitrisP]

Hi

So if I get it right

There is a new option in peer manager (NRFFOSDK-13484), Nordic announce it and do not let customers to use it. Don't you thing it is bit strange?

I do need code from other users, but it is really useful to know how to exclude connections from handled by PM 

Dimitris

[ovrebekk]

Hi Dimitris

Not sure what you mean, you are obviously free to use this feature if you want 

The pm_conn_exclude(..) function is documented here (the same documentation that you can find in the header file). 

DimitrisP said:

I do need code from other users, but it is really useful to know how to exclude connections from handled by PM 

Could you provide some more information on what you are trying to do?

The reason this feature wasn't there before is that normal BLE applications don't need it. If you don't want to do pairing/bonding for particular connections you can always do that, the only difference with this feature is that it allows you to handle pairing/bonding manually for specific connections. 

Normally people use the peer_manager to avoid having to implement all of this themselves. 

Best regards
Torbjørn

[DimitrisP]

Hi Torbjorn

Thank very mutch that is a crystal clear answer to my initial first question.

Before closing the case I will if there in anything  for:

"2. - NRFFOSDK-13616: Updated handling of bonding events to be more sceptical of failed bonding/encryption attempts, since they can be the sign of an attack."

Is that what Avrebbek said "I am still waiting for more background on 2), but essentially if you get repeated failed pairing attempts it could be a sign that someone is trying to hack your connection by intercepting the pairing packets and trying to install themselves as a man in the middle. For this reason it is safer to disconnect when this situation occurs, rather than to repeatedly try to do pairing again. "

or there is more?

 

Dimitris