From: "Marcus C. Gottwald" <gottwald@inf.fu-berlin.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] devices always connect with out asking for PIN even with pairing enabled!
Date: Tue, 11 Sep 2007 18:00:35 +0200 [thread overview]
Message-ID: <20070911160035.GA21014@mi.fu-berlin.de> (raw)
In-Reply-To: <1189523747.12789.25.camel@aeonflux.holtmann.net>
Marcel Holtmann wrote (Tue 2007-Sep-11 17:15:47 +0200):
> You have to run a passkey agent. It takes care of asking for the PIN. A
> passkey agent however must not be interactive. It could always provide a
> default PIN. Write your own one if you need something special.
Note that when a German writes "must not" and it doesn't really
seem to make sense, he usually means "does not have to". This is
due to similar wording (but different meaning) used in the
German language. Same is true for "actual", which is often used
when the intended meaning is "current" or "prevailing".
Cheers, Marcus
-- =
Marcus C. Gottwald =B7 http://www.inf.fu-berlin.de/~gottwald/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-09-11 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 20:06 [Bluez-users] devices always connect with out asking for PIN even with pairing enabled! shanevolpe
2007-09-10 19:10 ` Marcel Holtmann
2007-09-10 19:56 ` shanevolpe
2007-09-10 20:56 ` Marcel Holtmann
2007-09-11 12:12 ` shanevolpe
2007-09-11 15:15 ` Marcel Holtmann
2007-09-11 16:00 ` Marcus C. Gottwald [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=20070911160035.GA21014@mi.fu-berlin.de \
--to=gottwald@inf.fu-berlin.de \
--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