All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edd Dumbill <edd@usefulinc.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Fredrik Noring <noring@nocrew.org>,
	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: Thu, 29 Jan 2004 15:32:00 +0000	[thread overview]
Message-ID: <1075390320.1269.6.camel@nova> (raw)
In-Reply-To: <1075389771.26729.95.camel@pegasus>

On Thu, 2004-01-29 at 15:22, Marcel Holtmann wrote:
> Hi Edd,
> 
> > Well, these changes would definitely make me much happier.  From a user
> > interface level the user needs some visual feedback whether they're
> > paired or not.  Often "permission denied" means they've forgotten to
> > pair, but we need to find a nice way to tell the user this when it
> > happens.
> 
> but you can't use the link key database for it. The link keys must be
> stored with the highest possible security and this means that they
> should only be readable and writable by root.

OK, I can see this.  But it wouldn't be a violation if hcid maintained a
file with a list of devices with which it was paired?  That's really the
information we're after.  Well, that, and the ability to delete a link
key.

-- Edd

  reply	other threads:[~2004-01-29 15:32 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 [this message]
2004-01-29 18:14               ` Fredrik Noring
2004-01-30 17:45               ` Fredrik Noring
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=1075390320.1269.6.camel@nova \
    --to=edd@usefulinc.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=gnome-bluetooth@usefulinc.com \
    --cc=marcel@holtmann.org \
    --cc=noring@nocrew.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 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.