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: Sat, 30 Apr 2005 01:28:40 +0200 [thread overview]
Message-ID: <200504300128.41156.bluez-user@schaettgen.de> (raw)
In-Reply-To: <200504292307.25245@ByZsA>
On Friday, 29. April 2005 23:07, Attila Zsigmond wrote:
...
> Hmmm... Thank you, Marcel. I know that this list is not about MS windows
> but maybe somebody can help. Here is the link key exported from XP
> registry:
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Devices\08:00:1f:51:d1:e9]
> "Name"=hex:57,69,6c,64,72,6f,73,65,00
> "DevClass"=hex:50,02,04
> "Features"=hex:ef,ff,0b,00,00,00,00,00
> "TimeStamp"=dword:0000329d
> "FTPAuthorizationExpires"=hex:00
> "OPPAuthorizationExpires"=hex:00
> "TrustedMask"=dword:00000000
> "LinkKey"=hex:80,00,00,00,4c,00,00,00,01,02,00,00,02,66,00,00,00,a4,00,00,84
> e1,7a,fe,7f,da,a6,51,87,b1,b7,1e,19,cc,cd,ea,fe,f7,b5,88,57,33,15,27,91,f8,
> c9,db,74,00,59,64,ff,9f,8b,3c,a0,fb,01,ba,52,7c,f3,28,94,b1,54,52,a4,30,42,
> 6a,90,9f,55,40,a8,62,af,5c,60,7e,1f,92,28,00,00,00,15,86,a6,99,9b,53,e6,6c,
> a3,8e,06,77,c5,4d,3e,9a,17,70,8d,6b,06,40,19,88,fb,6b,d6,9f,8f,ef,77,3d,23,
> 0f,99,cc,c7,d0,1d,cb
...
> How can it be 16 bytes long? How can it be decoded or which part should
> I use?
I guess the "LinkKey" registry key contains simply a little bit more than just
the link key itself. If you have both a windows and a linux system you might
try pairing the windows box with the linux system. Then have a look at the
link_keys file with a hex editor to find matching parts. The beginning of the
"LinkKey" doesn't look very linkkey-like.
Is 08:00:1f:51:d1:e9 the adaptor's adress or is it the address of the peer
device? In any case, where is the other address stored? Or does the Widcomm
stack support only a single adaptor?
Fred
--
Fred Schaettgen
bluez-devel@schaettgen.de
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-04-29 23:28 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
2005-04-29 21:07 ` Attila Zsigmond
2005-04-29 23:28 ` Fred Schaettgen [this message]
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=200504300128.41156.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