My favorites | Sign in
Logo
Project hosting will be READ-ONLY Wednesday at 8am PST due to brief network maintenance.
             
New issue | Search
for
| Advanced search | Search tips
Issue 2221: Proxy authentication not supported for updates
5 people starred this issue and may be notified of changes. Back to list
Status:  Duplicate
Owner:  ----
Closed:  Jan 2009
Cc:  thatan...@google.com
OS-All
Pri-1
Type-Bug
Area-Internals
Internals-Install


Sign in to add a comment
 
Reported by helder.magalhaes, Sep 13, 2008
Product Version      : 0.2.149.29
Other browsers tested: 
     Safari 3: FAIL (Apple Software Updater also suffers from this issue)
    Firefox 3: OK (using "Help"->"Check for updates...")
         IE 7: OK (through Windows Update)
      Opera 9: OK (through "Help"->"Check for Updates")

What steps will reproduce the problem?
1. Open Google Chrome in a network environment with an authenticated proxy;
2. Open the tools menu's "About" (or similar) panel;

What is the expected result? 
The browser would display a notification about updates found or no new
updates available.

What happens instead?
After about two minutes displaying a "Checking for updates..." message, an
error message is displayed: "The updates server is not available (error:
7)". Additionally, the system's default browser is triggered to open a
troubleshooting page [1].

Please provide any additional information below. Attach a screenshot if
possible.
This is seen as a somehow important issue. Specially if taking into
consideration the statement in the Google Chrome blog:
  «Automatic updates are a key security feature in helping to ensure the
safety of Google Chrome users.» [2]
As this issue will prevent Google Chrome from updating itself, less
experienced and/or proactive users will potentially be using a browser
version which is vulnerable to attacks, so this issue can almost be
considered a security bug.

Note that this issue makes little sense considering the browser itself
reasonably (not perfectly [3]) supports authenticated proxy.

A related issue [4] exists at the installer level, therefore preventing
users in a similar environment to be able to install the browser.

Attached are a screenshot of the about panel containing the error message
(in Portuguese) and the error logged in the Event viewer.

[1]http://www.google.com/support/installer/bin/answer.py?answer=106640&hl=&errorcode=0x80042197&extracode1=0x00000000&extracode2=0&app={8A69D345-D564-463C-AFF1-A69D9E530F96}&guver=1.2.131.11&ismachine=0&os=5.1&sp=Service%20Pack%203&mid={B7A3062B-4320-4478-B227-DDD4DA548BDF}&uid={6177EF8E-29A4-4CFA-B242-FC882CC3893B}&iid=&source=updatecheck
[2] http://googlechromereleases.blogspot.com/2008/09/beta-release-0214929.html
[3] http://code.google.com/p/chromium/issues/detail?id=24
[4] http://code.google.com/p/chromium/issues/detail?id=14
CheckingForUpdates-ProxyAuthenticationFails.png
56.6 KB   View   Download
GoogleUpdate-EventViewerError.txt
1.0 KB   Download
Comment 1 by ian@chromium.org, Sep 14, 2008
Marking as an installer issue, not a security issue. (I think this is on file 
already, but I'm not totally sure.)
Labels: -private -Security -Pri-0 -Area-Unknown Pri-1 Area-Installer
Comment 2 by thatan...@google.com, Oct 03, 2008
(No comment was entered for this change.)
Cc: thatan...@google.com
Comment 3 by kuchhal@chromium.org, Jan 05, 2009
This is same as  issue 14  since Google Update doesn't support authenticated proxies.
Status: Duplicate
Mergedinto: 14
Comment 4 by helder.magalhaes, Mar 05, 2009
(In reply to comment#3)
> This is same as  issue 14  since Google Update doesn't support authenticated proxies.

This doesn't appear to be a duplicate. Note that this issue is meant to track the
updating procedure, not the install. This has became specially relevant after reading
comment 70 of  issue 14 :

> To clarify, auto-updating won't be effected by this change.
> It only provides a solution for initial installs.

I'd suggest removing the duplicate tagging from this issue and treating it as a
separate issue (or marking as a duplicate of a proper issue, of course, though I
wasn't able to find one in a set of quick searches).
Comment 5 by mal.chromium, Dec 18, 2009
(No comment was entered for this change.)
Labels: -Area-Installer Area-Internals Internals-Install
Mergedinto: -
Sign in to add a comment