Linux bluetooth development
 help / color / mirror / Atom feed
From: Fredrik Noring <noring@nocrew.org>
To: Edd Dumbill <edd@usefulinc.com>, Marcel Holtmann <marcel@holtmann.org>
Cc: GNOME Bluetooth Mailing List <gnome-bluetooth@usefulinc.com>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [gnome-bluetooth] What stuff in gnome-bluetooth does, and ideas for its future
Date: Fri, 30 Jan 2004 18:45:59 +0100	[thread overview]
Message-ID: <1075484759.14644.10.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <1075390320.1269.6.camel@nova>

Edd and Marcel,

tor 2004-01-29 klockan 16.32 skrev Edd Dumbill:
> Well, that, and the ability to delete a link key.

Here's a nice solution I think:

Make hcid create a socket in /etc/bluetooth/keytab.socket. Preferably,
having the same group membership as the socket (for examle "bluetooth")
enables a user to send commands like:

    DELETE <sba> <dba>

This makes hcid delete the link and update /etc/bluetooth/keytab and
/etc/bluetooth/keytab.shadow accordingly. These are ASCII files of
course and can also be maintained with Emacs or whatever tool although
this is not as safe because of race conditions.

Then we'll extend hcitool with the ability to connect to this socket
and do this stuff too.

The protocol can be extended in the future. Like for example initiating
pairing procedures and so on.

What do you think?

Fredrik

  parent reply	other threads:[~2004-01-30 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1064593223.12843.127.camel@saag>
     [not found] ` <1067882864.15593.326.camel@dhcp-116.surrey.redhat.com>
     [not found]   ` <1067906859.15607.48.camel@saag>
2004-01-28 23:04     ` [gnome-bluetooth] What stuff in gnome-bluetooth does, and ideas for its future Fredrik Noring
2004-01-29  0:50       ` Fredrik Noring
2004-01-29 11:09         ` Edd Dumbill
2004-01-29 15:22           ` Marcel Holtmann
2004-01-29 15:32             ` Edd Dumbill
2004-01-29 18:14               ` Fredrik Noring
2004-01-30 17:45               ` Fredrik Noring [this message]
2004-01-30 18:18                 ` Marcel Holtmann
2004-01-30 20:31                   ` Fredrik Noring
2004-01-29 11:30         ` [Bluez-devel] " Fred Schättgen
2004-01-29 18:44           ` Fredrik Noring
2004-01-29 20:19             ` [Bluez-devel] " Fred Schättgen
2004-01-30 18:10               ` [gnome-bluetooth] " Fredrik Noring
2004-01-30 18:26                 ` Marcel Holtmann
2004-01-30 18:49                   ` Eugene Crosser
2004-01-30 19:06                     ` Marcel Holtmann
2004-01-30 20:41                     ` Fredrik Noring
2004-01-30 20:35                   ` Fredrik Noring
2004-01-30 18:49                 ` [Bluez-devel] name cache Fred Schättgen
2004-01-30 20:54                   ` Fredrik Noring

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=1075484759.14644.10.camel@akka.yeti.nocrew.org \
    --to=noring@nocrew.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=edd@usefulinc.com \
    --cc=gnome-bluetooth@usefulinc.com \
    --cc=marcel@holtmann.org \
    /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