diff options
| author | rsleevi@chromium.org <rsleevi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-24 03:02:07 +0000 |
|---|---|---|
| committer | rsleevi@chromium.org <rsleevi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-06-24 03:02:07 +0000 |
| commit | 810e6e11d6e608532d324767aa039e885e2cc87b (patch) | |
| tree | c1dc7142f8a97233af7289cfa608e50dfb44c30e /net | |
| parent | 8a760de30fd6aaaac460278fa0f55128e77dfe33 (diff) | |
| download | chromium_src-810e6e11d6e608532d324767aa039e885e2cc87b.zip chromium_src-810e6e11d6e608532d324767aa039e885e2cc87b.tar.gz chromium_src-810e6e11d6e608532d324767aa039e885e2cc87b.tar.bz2 | |
Windows and NSS implementations allow for any certificate, while the Mac implementation currenly constrains to certificates flagged for client authentication. The behaviour on other browsers is to allow any certificate for which the user has a private key, regardless of usage constraints, when handling application/x-x509-user-cert.
BUG=148
TEST=none
Review URL: http://codereview.chromium.org/2843015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50691 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net')
| -rw-r--r-- | net/base/cert_database_mac.cc | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/net/base/cert_database_mac.cc b/net/base/cert_database_mac.cc index 2fa3340..938f133 100644 --- a/net/base/cert_database_mac.cc +++ b/net/base/cert_database_mac.cc @@ -20,8 +20,6 @@ int CertDatabase::CheckUserCert(X509Certificate* cert) { return ERR_CERT_INVALID; if (cert->HasExpired()) return ERR_CERT_DATE_INVALID; - if (!cert->SupportsSSLClientAuth()) - return ERR_CERT_INVALID; // Verify the Keychain already has the corresponding private key: SecIdentityRef identity = NULL; |