| Index: base/crypto/capi_util.h
|
| ===================================================================
|
| --- base/crypto/capi_util.h (revision 81350)
|
| +++ base/crypto/capi_util.h (working copy)
|
| @@ -1,34 +0,0 @@
|
| -// 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 BASE_CRYPTO_CAPI_UTIL_H_
|
| -#define BASE_CRYPTO_CAPI_UTIL_H_
|
| -#pragma once
|
| -
|
| -#include <windows.h>
|
| -#include <wincrypt.h>
|
| -
|
| -#include "base/base_api.h"
|
| -
|
| -namespace base {
|
| -
|
| -// 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."
|
| -BASE_API BOOL CryptAcquireContextLocked(HCRYPTPROV* prov,
|
| - LPCWSTR container,
|
| - LPCWSTR provider,
|
| - DWORD prov_type,
|
| - DWORD flags);
|
| -
|
| -} // namespace base
|
| -
|
| -#endif // BASE_CRYPTO_CAPI_UTIL_H_
|
|
|