From: Guylhem Aznar <bluez-devel@externe.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Using ASCII based files for link key storage
Date: Sun, 17 Apr 2005 14:41:47 -0400 [thread overview]
Message-ID: <20050417184147.GA2546@externe.net> (raw)
In-Reply-To: <1113693376.18450.23.camel@pegasus>
On Sunday, 17 April 2005 at 1:16:16 (+0200), Marcel Holtmann wrote:
> I just wrote some code do deal with the link key storage and to support
> the device name cache. I don't fully like it and I think it contains
> some bugs, but it is better than nothing. So feel free to send me
> patches to improve it. And btw using the hcitool with name cache suppor=
t
> is very great in my environment.
Some general thoughts:
- regarding keys, an ascii version to ease manipulation would be
great. I hate it when I have to rm all the keys because one device
has a problem. Even worse - some device can only pair with 1 other
device. If I was able to share keys between my desktop, my laptop and
my handheld that would be great(but maybe the bt device will use the
bt address too and refuse that)
- regarding names : would it be possible to replace bt address by
nicknames? My devices send back a FQDN on scan because that's the
way I set them up, but it would be much better if I could address
them with that FQDN too.
The current ascii key approach is interesting, but entries in
/etc/hosts where bt address would be bound to names, which names would
then be used by l2ping, obexftp etc would be even better !
Guylhem
--=20
Bien =E0 vous - Best regards,
Guylhem P. Aznar
--=20
*@externe.net http://externe.n=
et
P=E9rim=E9/Deprecated: @oeil.qc.ca, @metalab.unc.edu, @ibiblio.org, @7=
un.org
GPG: 92EB37C1 DD11C9C9 20519D01 E8FA1B11 42975AF7 http://externe.net/pubk=
ey
-------------------------------------------------------
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-17 18:41 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
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 [this message]
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=20050417184147.GA2546@externe.net \
--to=bluez-devel@externe.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