diff options
| author | wtc@chromium.org <wtc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-14 01:06:05 +0000 |
|---|---|---|
| committer | wtc@chromium.org <wtc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-14 01:06:05 +0000 |
| commit | 01c553f08001332cb00cdb7bb7f02256a0146fe0 (patch) | |
| tree | f1d204c01f56f8cdd304f75a0b9d7f5d6b52e261 /webkit | |
| parent | 7be0e1710c92420e5b15b3d0d1850a09848cf217 (diff) | |
| download | chromium_src-01c553f08001332cb00cdb7bb7f02256a0146fe0.zip chromium_src-01c553f08001332cb00cdb7bb7f02256a0146fe0.tar.gz chromium_src-01c553f08001332cb00cdb7bb7f02256a0146fe0.tar.bz2 | |
If Schannel's InitializeSecurityContext calls return
certificate errors, do not map them to our (server)
certificate errors because the errors are referring to the
(missing) client certificate. If we incorrectly handle
them as server certificate errors, we will crash because
we can't get the server certificate from Schannel when the
handshake fails.
Fumitoshi Ukai of Google tracked down the bug and proposed
an alternative fix.
R=rvargas,ukai
BUG=http://crbug.com/11646
TEST=Visit https://www.cdep.ro/. Chromium should not crash.
Review URL: http://codereview.chromium.org/113375
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16026 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit')
0 files changed, 0 insertions, 0 deletions