1037138 - Consistent remote debugging security policies

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Developer Tools, defect)

Description

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

We're working towards adding WiFi debugging.  In bug 1033079 comment 14, :pauljt mentioned we should strive for consistent security policies for WiFi and other transports:

(In reply to Paul Theriault [:pauljt] from comment #14)
> I would like us to apply security requirements consistently though, which
> might be a seperate discussion. Currently we have a number of security
> controls on adb-based remote debugging that are implemented by
> enabling/disabling adb - I thinking that we should do the same when it comes
> to opening up ports for listening/responding to multicast pings.  
> 
> - We currently disable adb whenever the phone is locked on production
> devices. Can we do the same wireless debugging (i.e close the port/don't
> respond to pings when the phone is locked)
> - We currently disable remote debugging after a period of no connections (12
> hours I believe). I'd recommend we do the same for wireless connections
> 
> I know this is pain point for some developers (jryans pointed me to bug
> 1032128), so maybe we want UI to be able to disable these controls, but I
> feel like whatever we do, we should be consistent across both.

Comment 1

[BMO Automation]

Firefox OS is not being worked on