From: "Zmej Gorianin" <mortagon.iyi@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Combination Keys?
Date: Mon, 14 May 2007 20:07:42 +0300 [thread overview]
Message-ID: <464194a50705141007p3d81a78dlbd2e364d47a51d21@mail.gmail.com> (raw)
In-Reply-To: <1179152578.13351.47.camel@violet>
[-- Attachment #1.1: Type: text/plain, Size: 567 bytes --]
2007/5/14, Marcel Holtmann <marcel@holtmann.org>:
>
> Hi,
>
> > I'm doing my bachelors dissertation project about alternative Bluetooth
> authentication and key exchange and I would like to know whether it is
> possible to pass the combination key my app has constructed to BlueZ in some
> way, so that BlueZ will write the key in
> /var/lib/bluetooth/<BD_ADDR>linkkeys or my application should tamper with
> the file directly.
>
> you might wanna modify the file directly or better use the textfile.c
> library to do so.
>
> Regards
>
> Marcel
Thank you.
Regards
[-- Attachment #1.2: Type: text/html, Size: 872 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- 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
prev parent reply other threads:[~2007-05-14 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 13:36 [Bluez-devel] Combination Keys? Zmej Gorianin
2007-05-14 14:22 ` Marcel Holtmann
2007-05-14 17:07 ` Zmej Gorianin [this message]
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=464194a50705141007p3d81a78dlbd2e364d47a51d21@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