Restrict log uploads, screen capture to auto-launch single-app kiosk on the client |
|||||
Issue descriptionFrom my reading of the code log upload is only gated on kSystemLogUploadEnabled which means that in case of an erroneous server configuration log upload might accidentally happen during user sessions. We should prevent such errors from happening and add client-side logic to ensure that SystemLogUploader only runs in auto-launch single app kiosk mode. Likewise for screen capture.
,
Aug 9 2017
(Note: This bug is a follow-up to issue 579579.)
,
Aug 10 2017
,
Aug 10 2017
,
Aug 10 2017
(Drew, fyi) Ivan, is this something you can look into when you get sometime?
,
Aug 11 2017
This is WAI - since system logs are shared across all users, and can be viewed by *all users* via chrome://system, we don't treat them as PII per se (and we do some sanitization before upload in case anything happens to leak in there). We explicitly do not try to limit the system logs being uploaded to specific types of sessions. This was approved by pcounsel and privacy team when we launched the original feature. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tnagel@chromium.org
, Aug 9 2017