From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Fred Schaettgen To: BlueZ Mailing List MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <200501030040.48387.bluez-devel@schaettgen.de> Subject: [Bluez-devel] Problem with service level security (2.6.10-mh1) Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 3 Jan 2005 00:40:46 +0100 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