summaryrefslogtreecommitdiffstats
path: root/crypto/capi_util.h
diff options
context:
space:
mode:
Diffstat (limited to 'crypto/capi_util.h')
-rw-r--r--crypto/capi_util.h32
1 files changed, 32 insertions, 0 deletions
diff --git a/crypto/capi_util.h b/crypto/capi_util.h
new file mode 100644
index 0000000..faaf012
--- /dev/null
+++ b/crypto/capi_util.h
@@ -0,0 +1,32 @@
+// Copyright (c) 2011 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.
+
+#ifndef CRYPTO_CAPI_UTIL_H_
+#define CRYPTO_CAPI_UTIL_H_
+#pragma once
+
+#include <windows.h>
+#include <wincrypt.h>
+
+namespace crypto {
+
+// CryptAcquireContext when passed CRYPT_NEWKEYSET or CRYPT_DELETEKEYSET in
+// flags is not thread-safe. For such calls, we create a global lock to
+// synchronize it.
+//
+// From "Threading Issues with Cryptographic Service Providers",
+// <http://msdn.microsoft.com/en-us/library/aa388149(v=VS.85).aspx>:
+//
+// "The CryptAcquireContext function is generally thread safe unless
+// CRYPT_NEWKEYSET or CRYPT_DELETEKEYSET is specified in the dwFlags
+// parameter."
+BOOL CryptAcquireContextLocked(HCRYPTPROV* prov,
+ LPCWSTR container,
+ LPCWSTR provider,
+ DWORD prov_type,
+ DWORD flags);
+
+} // namespace crypto
+
+#endif // CRYPTO_CAPI_UTIL_H_