| Index: crypto/capi_util.h
|
| ===================================================================
|
| --- crypto/capi_util.h (revision 0)
|
| +++ crypto/capi_util.h (revision 0)
|
| @@ -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_
|
|
|
| Property changes on: crypto\capi_util.h
|
| ___________________________________________________________________
|
| Added: svn:eol-style
|
| + LF
|
|
|
|
|