0374b299997a8bd265a7f79cc06f79e7892a0ac7 - chromium/src

commit	0374b299997a8bd265a7f79cc06f79e7892a0ac7	[log] [tgz]
author	wtc@chromium.org <wtc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>	Fri Aug 14 23:49:19 2009
committer	wtc@chromium.org <wtc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>	Fri Aug 14 23:49:19 2009
tree	e6df89d8a3dd741026b39442ffed95b30835b075
parent	b31844be04ffac8e67d5f302c3bad5b28e1dec79 [diff]

Add new certificate error code
ERR_CERT_WEAK_SIGNATURE_ALGORITHM and certificate status
flag CERT_STATUS_WEAK_SIGNATURE_ALGORITHM.  Note that I
didn't add new load flag
LOAD_IGNORE_CERT_WEAK_SIGNATURE_ALGORITHM.

Allow users to accept MD2 certificates as certificates
signed using a weak signature algorithm.  MD4 certificates
are still treated as invalid certificates.

R=jar,jcampan
BUG=http://crbug.com/18725
TEST=none
Review URL: http://codereview.chromium.org/165504

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23497 0039d316-1c4b-4281-b951-d872f2087c98

chrome/app/generated_resources.grd[diff]
chrome/browser/ssl/ssl_error_info.cc[diff]
chrome/browser/ssl/ssl_error_info.h[diff]
chrome/browser/ssl/ssl_policy.cc[diff]
chrome/common/security_filter_peer.cc[diff]
net/base/cert_status_flags.cc[diff]
net/base/cert_status_flags.h[diff]
net/base/net_error_list.h[diff]
net/base/x509_certificate_win.cc[diff]

9 files changed

tree: e6df89d8a3dd741026b39442ffed95b30835b075