Internet Related/Filtering/Firewall Thread, Google Chrome Updater vs Proxy in Technical; I know I've seen an answer to this somewhere, but I can't find it now that I need it, so... ...
27th June 2013, 03:57 PM #1
- Rep Power
Google Chrome Updater vs Proxy
I know I've seen an answer to this somewhere, but I can't find it now that I need it, so... When we installed Chrome, we targetted Updater at our LEA's ISA server (which is/was an unauthenticated proxy). Setting up the proxy was fiddly (in the GP bolt-on), but we got the hang of it after a while and it worked a treat.
Now, we've changed ISPs to Virgin and we no longer have a top-level proxy, only our internal proxies which need authentication to traverse. We've changed the proxy address in GP, but, problem, there is nowhere to put a username/password to authenticate the updater traffic. So how do you trick Updater to store an authentication pair, to traverse the proxy - deployable solution preferred, obviously? Alternatively, how do you find out which hosts Updater needs to update, so I can put them in Squid's whitelist?
1st July 2013, 07:28 PM #2
We use Chrome in our district and I just disabled the auto-update and updates are pushed via Group Policy. To get the update servers addresses you'll probably have to turn off authentication on your proxy and watch the logs as you force the update. I didn't see anything pertaining to Google Update server addresses in a quick search.
1st July 2013, 09:42 PM #3
Same here, disable updates and push chrome with gpo.
2nd July 2013, 05:55 PM #4
- Rep Power
Thanks Duke5A, ADMaster! I had considered GP push and that is the way we deploy the base install. However, I'm not fond of tinkering with GP any more than strictly necessary. In any case, GoogleUpdater works very neatly given the tools to work with; it's just a shame that Google didn't provide neater solutions for Enterprise users.
Good news is that I located the "official" update host list buried in Google's documentation somewhere or other. It looks like this:
I could have whitelisted these, but better news is that one of my technicians dusted off his SQUID acl knowledge and worked out how to identify browser + Google Update traffic, so that our proxy now has this on bypass. Apparently he's done this before with BOINC traffic, although I didn't realize it. Chrome now updates fine at any time of day and the students don't even notice. By the way, GoogleUpdate.adm is essential to set the proxy URL in GP and there is no other obvious way of doing it. Reading the web indicates that loads of people assume that the Updater uses the same settings page as Chrome (well, you would, wouldn't you?), whereas in fact, the settings are quite separate. When you begin to appreciate that GoogleUpdater performs for a whole suite of apps, not just Chrome, you start to realize why.
Last edited by Rammie; 2nd July 2013 at 05:59 PM.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Tags for this Thread