Classe TSSLOpenSSLCapi
Unit
ssl_openssl_capi
Declaração
type TSSLOpenSSLCapi = class(TSSLOpenSSL)
Descrição
class extending the OpenSSL SSL plugin with CAPI support.
Instance of this class will be created for each TTCPBlockSocket. You not need to create instance of this class, all is done by Synapse itself!
Hierarquia
Visão Geral
Métodos
Propriedades
Descrição
Métodos
 |
function LoadSigningCertificate: boolean; |
Loads a certificate context into the CAPI engine for signing/decryption.
|
 |
function SigningCertificateSpecified: boolean; |
Returns true if the signing certificate should be used.
|
 |
class function InitEngine: boolean; |
Use this function to load the CAPI engine and/or verify that the engine is available. The plugin will load CAPI itself when it is needed, so you may skip this function completely, but it may be useful to perform a manual CAPI load early during the application startup to make sure all connection use the same cryptographic engine (and, as a result, behave the same way).
|
Propriedades
 |
property Engine: PENGINE read GetEngine; |
Provides a cryptographic engine for OpenSSL
|
 |
property SigningCertificateLocation: TWindowsCertStoreLocation read FSigningCertificateLocation write FSigningCertificateLocation; |
Location of the certificate store used for the communication.
|
 |
property SigningCertificateStore: string read FSigningCertificateStore write FSigningCertificateStore; |
Certificate store used for the communication. The most common is "MY", or the user's private certificates.
|
 |
property SigningCertificateID: string read FSigningCertificateID write FSigningCertificateID; |
ID of the certificate to use. For standard CAPI, this is the friendly name of the certificate. For the client-side SSL it is not really necessary, as long as it is non-empty (which signifies that the CAPI engine should be used). For the server side, it must be a substring of the SubjectName of the certificate. The first matching certificate will be used.
|
Gerado por PasDoc 0.16.0.