On Sun, Jun 29, 2014 at 2:43 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > The biggest problem here is that even if you are trying to be private and doing everything right, the mouse will broadcast your public address every time it tries to reconnect. So thank you Microsoft for forcing us to be trackable. > \o/ (I'd had an open bug to investigate why this mouse wasn't reconnecting, y'all beat me to it) > Now the biggest problem is that with 3.15 and 3.16-rcX kernels we would need to go back to using our identity address for discovery. This means active scanning and it means we are broadcasting our identity address to everybody when trying to find this mouse. I rather not do that. > I think we would rather just document that this mouse isn't going to reconnect, since you can at least use the UI to reconnect by hand. Switching back to active scanning on the identity address would make our devices trackable, which is very definitely not on our wish list. 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
