RE: Service level security for RFCOMM

Hi Abhi,

On Fri, 2004-10-29 at 16:35, Bhatt Abhi-ABHATT wrote:

> Sorry for the confusion but I wasn't referring to user space at all. I was 
> thinking of having the rfcomm service level security implemented in almost 
> the same way as the l2cap service level security(incoming connection). The 
> service level security options could be set using setsockopt(..) in rfcomm. 
> This in turn could be used to set the service level settings for the l2cap 
> socket it uses. I can draw a sequence diagram(function calls) to show how i
> picture the design. I'll do that.

I think that from the user-space's point of view, the interface should
be identical. (In fact I think this is already supported, just not
acted-upon: you do setsockopt(sock, SOL_RFCOMM, ...).)

> > > 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.
> 
> > > I've had a look at this recently. If I get time I will have a go at  
> > > implementing it.
> 
> Steve, I would be interested to know how you intend to implement it.

I will need to revisit my notes. It's been a while and I've forgotten
:-(

> Plus JSR-82 requires that service level security should be possible for
> outgoing connections. So for anyone trying to implement JSR-82 and using
> bluez, it is needed.

This is a bit strong: p42 of the JSR-82 spec states that "Not all
Bluetooth systems support authentication [...]". Thus you _can_ conform
to JSR-82 without this. However it's nice to have :-)

> Regards
> Abhi

Cheers,
Steve
-- 
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@xxxxxxxxxxxxxx +353-1-6601315 (ext 209)



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click