Re: RFA: Implementing HID spec recommendation for Keyboard PINs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 18, 2012 at 2:56 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote:

> Hi Scott,
>
Hi Johan,

> On Wed, Jan 18, 2012, Scott James Remnant wrote:
>> The Bluetooth HID profile recommends (4.1, p24) that rather than
>> prompting the user for a PIN on the host, which then needs to be
>> entered into the connecting keyboard, instead the host simply generate
>> the PIN and display it to the user instead. Part of this will be
>> implemented as a plugin, but since UI is involved, the Agent is
>> involved as well. As far as I can tell, there are two options:
>>
>>
> 3) Keep using RequestPinCode and have let the agent be responsible for
> generating and showing a PIN to the user which is immediately sent as a
> reply to the agent callback (while the UI prompt remains).
>

Marcel has specifically instructed me not to do that, stating that the
Agent is not supposed to be "smart" like this but only to directly
interact with the user.

See http://thread.gmane.org/gmane.linux.bluez.kernel/20391 yesterday

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux