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?
Attila
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
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
[email protected]
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
>the link key is always 16 bytes / 128 bits long. Even Windows can"t
> change this.
>
> Regards
>
> Marcel
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
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Devices\08:00:1f:51:d1:e9\0]
"ServiceNameUTF8"=hex:53,65,72,69,61,6c,20,50,6f,72,74,00
"ServiceNameNative"=hex:53,65,72,69,61,6c,20,50,6f,72,74,00
"UUID"=dword:00001101
"Security"=dword:00000000
"DefaultConnection"=dword:00000000
How can it be 16 bytes long? How can it be decoded or which part should
I use?
Attila
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
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
[email protected]
Hi Attila,
> 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?
the link key is always 16 bytes / 128 bits long. Even Windows can't
change this.
Regards
Marcel
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users