blob: 038fc1c3b2a04b9018c0131b8199f8aa61b3adf7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
// Copyright (c) 2010 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#include "net/base/cert_database.h"
#include <windows.h>
#include <wincrypt.h>
#pragma comment(lib, "crypt32.lib")
#include "net/base/net_errors.h"
#include "net/base/x509_certificate.h"
namespace net {
CertDatabase::CertDatabase() {
}
int CertDatabase::CheckUserCert(X509Certificate* cert) {
if (!cert)
return ERR_CERT_INVALID;
if (cert->HasExpired())
return ERR_CERT_DATE_INVALID;
// TODO(rsleevi): Should CRYPT_FIND_SILENT_KEYSET_FLAG be specified? A UI
// may be shown here / this call may block.
if (!CryptFindCertificateKeyProvInfo(cert->os_cert_handle(), 0, NULL))
return ERR_NO_PRIVATE_KEY_FOR_CERT;
return OK;
}
int CertDatabase::AddUserCert(X509Certificate* cert) {
// TODO(rsleevi): Would it be more appropriate to have the CertDatabase take
// construction parameters (Keychain filepath on Mac OS X, PKCS #11 slot on
// NSS, and Store Type / Path) here? For now, certs will be stashed into the
// user's personal store, which will not automatically mark them as trusted,
// but will allow them to be used for client auth.
HCERTSTORE cert_db = CertOpenSystemStore(NULL, L"MY");
if (!cert_db)
return ERR_ADD_USER_CERT_FAILED;
BOOL added = CertAddCertificateContextToStore(cert_db,
cert->os_cert_handle(),
CERT_STORE_ADD_USE_EXISTING,
NULL);
CertCloseStore(cert_db, 0);
if (!added)
return ERR_ADD_USER_CERT_FAILED;
CertDatabase::NotifyObserversOfUserCertAdded(cert);
return OK;
}
} // namespace net
|
