RE: Service level security for RFCOMM

Hi Abhi,

> Service level security is required for JSR-82 like Steve pointed it out. 
> For anyone implementing JSR-82, they would have to add this service level
> security themselves. It would be most useful to have it as part of bluez
> rather than have people implement their own way of it. 

actually you can't implement it in a sane way in userspace, because you
don't have control over the RFCOMM signalling channel.

> Marcel, if you recall, we've exchanged an email regarding service level 
> security. At that point, you had mentioned thinking about a security manager 
> embedded in bluez that would allow it.

This is a little bit different, because this is more basic stuff. You
need to integrate the trigger points of the Bluetooth security mechanism
into the RFCOMM layer. And actually the state machine of RFCOMM is more
complex than the one of L2CAP. For me it is not clear at the moment what
is the best thing to do without breaking anything.

So the question still stands. Should we already force authentication
when the peer sends PN CMD?

> I am currently working on implementing JSR-82 which requires this level 
> of security. If anyone has already implemented or has a good way of doing it,
> please let me know. I would be very interested.

As mentioned above the only way is inside the kernel, because otherwise
you will trigger after the MSC exchange and this is too late.

> Also, currently there is no service level security in l2cap for outgoing
> connections. I would like to know if someone has already taken a stab at it
> and if this should be part of bluez in the future. 

You must convince me that this is really needed and a good idea. For
what kind of application do you wanna use it?

Regards

Marcel




-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/