From: "Zmej Gorianin" <mortagon.iyi@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Is LMP implemented in BlueZ?
Date: Thu, 15 Mar 2007 19:11:01 +0200 [thread overview]
Message-ID: <464194a50703151011j666c93e2s1ffbe017361279f5@mail.gmail.com> (raw)
In-Reply-To: <1173970416.7461.7.camel@aeonflux.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 1838 bytes --]
2007/3/15, Marcel Holtmann <marcel@holtmann.org>:
>
> Hi,
>
> > I am currently doing my bachelor's dissertation about creating an
> > alternative Bluetooth authentication and key exchange scheme, using
> > public key crypto, and would like to know whether I should build on
> > top of the Bluetooth protocol stack or I can actually add code inside
> > the LMP. I have looked thorough the code in the BlueZ kernel module
> > and In bluez -libs package and I'm left with the impression that the
> > link manager and the LMP are part of the Bluetooth device's firmware,
> > while the HCI asks it to initiate specific LMP transactions. So my
> > question is whether LMP is a software component implemented by BlueZ
> > on a computer or it's a firmware component on the Bluetooth receiver
> > connected to the computer. I'd be thankful if somebody can clarify
> > that for me.
>
> the LMP implementation is part of the firmware inside the Bluetooth
> chip.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
Thank you very much. Can you tell me then, if I can tamper with the
semi-permanent keys or are they stored within the device also. I need to
know whether I can overwrite them in some way or I have to work without
augmenting the existing authentication and key exchange scheme at all.
Thanks in advance.
Regards,
Dragomir
[-- Attachment #1.2: Type: text/html, Size: 2455 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-03-15 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 13:39 [Bluez-devel] Is LMP implemented in BlueZ? Zmej Gorianin
2007-03-15 14:53 ` Marcel Holtmann
2007-03-15 17:11 ` Zmej Gorianin [this message]
2007-03-16 15:30 ` Zmej Gorianin
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=464194a50703151011j666c93e2s1ffbe017361279f5@mail.gmail.com \
--to=mortagon.iyi@gmail.com \
--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