From: wim delvaux <wim.delvaux@adaptiveplanet.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] managing pairing
Date: Fri, 3 Dec 2004 04:43:52 +0100 [thread overview]
Message-ID: <200412030443.52876.wim.delvaux@adaptiveplanet.com> (raw)
In-Reply-To: <1102042677.7350.31.camel@pegasus>
On Friday 03 December 2004 03:57, Marcel Holtmann wrote:
> Hi Wim,
>
> > 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.
> >
> > so
> >
> > 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)
>
> there were plans to move this file into a text file, but no code has
> been written so far. However you can do your modification by hand, but
> at the moment after each change the hcid must be restarted.
restarting is doable.
If I understand properly, the file is binary. Can you point me to the
source file where the IO to the link_key file is written ? For the time being
I could use that code to load the link_key file and later use the proper
ASCII format.
W
>
> 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://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
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-03 3:43 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 [this message]
2004-12-03 3:50 ` Marcel Holtmann
2004-12-05 0:59 ` Fred Schaettgen
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=200412030443.52876.wim.delvaux@adaptiveplanet.com \
--to=wim.delvaux@adaptiveplanet.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox