Add "is Admin with UAC disabled" to launcher-process-failure ping
Categories
(Firefox :: Launcher Process, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: bugzilla, Assigned: toshi)
References
(Blocks 1 open bug)
Details
(Whiteboard: inj+)
Attachments
(2 files, 1 obsolete file)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
2.29 KB,
text/plain
|
chutten
:
data-review+
|
Details |
This will be useful when diagnosing failures.
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
This patch adds a new Scalar metric sandbox.is_admin_without_uac
that
indicates the process is lauched with Admin privileges when UAC is turned
off.
We use the elevation type of a process token to determine UAC is on or off
instead of reading the registry value EnableLUA
. Basically a token is
either full or limited if UAC is on. If the account is built-in
Administrator, however, the token type is default though UAC is on. Thus
we check the account SID as well as the elevation type.
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Reporter | ||
Comment 5•5 years ago
|
||
This looks great, however we do have one more change that we need to make: we need to update the schema on the back-end.
You will need to clone the dev
branch of this github repo and update these files with the new field, then follow the procedure for regenerating the schemas. Then check those in and submit a PR.
The process is a bit complicated but is described in the README for the repository. As always, feel free to ping me or ask questions in #telemetry
on IRC.
Assignee | ||
Comment 6•5 years ago
|
||
Thanks, Aaron. Started https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/399
Assignee | ||
Comment 7•5 years ago
|
||
(In reply to Aaron Klotz [:aklotz] from comment #5)
This looks great, however we do have one more change that we need to make: we need to update the schema on the back-end.
Thanks, Aaron. The schema update has been merged into the master branch. This is ready to land.
https://github.com/mozilla-services/mozilla-pipeline-schemas/commit/603b5583ed4f725847ce24c4e594c3207b71a263
Comment 9•5 years ago
|
||
bugherder |
Description
•