From: Fred Schaettgen <bluez-devel@schaettgen.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Support for stored link keys
Date: Sun, 24 Apr 2005 20:12:09 +0200 [thread overview]
Message-ID: <200504242012.10067.bluez-devel@schaettgen.de> (raw)
In-Reply-To: <1114101950.32265.40.camel@pegasus>
On Thursday, 21. April 2005 18:45, Marcel Holtmann wrote:
> > > 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?
> >
> > This would be cool :)
>
> Exists any tool or library that allows to read the Windows registry
> directly from Linux if the filesystem is mounted?
What I tried a while ago was to export BlueZ link keys to reuse them with
Microsoft's bluetooth stack. The idea was to write a .inf-file under Linux,
which can later be applied under windows to put the link key into the
registry. IIRC it was basically working, but I didn't include into the KDE
link key manager so far, because I had to change permission of some keys and
I didn't know how to do that in an inf file.
The same approach should work for the Widcomm stack, too. It's not fully
automatic, but it would be flexible and safe.
It should also be easy to write a small windows tool to extract the contents
of the windows bluetooth stack to use it with BlueZ. Extracting it directly
under Linux would be more efficient, but I don't think it's worth the effort.
It won't hurt much if windows had to be started to transfer link keys. It's
meant for Windows/Linux dual boot users anyway.
Fred
--
Fred Schaettgen
bluez-devel@schaettgen.de
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-24 18:12 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
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 [this message]
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=200504242012.10067.bluez-devel@schaettgen.de \
--to=bluez-devel@schaettgen.de \
--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.