From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Using ASCII based files for link key storage
Date: Sat, 16 Apr 2005 21:04:31 +0200 [thread overview]
Message-ID: <1113678271.16433.85.camel@pegasus> (raw)
In-Reply-To: <200504161932.39416.bluez-devel@schaettgen.de>
Hi Fred,
> > And second, The format of the link key file will be very simple:
> >
> > <bdaddr> <hex-linkkey> <type>
>
> This means that we will still be unable to list the devices for which a link
> key exists without root privileges, is this correct? If yes, is this
> intentional?
there is no other way, because we must store the link keys as secure as
possible.
> Anyway, I for myself don't care much about where the data goes, as long as the
> location and the file formats stay stable, because the link key manager of
> kdebluetooth has to be changed each time.
In the long term I like to make the place totally configurable, but for
now I think going with /var/lib/bluetooth and ASCII based files is a
good think.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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-04-16 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 16:23 [Bluez-devel] Using ASCII based files for link key storage Marcel Holtmann
2005-04-16 17:32 ` Fred Schaettgen
2005-04-16 18:01 ` Fred Schaettgen
2005-04-16 18:33 ` Marcel Holtmann
2005-04-18 11:35 ` Marcel Holtmann
2005-04-16 19:04 ` Marcel Holtmann [this message]
2005-04-16 21:21 ` Fred Schaettgen
2005-04-16 21:38 ` Marcel Holtmann
2005-04-16 23:16 ` Marcel Holtmann
2005-04-17 18:41 ` Guylhem Aznar
2005-04-17 18:54 ` 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=1113678271.16433.85.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