On 10/9/2014, 3:48, Paul Theriault wrote:
Other options for user authentication I had been thinking about were:
- pairing the phone with the computer it is going to be plugged into - maybe
via adb (maybe by use of 842747) or wifi (with upcoming wifi debugging)
- Ship phones with “developer NFC sticker” - basically an NFC tag which is
proof of ownership (only works for NFC devices obviously)
- Pair the phone with a computer via bluetooth during FTU. Access to developer
options later requires you to pair to the computer again
Of these options I dislike 1 and 3 because (a) you may not have a
computer handy at the time and (b) you may have a different computer
later when you actually want to enable the os-developer mode. I like
option (2) more. In the case of non-NFC devices (or even for NFC
devices) you could just ship phones with a separate unique PIN code to
activate developer mode. If the users lose this they can recover it by
calling their carrier and authenticating themselves via the regular
carrier authentication channel. Users who buy the phone without a
carrier plan are likely to be developers or savvy enough to realize they
should hang on to the code.
kats
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
