Re: Authentication problems
Re: Authentication problems
- Subject: Re: Authentication problems
- From: Nick Brook <email@hidden>
- Date: Tue, 05 Jul 2016 01:25:54 +0100
| It appears your theory is correct. Enabling MITM on the central and setting the IO capabilities to ‘display only’, and logging the received code to my debug output, I was able to enter the code into iOS. This allowed the characteristics to be accessed.
Very disappointing that this is not included in the documentation Apple, and also disappointing that ‘just works’ cannot be used. As this is a headless central I will have to remove encryption.
I will create bug/feature reports for these two issues.
Thanks Roland.
I am using just works, I haven’t specified MITM on iOS or the central, is that implicit when EncryptionRequired?
I don’t know because the documentation glosses over all the complicated bits of bluetooth and doesn’t say. However, empirical evidence from your test says that it does require MITM, because that’s the only sequence I can come up with which gives you the Insufficient Authentication twice and, since the documentation for Core Bluetooth doesn’t even mention MITM my handwaving guess would be that encryption sets that requirement because that’s the more secure version (although that begs the question, what does just works pairing do apart from identify the device for the future and allow the link to be encrypted).
Can you get your central to use MITM, even with a fixed key or something dumb, see if it changes things? What’s the central implementation?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden