From: Fred Schaettgen <bluez-user@schaettgen.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] managing pairing
Date: Sun, 5 Dec 2004 01:59:55 +0100 [thread overview]
Message-ID: <200412050159.55909.bluez-user@schaettgen.de> (raw)
In-Reply-To: <200412030025.02336.wim.delvaux@adaptiveplanet.com>
On Friday 03 December 2004 00:25, wim delvaux wrote:
> another question. I suppose the link_key file can contain link keys to
> multiple remove BT devices (e.g a USB BT dongle and a BT Phone)
>
> I also presume that each link_key is associated to the bdaddress of the
> remote device it relates to.
>
> 1. can the link_key file be browsed to find all the devices a link_key
> exists for
>
> 2. can one 'remove' one such record from the link_key file and assume that
> the pairing will retry once removed (much like removing the link_key file
> completely)
Just for the record and for the KDE users out there:
The KDE Bluetooth Framework just got it's own link key management tool a few
minutes ago, so you can see and remove any paired device without using a hex
editor or deleting the whole link key file now. I just wonder why no one
seemed to miss something like that the whole time.
regards
Fred
--
Fred Schaettgen
bluez-user@schaettgen.de
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-12-05 0:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 23:25 [Bluez-users] managing pairing wim delvaux
2004-12-03 2:57 ` Marcel Holtmann
2004-12-03 3:43 ` wim delvaux
2004-12-03 3:50 ` Marcel Holtmann
2004-12-05 0:59 ` Fred Schaettgen [this message]
2004-12-05 1:36 ` wim delvaux
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=200412050159.55909.bluez-user@schaettgen.de \
--to=bluez-user@schaettgen.de \
--cc=bluez-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.