Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(707)

Side by Side Diff: crypto/capi_util.h

Issue 6805019: Move crypto files out of base, to a top level directory. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Created 9 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 // Copyright (c) 2011 The Chromium Authors. All rights reserved. 1 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 #ifndef BASE_CRYPTO_CAPI_UTIL_H_ 5 #ifndef CRYPTO_CAPI_UTIL_H_
6 #define BASE_CRYPTO_CAPI_UTIL_H_ 6 #define CRYPTO_CAPI_UTIL_H_
7 #pragma once 7 #pragma once
8 8
9 #include <windows.h> 9 #include <windows.h>
10 #include <wincrypt.h> 10 #include <wincrypt.h>
11 11
12 #include "base/base_api.h" 12 namespace crypto {
13
14 namespace base {
15 13
16 // CryptAcquireContext when passed CRYPT_NEWKEYSET or CRYPT_DELETEKEYSET in 14 // CryptAcquireContext when passed CRYPT_NEWKEYSET or CRYPT_DELETEKEYSET in
17 // flags is not thread-safe. For such calls, we create a global lock to 15 // flags is not thread-safe. For such calls, we create a global lock to
18 // synchronize it. 16 // synchronize it.
19 // 17 //
20 // From "Threading Issues with Cryptographic Service Providers", 18 // From "Threading Issues with Cryptographic Service Providers",
21 // <http://msdn.microsoft.com/en-us/library/aa388149(v=VS.85).aspx>: 19 // <http://msdn.microsoft.com/en-us/library/aa388149(v=VS.85).aspx>:
22 // 20 //
23 // "The CryptAcquireContext function is generally thread safe unless 21 // "The CryptAcquireContext function is generally thread safe unless
24 // CRYPT_NEWKEYSET or CRYPT_DELETEKEYSET is specified in the dwFlags 22 // CRYPT_NEWKEYSET or CRYPT_DELETEKEYSET is specified in the dwFlags
25 // parameter." 23 // parameter."
26 BASE_API BOOL CryptAcquireContextLocked(HCRYPTPROV* prov, 24 BOOL CryptAcquireContextLocked(HCRYPTPROV* prov,
27 LPCWSTR container, 25 LPCWSTR container,
28 LPCWSTR provider, 26 LPCWSTR provider,
29 DWORD prov_type, 27 DWORD prov_type,
30 DWORD flags); 28 DWORD flags);
31 29
32 } // namespace base 30 } // namespace crypto
33 31
34 #endif // BASE_CRYPTO_CAPI_UTIL_H_ 32 #endif // CRYPTO_CAPI_UTIL_H_
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698