From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth security in bluez ?
Date: Mon, 29 Mar 2004 01:01:42 +0200 [thread overview]
Message-ID: <1080514902.2281.183.camel@pegasus> (raw)
In-Reply-To: <200403290053.32295.cijoml@volny.cz>
Hi Thomas,
first if you start asking on a mailing list you should keep posting also
your answers to it.
> > ok but i'm intersted in how the security is
> > implemented (E0, E1, E21, E22, E3 algorithms) ... i'm
> > looking for the source code that does the
> > authentification and encryption. You mean that it's
> > done inside the dongle ?
The Bluetooth host stack only handles everything at the HCI level and
its upper layers. Everything down like link manager, baseband and radio
is part of the Bluetooth chip. And this also means that every security
mechanism is implemented in the chip. From the host side you can only
trigger them.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-03-28 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040328223546.2206.qmail@web60303.mail.yahoo.com>
2004-03-28 22:53 ` [Bluez-users] Bluetooth security in bluez ? Michal Semler (volny.cz)
2004-03-28 23:01 ` Marcel Holtmann [this message]
2004-03-28 22:08 Thomas PEYRIN
2004-03-28 22:28 ` Michal Semler (volny.cz)
2004-03-28 22:56 ` 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=1080514902.2281.183.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=cijoml@volny.cz \
/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