On 09/09/2014 16:25, Dale Harvey wrote:

> Even in development builds but particularly with user builds adb access
> to the device is extremely flakey and I routinely have to go into
> fastboot mode to reflash my entire device, like if I push a syntax error
> in the system app in a user build then adb will never be reenabled.
> 


Sounds like an issue unrelated with security decisions, but I see your
point. To understand a bit more the UX flow: if you flash your phone,
then either

1) you have a standard build, and you have to go through the FTU. You
can then enable the 'os-developer' mode without having to add too much
steps (well, this is a matter of discussion of course). And since I'm
not sure if it was stated clearly enough in the first email: you would
need to go through this procedure only once, should you remember the PIN
code you set the first time.

2) or you flash your custom builds, in which case maybe it would be
possible to set a pref to enable os-developer mode by default if you
already configured it to skip the FTU, activate adb, etc?


> Having to do a factory reset, or as was mentioned in the google doc sign
> up to some firefox online account seems straight up developer hostile to me.
> 

The thing is, if the use case is a developer who is often flashing his
device to do testing or development, then the security risk related to
(security sensitive) data loss is pretty low, imho.
But if you're an attacker or a lambda user deciding to turn your
everyday phone into the os-developer mode (which currently is done
through the same routine of stopping/starting b2g via adb and setting a
pref, assuming you have a rooted device), then it's another story.


As a side note, for people debugging with the help of the App
Manager/WebIDE, the devtools team is working on implementing remote
debugging over Wi-Fi (without using adb at all) [1] .

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=962308
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to