Re: Authentication problems
Re: Authentication problems
- Subject: Re: Authentication problems
- From: Nick Brook <email@hidden>
- Date: Tue, 05 Jul 2016 00:38:11 +0100
I am using just works, I haven’t specified MITM on iOS or the central, is that implicit when EncryptionRequired?
On 5 Jul 2016, at 07:09, Nick Brook <email@hidden> wrote:
Hi,
I am building an App which creates a peripheral. I have some properties with encryption required for notify, read, write.
When a central I’ve built attempts to enable notifications, read or write, initially iOS returns 0x0405 as expected as the characteristics require authentication. However, after encrypting and bonding is complete (including tapping Pair on the iOS prompt), repeating the same command still returns 0x0405.
Just tapping “Pair” on the iOS prompt or putting in a 6 digit code and pairing (or doing out of bound pairing although i think that’s still not a thing on iOS)? If you’re using ‘Just Works’, ie just tapping the “Pair” button with no exchange of PIN, the link is authenticated but has no MITM protection. If the characteristic requires MITM protection, you’ll get Insufficient Authentication again. See BTLE spec volume 3, Part C section 10.3.1. There’s Table 10.2 just below which gives you all the permutations as well. (this is the 4.2 spec).
Why would iOS continue to reject the request after authentication? I can’t see anything in the Bluetooth diagnostic.
Thanks
Nick
|
_______________________________________________
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