Re: [OS X] Using unsecure/unauthenticated RFCOM
Re: [OS X] Using unsecure/unauthenticated RFCOM
- Subject: Re: [OS X] Using unsecure/unauthenticated RFCOM
- From: Alexander Traud <email@hidden>
- Date: Fri, 12 Oct 2012 17:18:11 +0200
- Thread-topic: [OS X] Using unsecure/unauthenticated RFCOM
Back in March, Matt wrote:
>>>> SSP requires that all L2CAP connections be authenticated ...
>> Bluetooth 4 Section 5.2.2.8 ... mandates the use of encryption when
>> the remote device is v2.1+EDR for all services other than SDP.
> Simple-Secure Pairing offers the Just-Works
authentication scheme. Here, both
> devices connect only for this service like
a one-time use. Such a connection
> can be encrypted. And this is what the
above cite is about.
Anything new?
If I exchange files between to Nokia SSP enabled devices, no pairing request
is shown.
Another issue:
In OS X v10.8 after some days, I am asked to update the pairing; I get a new
pairing request. This happens with all devices, even Nokia and an Apple
iPhone. I have to pair them again. If you have any idea what could be the
cause of this, please, reply.
_______________________________________________
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