Hi Scott, > Since the specification allows the PIN to be a sequence of arbitrary > octets, and not a UTF-8 string, allow the userspace agent to reply > with such a sequence (as a D-Bus Array of Bytes). > > This means a userspace agent can deal with devices that require their > BD_ADDR (or the host's) as a PIN, and take care of trying multiple of > such requirements. this has been discussed before and the answer is a clear no to this. You can however write a plugin that can handle binary PIN codes. Regards Marcel -- 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
