Closed
Bug 725513
Opened 13 years ago
Closed 12 years ago
Enable logging of sensitive information in Nightly
Categories
(Firefox for Android Graveyard :: Android Sync, defect, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rnewman, Unassigned)
Details
That'll do for now, until we can address Bug 725030 and Bug 725082.
(And of course, make sure that everything we don't want to log is a trace item!)
Comment 1•13 years ago
|
||
I did some testing with the following code
System.setProperty("log.tag." + TAG, "" + Log.ERROR);
Log.v(TAG, "testing verbose");
Log.e(TAG, "testing error");
The call to Log.v() still logs even though the log is set to only log for ERROR and above. If I wrap the Log.v() call with
if (Log.isLoggable(TAG, Log.VERBOSE)) {
Log.v(TAG, "testing verbose");
}
then nothing is logged...
Reporter | ||
Comment 2•13 years ago
|
||
Yeah, I've got a utility method to do these checks.
Reporter | ||
Comment 3•13 years ago
|
||
Let's flip this around after Bug 725525. Trace logging is off by default, but controlled by the VERBOSE system setting.
The logging of sensitive information is hard-coded to off.
Summary: Disable trace logging in Beta and Release → Enable logging of sensitive information in Nightly
Reporter | ||
Updated•13 years ago
|
Priority: -- → P4
Comment 4•13 years ago
|
||
what is considered sensitive here?
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to Tracy Walker [:tracy] from comment #4)
> what is considered sensitive here?
Anything logged by Logger.pii().
Are we still interested in this? I'm pretty sure we *never* want to log PII without developer intervention.
Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•12 years ago
|
Product: Mozilla Services → Android Background Services
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•