All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Support for stored link keys
Date: Thu, 21 Apr 2005 18:07:24 +0200	[thread overview]
Message-ID: <1114099644.32265.31.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.61.0504211721020.15599@cherokee.spacecom.si>

Hi Mitja,

> I use at least 3 dongles and so I implemented profiles for each one, simmilar 
> to alternatives, so each profile has a directory in /etc/bluetooth/profiles and
> script softlinks files to /etc/bluetooth and this solved my issues, when 
> connecting with different dongles, but it did not solve issues regarding 
> linkkeys in windows. 

I don't know for what this is needed. The current hcid stores the link
keys now under /var/lib/bluetooth and it uses a subdirectory with the
text representation of the BD_ADDR to differ between adapters.

However even the previous hcid was able to store link keys for different
dongles and you can also use profiling inside the hcid.conf. For example
I use something like this to name all my development dongles.

	device 00:02:xx:xx:xx:xx {
	        name "Casira BC4";
	}

	device 00:0B:xx:xx:xx:xx {
	        name "3Com USB dongle";
	}

> Your idea is great, would love to see it, and I would store all linkkeys 
> which device ever created, if it is possible to add them later on chip.
> But I think this would not solve my problem with multiple dongles, as I 
> would still need to use profiles, as each dongle would still need it's own 
> list, right? 

There is no problem or I don't understand what you mean. However the
space for stored link keys on the chip is limited. I think that max for
CSR based chips is 20.

> Do you have any other sollution to this, or what do you think of 
> inclusion of profiles for each device? Do you know how widcomm stack store 
> linkkeys, in registry? Would it be possible to use same linkkey in both 
> OSes?

The Widcomm stack stores it somewhere in the Registry and actually I
like to see a program that can read these keys from the Registry if the
Windows root partition is mounted. Anyone?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-04-21 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 14:46 [Bluez-devel] Support for stored link keys Marcel Holtmann
2005-04-21 15:55 ` Mitja Pufic
2005-04-21 16:07   ` Marcel Holtmann [this message]
2005-04-21 16:34     ` Mitja Pufic
2005-04-21 16:45       ` Marcel Holtmann
2005-04-22 22:26         ` Scott W Gifford
2005-04-22 22:55           ` Henryk Plötz
2005-04-23  0:00             ` Marcel Holtmann
2005-04-24 18:12         ` Fred Schaettgen
2005-04-21 16:37     ` Mitja Pufic
2005-04-28 18:28 ` David Woodhouse
2005-04-29  9:37   ` Marcel Holtmann

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=1114099644.32265.31.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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.