From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] D-Bus support
Date: Sun, 08 Feb 2004 22:07:25 +0100 [thread overview]
Message-ID: <1076274445.14742.73.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <1076267396.2670.58.camel@pegasus>
Hi Marcel
On Sun, 2004-02-08 at 20:09, Marcel Holtmann wrote:
> I already looked at your stuff. Nice work btw.
Thanks!
> At the moment I am more concerned on how the D-Bus interface should
> look like than a real implementation.
I will send you the interface proposal in another e-mail. It's largely
implemented and used by the Gnome Bluetooth Configuration tool already,
but it's possible to modify of course.
> You now that an important part for me is the security. For example a
> user can see what devices a paired and it can delete a pairing, but
> it don't have to see the link key itself. This is the job of the
> daemon that provides this interface. The same applies for changing
> device settings and storing them on the harddisk.
I agree. This is the way the new proposed hcid is implemented.
> My favourite storage is Berkeley DB.
That's an interesting idea, you mentioned that before. Can you
elaborate, please?
Here are some advantages of using textfiles (as default) for hcid
storage:
1. Textfiles are intuitive to use and debug because they work
with any tool (emacs, grep, awk, perl etc.)
2. Small to medium size storage files have always been text
files in Unix/Linux (/etc/passwd, /etc/hosts etc.)
3. Textfile routines are very lightweight and efficient.
Please understand that although it does work, applications should
use the DBus interface instead of manipulating these files directly.
Here's how it's implemented in the proposed hcid. The default location
of these files is something to discuss. File layout:
$ ls -l /etc/bluetooth/keytab*
-rw-r--r-- 1 root root 98 Feb 8 18:29 /etc/bluetooth/keytab
-rw-r--r-- 1 root root 147 Feb 8 16:56 /etc/bluetooth/keytab-
-rw------- 1 root root 138 Feb 8 18:29 /etc/bluetooth/keytab.shadow
-rw------- 1 root root 207 Feb 8 16:56 /etc/bluetooth/keytab.shadow-
$ ls -l /etc/bluetooth/nametab*
-rw-r--r-- 1 root root 115 Feb 8 16:00 /etc/bluetooth/nametab
-rw-r--r-- 1 root root 86 Feb 8 15:02 /etc/bluetooth/nametab-
The dash files ("keytab-" etc.) are backup files. The "keytab" file is
readable by all. The "keytab.shadow" is only r/w-able by root. Contents:
$ cat /etc/bluetooth/keytab
# sba dba type create time
00:03:C9:2A:C4:A8 00:07:E0:0C:1B:3F 0 1076252948
00:10:DC:E9:EF:20 00:80:37:AA:7A:DA 0 1076253156
$ cat /etc/bluetooth/keytab.shadow
# sba dba key
00:03:C9:2A:C4:A8 00:07:E0:0C:1B:3F 2f66d0364a1eea2fae680af948bb3299
00:10:DC:E9:EF:20 00:80:37:AA:7A:DA 2855bdc30b49254902d5deebe24c24ce
$ cat /etc/bluetooth/nametab
# bdaddr name
00:00:08:04:DE:C8 Fuzz Buzz
00:80:37:AA:7A:DA Fredrik T39
00:07:E0:0C:1B:3F Fredrik TT
Fredrik
next prev parent reply other threads:[~2004-02-08 21:07 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 18:35 [Bluez-devel] D-Bus support Marcel Holtmann
2004-02-08 18:51 ` Fredrik Noring
2004-02-08 19:09 ` Marcel Holtmann
2004-02-08 21:07 ` Fredrik Noring [this message]
2004-02-08 22:04 ` Marcel Holtmann
2004-02-08 22:33 ` Fredrik Noring
2004-02-08 21:28 ` [Bluez-devel] D-Bus interfaces Fredrik Noring
2004-02-08 21:54 ` Marcel Holtmann
2004-02-08 22:15 ` Fredrik Noring
2004-02-08 22:31 ` Marcel Holtmann
2004-02-08 22:50 ` Fredrik Noring
2004-02-08 23:19 ` Marcel Holtmann
2004-02-08 23:51 ` Fredrik Noring
2004-02-09 0:38 ` Marcel Holtmann
2004-02-09 7:22 ` Fredrik Noring
2004-02-09 10:06 ` Marcel Holtmann
2004-02-09 10:22 ` Fredrik Noring
2004-02-09 10:38 ` Marcel Holtmann
2004-02-09 10:46 ` Fredrik Noring
2004-02-09 11:03 ` Marcel Holtmann
2004-02-09 11:53 ` Fredrik Noring
2004-02-09 13:01 ` Marcel Holtmann
2004-02-09 13:23 ` Fredrik Noring
2004-02-09 15:46 ` Marcel Holtmann
2004-02-09 16:05 ` Fredrik Noring
2004-02-09 16:30 ` Marcel Holtmann
2004-02-09 17:04 ` Fredrik Noring
2004-02-11 10:03 ` Fredrik Noring
2004-02-11 13:32 ` Marcel Holtmann
2004-02-11 14:05 ` Fredrik Noring
2004-02-11 16:45 ` Marcel Holtmann
2004-02-11 22:00 ` Fredrik Noring
2004-02-11 22:29 ` Marcel Holtmann
2004-02-11 22:33 ` Fredrik Noring
2004-02-11 12:32 ` Fredrik Noring
2004-02-11 13:28 ` Marcel Holtmann
2004-02-11 14:35 ` Fredrik Noring
2004-02-11 17:05 ` Marcel Holtmann
2004-02-11 22:25 ` Fredrik Noring
2004-02-11 22:42 ` Marcel Holtmann
2004-02-11 22:57 ` Fredrik Noring
2004-02-11 23:14 ` Marcel Holtmann
2004-02-11 23:29 ` Fredrik Noring
2004-02-11 23:36 ` Marcel Holtmann
2004-02-11 23:41 ` Fredrik Noring
2004-02-11 23:46 ` Marcel Holtmann
2004-02-08 23:15 ` Fred Schättgen
2004-02-16 14:46 ` Phil Blundell
2004-02-16 15:36 ` Marcel Holtmann
2004-02-16 15:41 ` Phil Blundell
2004-02-17 22:59 ` Marcel Holtmann
2004-02-17 23:38 ` Philip Blundell
2004-02-17 23:44 ` Marcel Holtmann
2004-02-17 23:49 ` Philip Blundell
2004-02-17 23:57 ` Marcel Holtmann
2004-02-18 0:08 ` Philip Blundell
2004-02-18 0:17 ` Marcel Holtmann
2004-02-18 0:29 ` Philip Blundell
2004-02-19 15:55 ` Fredrik Noring
2004-02-19 16:01 ` Fredrik Noring
2004-02-19 15:52 ` Fredrik Noring
2004-02-19 16:48 ` Phil Blundell
2004-02-20 4:04 ` 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=1076274445.14742.73.camel@akka.yeti.nocrew.org \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
--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