From: Fred Schaettgen <bluez-user@schaettgen.de>
To: bluez-users@lists.sourceforge.net
Cc: Attila Zsigmond <mail@backend-wizard.com>
Subject: Re: [Bluez-users] Transfer link key from/to windows
Date: Fri, 29 Apr 2005 20:10:42 +0200 [thread overview]
Message-ID: <200504292010.42625.bluez-user@schaettgen.de> (raw)
In-Reply-To: <200504291858.19965@ByZsA>
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
On Friday, 29. April 2005 18:58, Attila Zsigmond wrote:
> Hello,
>
> I have a dual boot PC and I want to connect it to my mobile phone via
> bluetooth. Currently I need enter the pin code each time if I boot the
> other operating system. I know where the link key is in my linux and
> could export link key from windows registry. But I cannot replace them
> each other because they have different length. On linux key is 16 bytes
> length while on windows it is 128. Can bluez be configured to create
> longer link keys? Any other idea?
Maybe you can use the attached script as a starting point, which I just
rescued from the deepest depths of my harddisk. It's supposed to transfer
link keys from Linux to Windows.
It's highly unlikely that it works as is, and I didn't touch it since quite a
while since I don't have a windows installation atm. At least one problem I
remember was that the acl of some registry key had to be changed manually
before applying the inf-file, because not even an admin can change (or even
see?) it by default. I'm quite sure that it's possible to change this with
some inf-file magic, but I didn't feel motivated enough to investiagte
further and finally abandoned the whole thing in an unknown state.
All I can promise is that it generates some sort of inf file from the
link_keys file which you can apply under windows. I even can't remember if it
ever worked. It's for the XP stack, not for Widcomm btw. Maybe you or someone
else is motivated enough to make this work.
Fred
--
Fred Schaettgen
bluez-devel@schaettgen.de
[-- Attachment #2: bt_export_linkkeys --]
[-- Type: application/x-python, Size: 2644 bytes --]
next prev parent reply other threads:[~2005-04-29 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 16:58 [Bluez-users] Transfer link key from/to windows Attila Zsigmond
2005-04-29 17:14 ` Marcel Holtmann
2005-04-29 18:10 ` Fred Schaettgen [this message]
2005-04-29 21:07 ` Attila Zsigmond
2005-04-29 23:28 ` Fred Schaettgen
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=200504292010.42625.bluez-user@schaettgen.de \
--to=bluez-user@schaettgen.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=mail@backend-wizard.com \
/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