* Re: [Bluez-users] Re: [Bluez-devel] DB aliases (wishlist) @ 2003-04-25 15:49 Max Krasnyansky 0 siblings, 0 replies; 2+ messages in thread From: Max Krasnyansky @ 2003-04-25 15:49 UTC (permalink / raw) To: bluez-devel At 12:56 AM 4/9/2003, David Woodhouse wrote: >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. Yep. I had something similar in mind. >/etc/bluetooth/paired_devices and /etc/bluetooth/paired_devices.shadow, anyone? :) /etc/bluetooth/ neighbours (world readable) - <bdaddr>, <name>, <last seen>, etc security - <bdaddr>, <pin code>, <link key> Max ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <20030404072437.GD8317@wacka.mjr.org>]
[parent not found: <1049751844.11258.31.camel@pegasus.local>]
* Re: [Bluez-devel] DB aliases (wishlist) [not found] ` <1049751844.11258.31.camel@pegasus.local> @ 2003-04-09 7:56 ` David Woodhouse 2003-04-24 22:42 ` [Bluez-users] " Max Krasnyansky 0 siblings, 1 reply; 2+ messages in thread From: David Woodhouse @ 2003-04-09 7:56 UTC (permalink / raw) To: Marcel Holtmann; +Cc: Paul Hedderly, BlueZ Mailing List, BlueZ Mailing List 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-users] Re: [Bluez-devel] DB aliases (wishlist) 2003-04-09 7:56 ` David Woodhouse @ 2003-04-24 22:42 ` Max Krasnyansky 0 siblings, 0 replies; 2+ messages in thread From: Max Krasnyansky @ 2003-04-24 22:42 UTC (permalink / raw) To: David Woodhouse, Marcel Holtmann; +Cc: Paul Hedderly, BlueZ Mailing List At 12:56 AM 4/9/2003, David Woodhouse wrote: >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. Yep. I had something similar in mind. >/etc/bluetooth/paired_devices and /etc/bluetooth/paired_devices.shadow, anyone? :) /etc/bluetooth/ neighbours (world readable) - <bdaddr>, <name>, <last seen>, etc security - <bdaddr>, <pin code>, <link key> Max ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-04-25 15:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-25 15:49 [Bluez-users] Re: [Bluez-devel] DB aliases (wishlist) Max Krasnyansky
[not found] <20030404072437.GD8317@wacka.mjr.org>
[not found] ` <1049751844.11258.31.camel@pegasus.local>
2003-04-09 7:56 ` David Woodhouse
2003-04-24 22:42 ` [Bluez-users] " Max Krasnyansky
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox