public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Fred Schaettgen <bluez-devel@schaettgen.de>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Problem with service level security (2.6.10-mh1)
Date: Mon, 3 Jan 2005 00:40:46 +0100	[thread overview]
Message-ID: <200501030040.48387.bluez-devel@schaettgen.de> (raw)

Hi,

I've got some problems with enabling service level security for rfcomm.
First I was hoping that this is in 2.6.10, but obvisously it isn't.
Btw. rctest doesn't work with a vanilla kernel, because setsockopt() is called 
(and fails), no matter if it's necessary or not. 

So after applying the mh1-patch for 2.6.10, the result looks like this:

$ ./rctest -d -P 27 -A
rctest[12830]: Waiting for connection on channel 27 ...
rctest[12831]: Connect from 00:E0:03:32:28:37
rctest[12831]: Receiving ...
rctest[12831]: Recevied 4 bytes
(nothing more to expect at this point..)
rctest[12831]: Disconnect
$

No authentication is triggered, even though the two devices are not paired.
rctest seems to recognize the A-switch nicely. setsockopt is called and 
doesn't fail.
Is service level security supposed to work at the moment with 2.6.10-mh1?

regards
Fred

-- 
Fred Schaettgen
bluez-devel@schaettgen.de


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-01-02 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 23:40 Fred Schaettgen [this message]
2005-01-03  0:48 ` [Bluez-devel] Problem with service level security (2.6.10-mh1) Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501030040.48387.bluez-devel@schaettgen.de \
    --to=bluez-devel@schaettgen.de \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox