From: "Collin R. Mulliner" <collin@betaversion.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Encryption
Date: Thu, 01 Dec 2005 21:10:33 -0800 [thread overview]
Message-ID: <1133500233.15695.3.camel@panic> (raw)
In-Reply-To: <9d47cfd0512011325x4de6e0a6wbd78806c2072dc5f@mail.gmail.com>
Hi Abu,
On Thu, 2005-12-01 at 15:25 -0600, Abu hasnat Sayem wrote:
> I am working on doing Encryption and Authentication at the RFCOMM and
> L2CAP level using BlueZ. I would like to know if there exists certain
> function calls to accompolish it or i have to incorporate new code in
> it.
this is done via setsockopt(2), take a look at:
/usr/src/bluez-utils-2.22/pand/main.c (search for SECURE)
or check sobexsrv (http://www.mulliner.org/bluetooth/sobexsrv.php)
... Collin
--
Collin R. Mulliner <collin@betaversion.net>
BETAVERSiON Systems [www.betaversion.net]
info/pgp: finger collin@betaversion.net
Don't talk just code!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-02 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 21:25 [Bluez-devel] Encryption Abu hasnat Sayem
2005-12-02 5:10 ` Collin R. Mulliner [this message]
2005-12-05 16:08 ` Abu hasnat Sayem
2005-12-05 16:19 ` Albert Huang
2005-12-06 19:51 ` Abu hasnat Sayem
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=1133500233.15695.3.camel@panic \
--to=collin@betaversion.net \
--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;
as well as URLs for NNTP newsgroup(s).