Classe TSSLOpenSSLCapi

Unit

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

Protected function LoadSigningCertificate: boolean;
Protected function SetSslKeys: boolean; override;
Protected function NeedSigningCertificate: boolean; override;
Protected function SigningCertificateSpecified: boolean;
Public constructor Create(const Value: TTCPBlockSocket); override;
Public destructor Destroy; override;
Public procedure Assign(const Value: TCustomSSL); override;
Public class function InitEngine: boolean;

Propriedades

Protected property Engine: PENGINE read GetEngine;
Public property SigningCertificateLocation: TWindowsCertStoreLocation read FSigningCertificateLocation write FSigningCertificateLocation;
Public property SigningCertificateStore: string read FSigningCertificateStore write FSigningCertificateStore;
Public property SigningCertificateID: string read FSigningCertificateID write FSigningCertificateID;

Descrição

Métodos

Protected function LoadSigningCertificate: boolean;

Loads a certificate context into the CAPI engine for signing/decryption.

Protected function SetSslKeys: boolean; override;

See TSSLOpenSSL.SetSslKeys

Protected function NeedSigningCertificate: boolean; override;

See TSSLOpenSSL.NeedSigningCertificate

Protected function SigningCertificateSpecified: boolean;

Returns true if the signing certificate should be used.

Public constructor Create(const Value: TTCPBlockSocket); override;

See TSSLOpenSSL.Create

Public destructor Destroy; override;

See TSSLOpenSSL.Destroy

Public procedure Assign(const Value: TCustomSSL); override;

See TCustomSSL.Assign

Public 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

Protected property Engine: PENGINE read GetEngine;

Provides a cryptographic engine for OpenSSL

Public property SigningCertificateLocation: TWindowsCertStoreLocation read FSigningCertificateLocation write FSigningCertificateLocation;

Location of the certificate store used for the communication.

Public property SigningCertificateStore: string read FSigningCertificateStore write FSigningCertificateStore;

Certificate store used for the communication. The most common is "MY", or the user's private certificates.

Public 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.