New issue
Advanced search Search tips

Issue 646553 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

KSADMIN blocked via Parental Controls Results in Chrome failing to launch

Reported by zack.mcc...@bsd7.org, Sep 13 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36

Steps to reproduce the problem:
1. Create an account with Parental Controls turned on.
2. Do not allow ksadmin or the google update service to run
3. Open chrome

What is the expected behavior?
Chrome should open and be fine. Instead, Chrome crashes instantly because Chrome now requires ksadmin + GoogleSoftwareUpdateAgent to be whitelisted to run.

What went wrong?
Chrome copies the stupid Google Update agent to every user's local folder. Admin accounts should be the only accounts to have access to this hence keeping it in the /Library/Google domain as opposed to ~/Library/Google. Now Chrome refuses to launch unless you add ksadmin to the whitelist (which defeats the purpose of locking down non-admin accounts form doing updates). ksinstall --nuke only deletes the update service until the next launch of chrome. /usr/bin/defaults write /Library/Preferences/com.google.Keystone masterDisable -bool YES does not prevent ksadmin from running.

Did this work before? Yes Before V52 Stable release.

Chrome version: 53.0.2785.101  Channel: n/a
OS Version: OS X 10.12.0
Flash Version: Shockwave Flash 22.0 r0
 
Many Mac admins control chrome's update through either Munki, Simian, Autopkg, or JSS. There needs to be a way to completely disable the chrome/google update service and prevent ksadmin from being copied to each user folder. ksadmin --uninstall is no longer a valid flag either.
Choosing allow always results in a temporary fix until the next day. Then the same cycle starts.
ksadmincrash.png
719 KB View Download
Components: -Enterprise Enterprise>Triaged
Owner: georgesak@chromium.org
Assigned to georgesak@ for prioritization.

Comment 4 by tnagel@chromium.org, Feb 28 2017

Labels: Enterprise-Triaged

Comment 5 by tnagel@chromium.org, Feb 28 2017

Components: Enterprise

Comment 6 by tnagel@chromium.org, Feb 28 2017

Components: -Enterprise>Triaged
Project Member

Comment 7 by sheriffbot@chromium.org, Feb 28 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment