Re: [RFC PATCHv2] autopair: add autopair plugin

On Mon, Jan 30, 2012 at 3:03 PM, Bastien Nocera [off-list ref] wrote:

Em Mon, 2012-01-30 =E0s 14:35 -0800, Scott James Remnant escreveu:

quoted

On Mon, Jan 30, 2012 at 2:33 PM, Bastien Nocera [off-list ref] wrot=

e:

quoted

quoted

Em Mon, 2012-01-30 =E0s 13:42 -0800, Scott James Remnant escreveu:

quoted

quoted

The PIN length hint is also ignored in the current code:
+ =A0 =A0 =A0 <device type=3D"audio" oui=3D"00:1A:80:" name=3D"CMT-=

DH5BT"

quoted

quoted

quoted

pin=3D"max:4"/>

quoted

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 it
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.

Recommended where? Can you point at least at the correct document?

The only recommendation I'm aware of is in the HID profile, which
would not apply here, and strangely you don't use this max: form for
keyboards which would be the only devices they applied to.


The description matches the HID profile behavior I've sumitted as a
separate set of CLs.

Scott
--=20
Have you ever, ever felt like this?
Had strange things happen? =A0Are you going round the twist?