Re: RFCOMM Security

Marcel,
 I would like to rephrase this question. This is again all about
BlueCove JSR-82.

 When we open socket for client connection there is an options for
setsockopt  RFCOMM_LM_AUTH and RFCOMM_LM_ENCRYPT as far as I can see
they don't change the connection settings.  The same for L2CAP
connections: only we tried L2CAP_LM_AUTH

 I do calls in this sequence: socket, bind, setsockopt, connect
 But the connection does not get authenticated. (pairing procedure not started)

 The problem does not apply for RFCOMM/L2CAP service when service
created and I want only authenticated connections to be accepted we
use socket(),bind(), setsockopt(RFCOMM_LM_AUTH), listen().  Then when
client connects.  The system will initiate pairing procedure.

 Is this unimplemented feature of BlueZ for client connections of we
are not using it right?

 Our code is here:
http://code.google.com/p/bluecove/source/browse/bluecove-gpl/trunk/src/main/c/

Regards,
Vlad Skarzhevskyy
http://bluecove.org

On 5/31/08, Mina Shokry <[email protected]> wrote:
> Hello all
> I have a question regarding BlueZ
> does bluez support rfcomm connection security (eg. authenticate and
> encrypt)?
> if yes, please can anyone give an example (C code)?
> thanks in advance
>
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
>  Bluez-devel mailing list
>  [email protected]
>  https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php