From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] RFCOMM service level security testing
Date: Sat, 30 Oct 2004 17:55:59 +0200 [thread overview]
Message-ID: <1099151759.16247.18.camel@pegasus> (raw)
Hi Folks,
I released patch-2.6.9-mh3 some minutes ago and it contains the first
experimental version of the service level security implementation for
the RFCOMM layer.
The libs CVS is also updated to add the specific defines for using it
and rctest got some extra paramters for it, but it seems that the CVS
service for anonymous access from Sourceforge is broken and so most of
you won't get these modification. However this is not a big problem,
because you can use L2CAP_LM, L2CAP_LM_AUTH etc. for it. The values
behind these defines are identical and so this should work at least for
testing this new feature.
Please test this and send reports back to the mailing list.
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-10-30 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 15:55 Marcel Holtmann [this message]
2004-11-02 22:03 ` [Bluez-devel] RFCOMM service level security testing Marcel Holtmann
2004-11-03 15:28 ` Stephen Crane
2004-11-03 15:37 ` Marcel Holtmann
2004-11-03 15:56 ` Stephen Crane
2004-11-03 16:08 ` Marcel Holtmann
2004-11-03 16:38 ` Stephen Crane
2004-11-05 12:28 ` Marcel Holtmann
2004-11-03 16:49 ` Steven Singer
2004-11-03 17:52 ` Marcel Holtmann
2004-11-03 18:45 ` Steven Singer
2004-11-03 19:01 ` Marcel Holtmann
2004-11-15 17:58 ` [Bluez-devel] " David Hughes
2004-11-15 18:10 ` 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=1099151759.16247.18.camel@pegasus \
--to=marcel@holtmann.org \
--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