From: Bastien Nocera <hadess@hadess.net>
To: Scott James Remnant <scott@netsplit.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, keybuk@chromium.org
Subject: Re: [RFC PATCHv2] autopair: add autopair plugin
Date: Mon, 30 Jan 2012 23:03:39 +0000 [thread overview]
Message-ID: <1327964619.2125.14.camel@sirocco.config> (raw)
In-Reply-To: <CA+bD78hQcBm5-94RHNSPXUsM1kAD8pYJ5Yu=-jPv8T=iedr6bA@mail.gmail.com>
Em Mon, 2012-01-30 =C3=A0s 14:35 -0800, Scott James Remnant escreveu:
> On Mon, Jan 30, 2012 at 2:33 PM, Bastien Nocera <hadess@hadess.net> wro=
te:
> > Em Mon, 2012-01-30 =C3=A0s 13:42 -0800, Scott James Remnant escreveu:
> >> > The PIN length hint is also ignored in the current code:
> >> > + <device type=3D"audio" oui=3D"00:1A:80:" name=3D"CMT-DH5BT=
"
> >> pin=3D"max:4"/>
> >> >
> >> Because that's a UI restriction, no?
> >>
> >> I didn't put any PIN-generation code here, because I'm not entirely
> >> sure what the UI for "generate random PIN' should look like or which
> >> spec you're following.
> >
> > It means that a generated PIN shouldn't have more than 4 digits for i=
t
> > to work with this device.
> >
> What generated PIN? Which spec/profile says you have to generate a PIN
> for this device?
It's recommended that the UIs try to generate PINs for the users, rather
than relying on them entering random numbers.
> How does the user know what PIN has been generated?
You will display it to them.
> Do you display the PIN in the UI in any way?
Yep, in the UI, because that's the PIN you will have to enter on the devi=
ce.
> Are they expected to confirm the PIN with a remote display?
Not confirm, but enter.
> Are they expected to type the PIN into the remote device? Or even the
> host, perhaps it's displayed there?
They're supposed to enter it. The device is a Hi-Fi with Bluetooth
functionality:
http://www.sony.co.uk/support/en/product/CMT-DH5BT
You have a UI to enter the PIN but it will only allow you to enter 4
digits. So any number longer than 4 digits will fail to pair.
> Or do these devices simply just accept any PIN without question? In
> which case, why does it matter whether you send a random PIN or 0000?
It doesn't.
next prev parent reply other threads:[~2012-01-30 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 23:47 [RFC PATCHv2] autopair: add autopair plugin Scott James Remnant
2012-01-30 19:49 ` Marcel Holtmann
2012-01-30 20:05 ` Bastien Nocera
2012-01-30 21:42 ` Scott James Remnant
2012-01-30 22:33 ` Bastien Nocera
2012-01-30 22:35 ` Scott James Remnant
2012-01-30 23:03 ` Bastien Nocera [this message]
2012-01-30 23:10 ` Scott James Remnant
2012-02-15 17:57 ` David Herrmann
2012-02-15 19:18 ` Scott James Remnant
2012-01-30 21:40 ` Scott James Remnant
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=1327964619.2125.14.camel@sirocco.config \
--to=hadess@hadess.net \
--cc=keybuk@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=scott@netsplit.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;
as well as URLs for NNTP newsgroup(s).