RE: Service level security for RFCOMM

Hi Steve,

> > 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, ...).)

it is the same. I already committed the needed stuff to the CVS and
changed rctest to set them. However without a correct kernel the call of
setsockopt() will fail.

Regards

Marcel




-------------------------------------------------------
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