Unexpected indicated connection security with connectivity firmware

RE: Unexpected indicated connection security with connectivity firmware

Petter Myhre — Wed, 10 Aug 2016 11:37:10 GMT

Thank you for adding the fix Adrian :)

RE: Unexpected indicated connection security with connectivity firmware

Adrian Eggenberger — Tue, 09 Aug 2016 11:25:54 GMT

I've found the bug that causes the same problem on the central side. The problem on the central side is the same as on the peripheral side. The encoding of the structure ble_gap_enc_info_t has not been adapted to the S130 2.0.0.

For the peripheral side the provided ble_gap_sec_info_reply.c fixes this issue.

For the central side another fix is required. You can download the fix for the central side here (ble_gap_encrypt.c).

Regards Adrian

RE: Unexpected indicated connection security with connectivity firmware

Adrian Eggenberger — Mon, 08 Aug 2016 13:10:25 GMT

The file fixes the issue on the peripheral side. Now I have to reopen the issue. The same problem also exists when acting as a central. Also in this role the security after reestablishing a connection is only 1/2 with key length 8. What file causes the same thing on the central side?

RE: Unexpected indicated connection security with connectivity firmware

Petter Myhre — Tue, 03 May 2016 13:30:43 GMT

Here is a fix for achieving the correct security level when re-encryption the link with bonded peer.

Replace ble_gap_sec_info_reply.c with it.

RE: Unexpected indicated connection security with connectivity firmware

Adrian Eggenberger — Thu, 31 Mar 2016 14:47:49 GMT

The source code is strictly confidential, so I've opened a new support case on the MyPage and attached the project and some instructions how to reproduce there. It would be great if you could have a look at it. Don't hesitate to ask me if something doesn't work as expected.

RE: Unexpected indicated connection security with connectivity firmware

Petter Myhre — Wed, 30 Mar 2016 14:54:56 GMT

Ok. Thanks. Both if you have changed the connectivity source code.

RE: Unexpected indicated connection security with connectivity firmware

Adrian Eggenberger — Wed, 30 Mar 2016 14:19:02 GMT

After the initial bonding the security mode is correct. After a disconnect and reconnect the security mode is invalid. I'll check if i can share the project or parts of it to reproduce. What parts of the project do you need? Host, Connectivity or Both?

RE: Unexpected indicated connection security with connectivity firmware

Petter Myhre — Wed, 30 Mar 2016 14:11:10 GMT

I see. Do you get the correct security level with the BLE_GAP_EVT_CONN_SEC_UPDATE event when you do the initial bonding? Would it be possible to share your project? If it is confidential or secret you can do it privately through your MyPage at www.nordicsemi.com

RE: Unexpected indicated connection security with connectivity firmware

Adrian Eggenberger — Wed, 30 Mar 2016 12:38:28 GMT

I actually added some code in the connectvity firmware to verify if the event from the softdevice contains the unexpected values or if it's a serialisation/deserialisation problem. That was my first guess, but the event coming from the softdevice in the connectivity firmware alredy contains the invalid values.

If I should test something to help to investigate the issue please ask.

RE: Unexpected indicated connection security with connectivity firmware

Petter Myhre — Wed, 30 Mar 2016 12:01:59 GMT

I think your assumption is correct. I will investigate. You could also try putting a breakpoint in the nRF51 and check the BLE_GAP_EVT_CONN_SEC_UPDATE event, before it is relayed.