On Sun, Mar 30, 2014 at 9:34 PM, Hirenkumar Tandel <hirent@xxxxxxxxxxx> wrote: > > So basically this changes the policy from rejecting pairings when an agent is not registered to accepting them in case it's a just-works pairing? I'm not convinced we want to do such a policy change that relaxes security in this regard. > > Do you have an actual product use case for this? What's the background and reasoning behind it? > > [Hiren]A use case is for chrome book, for user not logged in case, Bluetooth is working at this time, but default-agent is not registered, however user will expect Bluetooth to work for certain simple devices like mouse. > That is NOT a use case that is valid for a Chromebook. We do NOT want to accept random Bluetooth pairings without a user logged in to confirm. Scott -- Scott James Remnant | Chrome OS Systems | keybuk@xxxxxxxxxx | Google -- 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
