-->
[CAPICOM is a 32-bit only component that is available for use in the following operating systems: Windows Server 2008, Windows Vista and Windows XP. Instead, use the .NET Framework to implement security features. For more information, see Alternatives to Using CAPICOM.]
The CAPICOM COM client provides services that enable application developers to add security based on cryptography to applications. CryptoAPI includes functionality for authentication using digital signatures, for enveloping messages, and for encrypting and decrypting data.
Mac Os Mojave
| Category | Description |
|---|---|
| Certificate Store Objects | Objects available for using certificate stores and the certificates in those stores. |
| Digital Signature Objects | Objects used to digitally sign data and to verify digital signatures. |
| Enveloped Data Objects | Objects used to create enveloped data messages for privacy and to decrypt data in enveloped messages. |
| Data Encryption Objects | Objects used to encrypt data and to decrypt encrypted data. |
| Auxiliary Objects | Objects used to change default behaviors and to manage certificates, certificate stores, and user interface (UI) messages. |
| Interoperability Interfaces | Interfaces that allow derivations of CryptoAPI to work together with CAPICOM 2.0. |
| Enumeration Types | Enumeration types used with CAPICOM. |
Certificate Store Objects
Download macOS Big Sur. If you’re using macOS Mojave or later, choose Apple menu System Preferences, then click Software Update. If you’re using an earlier macOS, use the App Store instead.
The following objects work with certificate stores and the certificates in those stores. CAPICOM supports the use of Current User, Local Machine, Memory, and Active Directory certificate stores.
- Download the latest driver for your token, install it with a few clicks. Choose the driver depending on your operating system.
- Jul 05, 2018 Trusted Windows (PC) download Microsoft Capicom 2.1.0.2. Virus-free and 100% clean download. Get Microsoft Capicom alternative downloads.
| Object | Description |
|---|---|
| Certificate | A single digital certificate. |
| CertificatePolicies | A collection of PolicyInformation objects. |
| Certificates | Collection of Certificate objects. |
| CertificateStatus | Provides status information on a certificate. |
| Chain | Creates and checks a certificate validation chain based on a digital certificate. |
| ExtendedProperties | Represents a collection of ExtendedProperty objects. |
| ExtendedProperty | Represents a Microsoft-extended property. |
| Extension | Represents a single certificate extension. |
| Extensions | Represents a collection of Extension objects. |
| PrivateKey | Represents a private key. |
| PublicKey | Represents a public key in a Certificate object. |
| Store | Provides the properties and methods to choose, manage, and use certificate stores and the certificates in those stores. |
| Template | Represents the certificate extension template of the certificate. |
Digital Signature Objects
The following objects are exported to digitally sign data and to verify digital signatures.
| Object | Description |
|---|---|
| SignedCode | Provides functionality for signing content with an Authenticode digital signature. |
| SignedData | Object used to sign data and to verify the signature on signed data. |
| Signer | Information on a single data signer, including the signer's certificate. |
| Signers | Collection of Signer objects. |
Enveloped Data Objects
The following objects are exported to create enveloped data messages for privacy and to decrypt data in enveloped messages.
| Object | Description |
|---|---|
| EnvelopedData | Objects used to create, send, and receive enveloped data. Enveloped data is encrypted so that only the intended recipients can decrypt it. |
| Recipients | Collection of the Certificate objects of the intended recipients of an enveloped message. |
Data Encryption Objects
.jpg "Capicom mac os 10.13")
The following object is exported to encrypt arbitrary data for privacy and to decrypt encrypted data.
| Object | Description |
|---|---|
| EncryptedData | Objects used to encrypt data. Encrypted data in an EncryptedData object can be decrypted. |
Auxiliary Objects
The following objects are exported to change default behaviors of other objects and to manage certificates, certificate stores, and messages.
| Object | Description |
|---|---|
| Algorithm | Sets the algorithm and key length to be used in cryptographic operations. |
| Attribute | Provides a single piece of added information about a signature, such as the time of signing. |
| Attributes | Collection of Attribute objects. |
| BasicConstraints | Provides read-only access to basic constraints on the uses of a certificate. |
| EKU | Provides access to EKU properties of certificates. |
| EKUs | Collection of EKU objects. |
| EncodedData | Represents a block of encoded data. |
| ExtendedKeyUsage | Provides read-only access to the extended key usage properties of certificates. |
| HashedData | Provides functionality for applying a hash algorithm to a string. |
| KeyUsage | Provides read-only access to key usage properties of certificates. |
| OID | Represents an object identifier that is used by several CAPICOM properties. |
| OIDs | Represents a collection of OID objects. |
| PolicyInformation | Provides access to the policy OIDs of an extension. |
| Qualifier | Represents a Certification Practice Statement (CPS) pointer or user notice qualifier. |
| Qualifiers | Represents a collection of qualifiers. |
| Settings | Enables or disables dialog boxes to prompt for signer or sender identity if that identity is not specified. |
| Utilities | Provides functionality for common tasks. |
Interoperability Interfaces
The following interfaces allow derivations of CryptoAPI to work together with CAPICOM 2.0.
| Interface | Description |
|---|---|
| ICertContext | Provides access to the context of a CAPICOM X.509v3 Certificate object. This context allows the CAPICOM certificate to be used in other derivations of CryptoAPI. |
| ICertStore | Provides access to the context of a CAPICOM Store object. This context allows the CAPICOM certificate store to be used in other derivations of CryptoAPI. |
| IChainContext | Provides access to the context of a CAPICOM Chain object. This context allows the CAPICOM certificate trust chain to be used in other derivations of CryptoAPI. |
Enumeration Types
CAPICOM defines the following enumeration types:
-->[CAPICOM is a 32-bit only component that is available for use in the following operating systems: Windows Server 2008, Windows Vista, Windows XP. Instead, use the .NET Framework to implement security features. For more information, see the alternatives listed below.]
Important
None of the alternatives to CAPICOM offer a solution for scripts; therefore, you must write your own ActiveX control. For more information, see ActiveX Controls.
Certificate Store Objects
We suggest the following alternatives for working with certificate stores and the certificates in those stores.
| Object | Alternative |
|---|---|
| Certificate | The Certificate object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Certificate2 Class in the System.Security.Cryptography.X509Certificates namespace. |
| CertificatePolicies | The CertificatePolicies object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Extension Class in the System.Security.Cryptography.X509Certificates namespace by calling the constructor that takes an OID as a parameter, and then use the OID for Certificate Policies to retrieve the certificate policies. |
| Certificates | The Certificates object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Certificate2Collection Class in the System.Security.Cryptography.X509Certificates namespace. |
| CertificateStatus | The CertificateStatus object is available for use in the operating systems specified in the Requirements section. Instead, use the X509ChainStatus Structure in the System.Security.Cryptography.X509Certificates namespace. |
| Chain | The Chain object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Chain Class in the System.Security.Cryptography.X509Certificates namespace. |
| ExtendedProperties | The ExtendedProperties object is available for use in the operating systems specified in the Requirements section. Instead, use Platform Invocation Services (PInvoke) to call the Win32 API function CertGetCertificateContextProperty and obtain the properties. For information about PInvoke, see Platform Invoke Tutorial. The .NET and CryptoAPI via P/Invoke: Part 1 and .NET and CryptoAPI via P/Invoke: Part 2 subsections of Extending .NET Cryptography with CAPICOM and P/Invoke may also be helpful. |
| ExtendedProperty | The ExtendedProperty object is available for use in the operating systems specified in the Requirements section. Instead, use Platform Invocation Services (PInvoke) to call the Win32 API function CertGetCertificateContextProperty and obtain the properties. For information about PInvoke, see Platform Invoke Tutorial. The .NET and CryptoAPI via P/Invoke: Part 1 and .NET and CryptoAPI via P/Invoke: Part 2 subsections of Extending .NET Cryptography with CAPICOM and P/Invoke may also be helpful. |
| Extension | The Extension object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Extension Class in the System.Security.Cryptography.X509Certificates namespace. |
| Extensions | The Extensions object is available for use in the operating systems specified in the Requirements section. Instead, use the X509ExtensionCollection Class in the System.Security.Cryptography.X509Certificates namespace. |
| PrivateKey | The PrivateKey object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Certificate2.PrivateKey Property in the System.Security.Cryptography.X509Certificates namespace. |
| PublicKey | The PublicKey object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Certificate2.PublicKey Property in the System.Security.Cryptography.X509Certificates namespace. |
| Store | The Store object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Store Class in the System.Security.Cryptography.X509Certificates namespace. |
| Template | The Template object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Extension Class in the System.Security.Cryptography.X509Certificates namespace by calling the constructor that takes an OID as a parameter, and then use the OID for Certificate Template to retrieve the certificate extension template. |
Digital Signature Objects
We suggest the following alternatives to digitally sign data and to verify digital signatures.
Mac Os Versions
| Object | Alternative |
|---|---|
| SignedCode | The SignedCode object is available for use in the operating systems specified in the Requirements section. Instead, use Platform Invocation Services (PInvoke) to call the Win32 API SignerSignEx, SignerTimeStampEx, and WinVerifyTrust functions to sign content with an Authenticode digital signature. For information about PInvoke, see Platform Invoke Tutorial. The .NET and CryptoAPI via P/Invoke: Part 1 and .NET and CryptoAPI via P/Invoke: Part 2 subsections of Extending .NET Cryptography with CAPICOM and P/Invoke may also be helpful. |
| SignedData | The SignedData object is available for use in the operating systems specified in the Requirements section. Instead, use the SignedCms Class in the System.Security.Cryptography.Pkcs namespace. |
| Signer | The Signer object is available for use in the operating systems specified in the Requirements section. Instead, use the CmsSigner Class in the System.Security.Cryptography.Pkcs namespace. |
| Signers | The Signers object is available for use in the operating systems specified in the Requirements section. Instead, use a collection of CmsSigner objects. For more information, see the CmsSigner Class in the System.Security.Cryptography.Pkcs namespace. |
Enveloped Data Objects
We suggest the following alternatives to create enveloped data messages for privacy and to decrypt data in enveloped messages.
| Object | Description |
|---|---|
| EnvelopedData | The EnvelopedData object is available for use in the operating systems specified in the Requirements section. Instead, use the EnvelopedCms Class in the System.Security.Cryptography.Pkcs namespace. |
| Recipients | The Recipients object is available for use in the operating systems specified in the Requirements section. Instead, use the CmsRecipientCollection Class in the System.Security.Cryptography.Pkcs namespace. |
Data Encryption Objects
We suggest the following alternatives to encrypt arbitrary data for privacy and to decrypt encrypted data.
| Object | Description |
|---|---|
| EncryptedData | The EncryptedData object is available for use in the operating systems specified in the Requirements section. Instead, use Platform Invocation Services (PInvoke) to call the Win32 API functions CryptEncryptMessage and CryptDecryptMessage to encrypt and decrypt messages. For information about PInvoke, see Platform Invoke Tutorial. The .NET and CryptoAPI via P/Invoke: Part 1 and .NET and CryptoAPI via P/Invoke: Part 2 subsections of Extending .NET Cryptography with CAPICOM and P/Invoke may also be helpful. |
Auxiliary Objects
We suggest the following alternatives to change default behaviors of other objects and to manage certificates, certificate stores, and messages.
Capicom Mac Os Mojave
| Object | Description |
|---|---|
| Algorithm | The Algorithm object is available for use in the operating systems specified in the Requirements section. Instead, use the AlgorithmIdentifier Class in the System.Security.Cryptography.Pkcs namespace. |
| Attribute | The Attribute object is available for use in the operating systems specified in the Requirements section. Instead, use the CryptographicAttributeObject Class in the System.Security.Cryptography namespace. |
| Attributes | The Attributes object is available for use in the operating systems specified in the Requirements section. Instead, use the CryptographicAttributeObjectCollection Class in the System.Security.Cryptography namespace. |
| BasicConstraints | The BasicConstraints object is available for use in the operating systems specified in the Requirements section. Instead, use the X509BasicConstraintsExtension Class in the System.Security.Cryptography.X509Certificates namespace. |
| EKU | The EKU object is available for use in the operating systems specified in the Requirements section. Instead, use the X509EnhancedKeyUsageExtension Class in the System.Security.Cryptography.X509Certificates namespace. |
| EKUs | The EKUs object is available for use in the operating systems specified in the Requirements section. Instead, use the X509ExtensionCollection Class in the System.Security.Cryptography.X509Certificates namespace. |
| EncodedData | The EncodedData object is available for use in the operating systems specified in the Requirements section. Instead, use the AsnEncodedData Class in the System.Security.Cryptography namespace. |
| ExtendedKeyUsage | The ExtendedKeyUsage object is available for use in the operating systems specified in the Requirements section. Instead, use the X509EnhancedKeyUsageExtension Class in the System.Security.Cryptography.X509Certificates namespace. |
| HashedData | The HashedData object is available for use in the operating systems specified in the Requirements section. Instead, use the HashAlgorithm Class in the System.Security.Cryptography namespace. |
| KeyUsage | The KeyUsage object is available for use in the operating systems specified in the Requirements section. Instead, use the X509EnhancedKeyUsageExtension Class in the System.Security.Cryptography.X509Certificates namespace. |
| NoticeNumbers | The NoticeNumbers object is available for use in the operating systems specified in the Requirements section. For more information, see Qualifier. |
| OID | The OID object is available for use in the operating systems specified in the Requirements section. Instead, use the Oid Class in the System.Security.Cryptography namespace. |
| OIDs | The OIDs object is available for use in the operating systems specified in the Requirements section. Instead, use the OidCollection Class in the System.Security.Cryptography namespace. |
| PolicyInformation | The PolicyInformation object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Extension Class in the System.Security.Cryptography.X509Certificates namespace by calling the constructor that takes an OID as a parameter, and then use the OID for Certificate Policies to process policy information in the Certificate policies extension. |
| Qualifier | The Qualifier object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Extension Class in the System.Security.Cryptography.X509Certificates namespace by calling the constructor that takes an OID as a parameter, and then use the OID for Certificate Policies to process qualifiers that are part of the policy information in the Certificate Policies extension. |
| Qualifiers | The Qualifiers object is available for use in the operating systems specified in the Requirements section. Instead, use the X509Extension Class in the System.Security.Cryptography.X509Certificates namespace by calling the constructor that takes an OID as a parameter, and then use the OID for Certificate Policies to process qualifiers that are part of the policy information in the Certificate Policies extension. |
| Settings | No alternative is available. |
| Utilities | No alternative is available. |