SSP Debug Mode for BLE Legacy Pairing

RE: SSP Debug Mode for BLE Legacy Pairing

bjorn-spockeli — Wed, 24 Apr 2019 13:41:37 GMT

Mark P. Mendelsohn: It appears that the BAD MIC failure originates from the firmware running on the nRF52 device and that it is a known issue even with the latest firmware, see https://devzone.nordicsemi.com/f/nordic-q-a/39439/nrf-sniffer-unable-to-track-packet-data-length-changes.

RE: SSP Debug Mode for BLE Legacy Pairing

Mark P. Mendelsohn — Wed, 03 Apr 2019 23:44:02 GMT

Updated nrfSniffer hex file to Beta 3. Attached is the latest Wireshark capture. Each packet has the same "Encrypted packet decrypted incorrectly (bad MIC).

devzone.nordicsemi.com/.../badMIC.pcapng

RE: SSP Debug Mode for BLE Legacy Pairing

Mark P. Mendelsohn — Tue, 02 Apr 2019 18:12:17 GMT

Here is another screen shot and trace that captured from the CONN_REQ packet.

devzone.nordicsemi.com/.../with-conn_5F00_req.pcapng

RE: SSP Debug Mode for BLE Legacy Pairing

Mark P. Mendelsohn — Tue, 02 Apr 2019 17:52:20 GMT

Attached Wireshark screen shot and trace taken with all protocols enabled and pairing occurring while the scope is on. Still unable to see into encrypted data packets shown as "Unknown".

devzone.nordicsemi.com/.../ssp-trace.pcapng

RE: SSP Debug Mode for BLE Legacy Pairing

bjorn-spockeli — Fri, 29 Mar 2019 15:45:43 GMT

As David Edwin stated in the question you referred to, you need to enable the protocol for the nordic ble sniffer, which is NORDIC_BLE and that needs to be enabled. Could you try to click enable all in the "Enabled Protocols" in Wireshark

RE: SSP Debug Mode for BLE Legacy Pairing

Mark P. Mendelsohn — Thu, 28 Mar 2019 16:25:04 GMT

I just want to view the encrypted data using the nRF Sniffer. It is a Just Works connection but the nRF Sniffer can't seem to decode the data even when it was present during the pairing process. I reported this issue some time ago here https://devzone.nordicsemi.com/support/206896. Since we are in production now on this product it is important to have some kind of solution. Both ways I have tried have not worked. Thanks.

RE: SSP Debug Mode for BLE Legacy Pairing

bjorn-spockeli — Thu, 28 Mar 2019 13:07:36 GMT

HI Mark,

I assume that you're referring to the ble_app_multirole_lesc example in SDK v14.0.0.

As far as I know we do not have any example that has this feature. Do you want to use a static encryption key in legacy pairing or is this only to be able to see the encrypted data with a Bluetooth Protocol sniffer? If its the latter, then you can use the Just Works pairing as the keys are sent in plain text. So as long as you capture the pariing procedure, then you should still be able to see all the data as the sniffer sees the encryption key.

Best regards

Bjørn