From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: Thinkpad X31 @ fedora core 2, trying to connect to Nokia 6380i
Date: Sat, 12 Jun 2004 16:48:34 +0200 [thread overview]
Message-ID: <20040612144834.GA12364@gmx.net> (raw)
In-Reply-To: <m3oenr9t1k.fsf@bfnet.com>
On 0, David Wuertele <dave-gnus@bfnet.com> wrote:
> Nicholas> Does appear a pin windows on the mobile display?
>
> No, there was no change on my 6310i display.
> But on my laptop display I got a dialog asking for the PIN.
> Where do I get this mysterious PIN?
> I tried making one up. Then it worked!
>
> Is this PIN stored somewhere? I see a file
>
> /etc/bluetooth/pin
>
> but it doesn't contain the PIN that I typed into the laptop dialog and
> the phone dialog.
No, the PIN is only needed for Pairing bluetooth devices. The
/etc/bluetooth/pin specifies a lasting key you take for every
connection. It is taken instead of the key you insert in the dialog-box
for incoming connections.
The PIN you insert is stored nowhere, but the devices generate a link-key
from the pin and other data, this stored in the /etc/bluetooth/link_key.
nicholas
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-06-12 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 23:47 [Bluez-users] Thinkpad X31 @ fedora core 2, trying to connect to Nokia 6380i David Wuertele
2004-06-10 10:16 ` Nicholas A. Preyss
2004-06-10 18:17 ` [Bluez-users] " David Wuertele
2004-06-12 14:48 ` Nicholas A. Preyss [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=20040612144834.GA12364@gmx.net \
--to=nalp@gmx.net \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox