Collaboration diagram for Windows Crypto API Interface:
![]() |
All initialisation of the Windows providers needs to be done by the calling application. The interface will call the provided DSS (PROV_DSS) provider and RSA (PROV_RSA_FULL) provider to perform cryptographic functions.
The tools use the default providers, but the calling application can use any providers that implement PROV_DSS and PROV_FULL_RSA.
Note that, unlike the OpenSSL classes, the various implementation classes all require their owner provider class to be passed into the constructor. This allows them to access the RSA and DSS CAPI providers being used for the implementation.
Classes | |
class | WinCAPICryptoHash |
Windows Crypto API Implementation of Hash functions. More... | |
class | WinCAPICryptoHashHMAC |
Implementation of HMAC Hash functions in the Windows providers. More... | |
class | WinCAPICryptoKeyDSA |
WinCAPI implementation class for DSA keys. More... | |
class | WinCAPICryptoKeyHMAC |
Windows Crypto API implementation for HMAC keys. More... | |
class | WinCAPICryptoKeyRSA |
WinCAPI implementation of the interface class for RSA keys. More... | |
class | WinCAPICryptoSymmetricKey |
Base interface definition for symmetric key material. More... | |
class | WinCAPICryptoX509 |
WinCAPI implementation class for interface for X509 certificates. More... |