On Mon, Jan 30, 2012 at 2:33 PM, Bastien Nocera <hadess@xxxxxxxxxx> wrote: > Em Mon, 2012-01-30 às 13:42 -0800, Scott James Remnant escreveu: >> > The PIN length hint is also ignored in the current code: >> > + <device type="audio" oui="00:1A:80:" name="CMT-DH5BT" >> pin="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 it > to work with this device. > What generated PIN? Which spec/profile says you have to generate a PIN for this device? How does the user know what PIN has been generated? Do you display the PIN in the UI in any way? Are they expected to confirm the PIN with a remote display? Are they expected to type the PIN into the remote device? Or even the host, perhaps it's displayed there? 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? 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
