public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Kenyon <simon@koala.ie>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Passkey-Agent for bluez 4.xx
Date: Wed, 17 Jun 2009 13:17:37 +0100	[thread overview]
Message-ID: <4A38DEE1.2080707@koala.ie> (raw)
In-Reply-To: <20090617073831.GA9544@jh-x301>

Johan Hedberg wrote:
> Most of the times I've heard people requesting this feature it has turned
> out that they didn't understand what pairing is and what role the PIN
> plays in it. The purpose of pairing is to create a common link key between
> two devices. The link key can also be reused in later connections to avoid
> pairing again. The purpose of the pin is to act as a one-time input in
> this pairing process to create the common link key. It is the link key
> that you want permanently stored so you don't need to repair when
> connecting later, and bluez already does this for you.
>
> So, the value of having a fixed PIN somewhere in the system is in most
> cases rather low since pairing is an infrequent event after which the
> generated link key is used to establish secure connections between the
> devices. Having a fixed PIN has also the security implication that anyone
> who knows your address can create a pairing with you without any knowledge
> of the local user. However, bluez doesn't want to define or enforce rules
> for where the PIN comes from. Instead, bluez externalizes the whole
> process using the agent concept so you are free to have whatever kind of
> mechanism you want (e.g. reading the PIN from the filesystem) for replying
> to PIN requests.
>   
maybe it is because the documentation is a little, how can i put it, light
--
simon

  reply	other threads:[~2009-06-17 12:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 15:48 Passkey-Agent for bluez 4.xx Artem Makhutov
2009-05-14  4:46 ` Brad Midgley
2009-05-16 14:52   ` Artem Makhutov
2009-06-16 13:07   ` John Frankish
2009-06-16 14:30     ` Timothy Murphy
2009-06-17  7:38       ` Johan Hedberg
2009-06-17 12:17         ` Simon Kenyon [this message]
2009-06-16 19:21     ` Artem Makhutov
2009-06-17  4:14       ` John Frankish
2009-06-17  7:12         ` Johan Hedberg
2009-06-17 14:15           ` John Frankish
2009-06-17 15:35             ` Brad Midgley
2009-06-17  6:27     ` Brad Midgley
2009-06-17 14:15       ` John Frankish
  -- strict thread matches above, loose matches on Subject: below --
2009-05-13 15:55 Artem Makhutov
2009-05-18 19:21 Wilson, Scott
2009-05-18 19:52 ` James Le Cuirot
2009-05-18 21:53   ` Wilson, Scott
2009-05-18 22:16     ` Marcel Holtmann
2009-05-18 22:20     ` tmm

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=4A38DEE1.2080707@koala.ie \
    --to=simon@koala.ie \
    --cc=linux-bluetooth@vger.kernel.org \
    /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