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?