This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is re-pairing necessary with MITM protection?

I am working on a peripheral. This peripheral is IO display only. On the other side, the central is keyboard + display. I have a single, custom service with a single characteristic. Said characteristic is readable and writable and requires both encryption and authentication. Pairing seems to work - I can read and write to it successfully.

However, with bonding enabled, once I re-connect and try to read or write to that characteristic, I get an "Insufficient Authentication (Error Code 0x05)" error.

Is this expected? When using MITM protection, does a central always need to re-pair?

Parents
  • Looks like the issue was with non-volatile memory. Security properties were not being saved properly. Why or how - I'm not sure yet, but that's a different issue.

    So if a device is paired and bonded with MITM protection, authenticated reads or writes should succeed on the initial and following connections.

    Thanks Hung Bui for your help. I deleted my previous "answer" as I was misunderstanding the book quote.

Reply
  • Looks like the issue was with non-volatile memory. Security properties were not being saved properly. Why or how - I'm not sure yet, but that's a different issue.

    So if a device is paired and bonded with MITM protection, authenticated reads or writes should succeed on the initial and following connections.

    Thanks Hung Bui for your help. I deleted my previous "answer" as I was misunderstanding the book quote.

Children
No Data
Related