Linux bluetooth development
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: Paul Hedderly <bulkpaul@mjr.org>,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] DB aliases (wishlist)
Date: Wed, 09 Apr 2003 08:56:00 +0100	[thread overview]
Message-ID: <1049874960.31462.20.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <1049751844.11258.31.camel@pegasus.local>

On Mon, 2003-04-07 at 22:43, Marcel Holtmann wrote:
> So this is a basic request to all of you. What do you want to see in the
> next version of the BlueZ utils?

Link key management.

hcitool lk list [<dev>|<bdaddr>] [<bdaddr>]
hcitool lk remove [<dev>|<bdaddr>] <bdaddr>...
hcitool lk add [<dev>|<bdaddr>] <bdaddr> <key>
hcitool lk merge <filename>

See xauth :)

I'm tired of manually copying link keys from /etc/bluetooth/link_key
from one machine to another when I move the CF Bluetooth card. I want to
be able to 'hcitool lk list | ssh ipaq hcitool lk merge -' ;)

OK, so buying another card would also help, but even so we do need at
least the 'hcitool lk remove' functionality and 'lk list' would be very
useful too.

As previously discussed, it would be nice if non-root users could see
the results of 'lk list' without the actual keys -- basically just a
list of devices with which we're paired.

/etc/bluetooth/paired_devices and /etc/bluetooth/paired_devices.shadow,
anyone? :)

-- 
dwmw2

       reply	other threads:[~2003-04-09  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030404072437.GD8317@wacka.mjr.org>
     [not found] ` <1049751844.11258.31.camel@pegasus.local>
2003-04-09  7:56   ` David Woodhouse [this message]
2003-04-24 22:42     ` [Bluez-users] Re: [Bluez-devel] DB aliases (wishlist) Max Krasnyansky

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=1049874960.31462.20.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=bulkpaul@mjr.org \
    --cc=marcel@rvs.uni-bielefeld.de \
    /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