# RSA Component

Implements RSA public-key cryptography to encrypt/decrypt and sign/verify messages.

## Syntax

```text
nsoftware.IPWorksEncrypt.RSA
```

## Remarks

The RSA component implements RSA public-key cryptography to encrypt/decrypt messages and sign/verify hash signatures.

To begin you must either specify an existing key or create a new key. Existing private keys may be specified by setting [Key](#key-property-rsa-component). To create a new key call [CreateKey](#createkey-method-rsa-component). Alternatively an existing certificate may be specified by setting [Certificate](#certificate-property-rsa-component)

**Signing**

To sign data first set [Key](#key-property-rsa-component) or [Certificate](#certificate-property-rsa-component). Specify the input data using [InputFile](#inputfile-property-rsa-component) or [InputMessage](#inputmessage-property-rsa-component). Next call [Sign](#sign-method-rsa-component). The component will populate [HashValue](#hashvalue-property-rsa-component) and [HashSignature](#hashsignature-property-rsa-component). After calling [Sign](#sign-method-rsa-component) the public key must be sent to the recipient along with [HashSignature](#hashsignature-property-rsa-component).

**Encrypting**

To encrypt data set [RecipientKey](#recipientkey-property-rsa-component) or [RecipientCert](#recipientcert-property-rsa-component). Specify the input data using [InputFile](#inputfile-property-rsa-component) or [InputMessage](#inputmessage-property-rsa-component). Next call [Encrypt](#encrypt-method-rsa-component). The component will populate [OutputMessage](#outputmessage-property-rsa-component), or write to the file specified by [OutputFile](#outputfile-property-rsa-component).

**Signature Verification**

To verify a signature specify the input data using [InputFile](#inputfile-property-rsa-component) or [InputMessage](#inputmessage-property-rsa-component). Set [SignerKey](#signerkey-property-rsa-component) or [SignerCert](#signercert-property-rsa-component). Next set [HashSignature](#hashsignature-property-rsa-component) and call [VerifySignature](#verifysignature-method-rsa-component). The [VerifySignature](#verifysignature-method-rsa-component) method will return True if the signature was successfully verified.

**Decrypting**

To decrypt data first set [Key](#key-property-rsa-component) or [Certificate](#certificate-property-rsa-component). Specify the input data using [InputFile](#inputfile-property-rsa-component) or [InputMessage](#inputmessage-property-rsa-component). Next call [Decrypt](#decrypt-method-rsa-component). The component will populate [OutputMessage](#outputmessage-property-rsa-component), or write to the file specified by [OutputFile](#outputfile-property-rsa-component).

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**RSA Keys**

A RSA key is made up of a number of individual parameters.

The public key consists of the following parameters:

- [Modulus](#RSAKey_f_Modulus)
- [Exponent](#RSAKey_f_Exponent)

The component also includes the [PublicKey](#RSAKey_f_PublicKey) field which holds the PEM formatted public key for ease of use. This is helpful if you are in control of both sides of the encryption/signing and decryption/signature verification process. When sending the public key to a recipient note that not all implementations will support using the PEM formatted value in [PublicKey](#RSAKey_f_PublicKey) in which case the individual parameters must be sent.

The private key may be represented in one of two ways. Both are mathematically equivalent. Private key format 1:

- [Modulus](#RSAKey_f_Modulus)
- [P](#RSAKey_f_P)
- [Q](#RSAKey_f_Q)
- [DP](#RSAKey_f_DP)
- [DQ](#RSAKey_f_DQ)

 Private key format 2 is simpler but has decreased performance when decrypting and signing. This format is:

- [Modulus](#RSAKey_f_Modulus)
- [D](#RSAKey_f_D)

 The component also include the [PrivateKey](#RSAKey_f_PrivateKey) field which holds the PEM formatted private key for ease of use. This is helpful for storing the private key more easily.

## Property List

*The following is the full list of the properties of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Certificate](#certificate-property-rsa-component) | The certificate used for signing and decryption. |
| [HashAlgorithm](#hashalgorithm-property-rsa-component) | The hash algorithm used for signing and signature verification. |
| [HashSignature](#hashsignature-property-rsa-component) | The hash signature. |
| [HashValue](#hashvalue-property-rsa-component) | The hash value of the data. |
| [InputFile](#inputfile-property-rsa-component) | The file to process. |
| [InputMessage](#inputmessage-property-rsa-component) | The message to process. |
| [Key](#key-property-rsa-component) | The RSA key. |
| [OutputFile](#outputfile-property-rsa-component) | The output file when encrypting or decrypting. |
| [OutputMessage](#outputmessage-property-rsa-component) | The output message after processing. |
| [Overwrite](#overwrite-property-rsa-component) | Indicates whether or not the component should overwrite files. |
| [RecipientCert](#recipientcert-property-rsa-component) | The certificate used for encryption. |
| [RecipientKey](#recipientkey-property-rsa-component) | The recipient's public key used when encrypting. |
| [SignerCert](#signercert-property-rsa-component) | The certificate used for signature verification. |
| [SignerKey](#signerkey-property-rsa-component) | The public key used to verify the signature. |
| [UseHex](#usehex-property-rsa-component) | Whether input or output is hex encoded. |
| [UseOAEP](#useoaep-property-rsa-component) | Whether to use Optimal Asymmetric Encryption Padding (OAEP). |
| [UsePSS](#usepss-property-rsa-component) | Whether to use RSA-PSS during signing and verification. |

## Method List

*The following is the full list of the methods of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Config](#config-method-rsa-component) | Sets or retrieves a configuration setting. |
| [CreateKey](#createkey-method-rsa-component) | Creates a new key. |
| [Decrypt](#decrypt-method-rsa-component) | Decrypts the input data using the specified private key. |
| [Encrypt](#encrypt-method-rsa-component) | Encrypts the input data using the recipient's public key. |
| [Reset](#reset-method-rsa-component) | Resets the component. |
| [SetInputStream](#setinputstream-method-rsa-component) | Sets the stream from which the component will read data to encrypt or decrypt. |
| [SetOutputStream](#setoutputstream-method-rsa-component) | Sets the stream to which the component will write encrypted or decrypted data. |
| [Sign](#sign-method-rsa-component) | Creates a hash signature. |
| [VerifySignature](#verifysignature-method-rsa-component) | Verifies the signature for the specified data. |

## Event List

*The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Error](#error-event-rsa-component) | Fired when information is available about errors during data delivery. |
| [Progress](#progress-event-rsa-component) | Fired as progress is made. |

## Config Settings

*The following is a list of config settings for the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) | Determines whether or not the input stream is closed after processing. |
| [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing) | Determines whether or not the output stream is closed after processing. |
| [KeyFormat](#KeyFormat) | How the public and private key are formatted. |
| [KeySize](#KeySize) | The size, in bits, of the secret key. |
| [OAEPMGF1HashAlgorithm](#OAEPMGF1HashAlgorithm) | The MGF1 hash algorithm used with OAEP. |
| [OAEPParams](#OAEPParams) | The hex encoded OAEP parameters. |
| [UsePrimitive](#UsePrimitive) | Enables primitive RSA encryption with no padding scheme or output modification. |
| [BuildInfo](#BuildInfo) | Information about the product's build. |
| [GUIAvailable](#GUIAvailable) | Whether or not a message loop is available for processing events. |
| [LicenseInfo](#LicenseInfo) | Information about the current license. |
| [MaskSensitiveData](#MaskSensitiveData) | Whether sensitive data is masked in log messages. |
| [UseFIPSCompliantAPI](#UseFIPSCompliantAPI) | Tells the component whether or not to use FIPS certified APIs. |
| [UseInternalSecurityAPI](#UseInternalSecurityAPI) | Whether or not to use the system security libraries or an internal implementation. |

# Certificate Property ([RSA](#rsa-component) Component)

The certificate used for signing and decryption.

## Syntax

```text
public Certificate Certificate { get; set; }
```

## Remarks

This property specifies a certificate with private key.

This may be set instead of [Key](#key-property-rsa-component). This allows a [Certificate](#certificate-type) object to be used instead of a [RSAKey](#rsakey-type) object. This certificate is used when calling [Sign](#sign-method-rsa-component) and [Decrypt](#decrypt-method-rsa-component). The specified certificate must have a private key.

If both this property and [Key](#key-property-rsa-component) are specified, [Key](#key-property-rsa-component) will be used and this property will be ignored.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# HashAlgorithm Property ([RSA](#rsa-component) Component)

The hash algorithm used for signing and signature verification.

## Syntax

```text
public RSAHashAlgorithms HashAlgorithm { get; set; }
enum RSAHashAlgorithms {
  rhaSHA1,
  rhaSHA224,
  rhaSHA256,
  rhaSHA384,
  rhaSHA512,
  rhaRIPEMD160,
  rhaMD2,
  rhaMD5,
  rhaMD5SHA1
}
```

## Default Value

2

## Remarks

This property specifies the hash algorithm used for signing and signature verification. Possible values are:

|  |  |
| --- | --- |
| 0 (rhaSHA1) | SHA-1 |
| 1 (rhaSHA224) | SHA-224 |
| 2 (rhaSHA256 - default) | SHA-256 |
| 3 (rhaSHA384) | SHA-384 |
| 4 (rhaSHA512) | SHA-512 |
| 5 (rhaRIPEMD160) | RIPEMD-160 |
| 6 (rhaMD2) | MD2 |
| 7 (rhaMD5) | MD5 |
| 8 (rhaMD5SHA1) | MD5SHA1 |

# HashSignature Property ([RSA](#rsa-component) Component)

The hash signature.

## Syntax

```text
public string HashSignature { get; set; }
public byte[] HashSignatureB { get; set; }
```

## Default Value

""

## Remarks

This property holds the computed hash signature. This is populated after calling [Sign](#sign-method-rsa-component). This must be set before calling [VerifySignature](#verifysignature-method-rsa-component).

# HashValue Property ([RSA](#rsa-component) Component)

The hash value of the data.

## Syntax

```text
public string HashValue { get; set; }
public byte[] HashValueB { get; set; }
```

## Default Value

""

## Remarks

This property holds the computed hash value for the specified data. This is populated when calling [Sign](#sign-method-rsa-component) or [VerifySignature](#verifysignature-method-rsa-component) when an input file is specified by setting [SetInputStream](#setinputstream-method-rsa-component), [InputFile](#inputfile-property-rsa-component), or [InputMessage](#inputmessage-property-rsa-component).

If you know the hash value prior to using the component you may specify the pre-computed hash value here.

**Hash Notes**

The component will determine whether or not to recompute the hash based on the properties that are set. If a file is specified by [SetInputStream](#setinputstream-method-rsa-component), [InputFile](#inputfile-property-rsa-component), or [InputMessage](#inputmessage-property-rsa-component), the hash will be recomputed when calling [Sign](#sign-method-rsa-component) or [VerifySignature](#verifysignature-method-rsa-component). If the HashValue property is set, the component will only sign the hash or verify the hash signature. Setting [SetInputStream](#setinputstream-method-rsa-component), [InputFile](#inputfile-property-rsa-component), or [InputMessage](#inputmessage-property-rsa-component) clears the HashValue property. Setting the HashValue property clears the input file selection.

# InputFile Property ([RSA](#rsa-component) Component)

The file to process.

## Syntax

```text
public string InputFile { get; set; }
```

## Default Value

""

## Remarks

This property specifies the file to be processed. Set this property to the full or relative path to the file which will be processed.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- InputFile
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# InputMessage Property ([RSA](#rsa-component) Component)

The message to process.

## Syntax

```text
public string InputMessage { get; set; }
public byte[] InputMessageB { get; set; }
```

## Default Value

""

## Remarks

This property specifies the message to be processed.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- InputMessage

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# Key Property ([RSA](#rsa-component) Component)

The RSA key.

## Syntax

```text
public RSAKey Key { get; set; }
```

## Remarks

This property specifies the RSA key used to sign or decrypt data. This property must be set before calling [Sign](#sign-method-rsa-component) or [Decrypt](#decrypt-method-rsa-component). Alternatively, a certificate may be specified by setting [Certificate](#certificate-property-rsa-component)

**RSA Keys**

A RSA key is made up of a number of individual parameters.

The public key consists of the following parameters:

- [Modulus](#RSAKey_f_Modulus)
- [Exponent](#RSAKey_f_Exponent)

The component also includes the [PublicKey](#RSAKey_f_PublicKey) field which holds the PEM formatted public key for ease of use. This is helpful if you are in control of both sides of the encryption/signing and decryption/signature verification process. When sending the public key to a recipient note that not all implementations will support using the PEM formatted value in [PublicKey](#RSAKey_f_PublicKey) in which case the individual parameters must be sent.

The private key may be represented in one of two ways. Both are mathematically equivalent. Private key format 1:

- [Modulus](#RSAKey_f_Modulus)
- [P](#RSAKey_f_P)
- [Q](#RSAKey_f_Q)
- [DP](#RSAKey_f_DP)
- [DQ](#RSAKey_f_DQ)

 Private key format 2 is simpler but has decreased performance when decrypting and signing. This format is:

- [Modulus](#RSAKey_f_Modulus)
- [D](#RSAKey_f_D)

 The component also include the [PrivateKey](#RSAKey_f_PrivateKey) field which holds the PEM formatted private key for ease of use. This is helpful for storing the private key more easily.

 Please refer to the [RSAKey](#rsakey-type) type for a complete list of fields.

# OutputFile Property ([RSA](#rsa-component) Component)

The output file when encrypting or decrypting.

## Syntax

```text
public string OutputFile { get; set; }
```

## Default Value

""

## Remarks

This property specifies the file to which the output will be written when [Encrypt](#encrypt-method-rsa-component) or [Decrypt](#decrypt-method-rsa-component) is called. This may be set to an absolute or relative path.

This property is only applicable to [Encrypt](#encrypt-method-rsa-component) and [Decrypt](#decrypt-method-rsa-component).

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- OutputFile
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# OutputMessage Property ([RSA](#rsa-component) Component)

The output message after processing.

## Syntax

```text
public string OutputMessage { get; }
public byte[] OutputMessageB { get; }
```

## Default Value

""

## Remarks

This property will be populated with the output from the operation if [OutputFile](#outputfile-property-rsa-component) and [SetOutputStream](#setoutputstream-method-rsa-component) are not set.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- OutputMessage: The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

This property is read-only and not available at design time.

# Overwrite Property ([RSA](#rsa-component) Component)

Indicates whether or not the component should overwrite files.

## Syntax

```text
public bool Overwrite { get; set; }
```

## Default Value

False

## Remarks

This property indicates whether or not the component will overwrite [OutputFile](#outputfile-property-rsa-component). If Overwrite is False, an error will be thrown whenever [OutputFile](#outputfile-property-rsa-component) exists before an operation. The default value is False.

# RecipientCert Property ([RSA](#rsa-component) Component)

The certificate used for encryption.

## Syntax

```text
public Certificate RecipientCert { get; set; }
```

## Remarks

This property specifies a certificate for encryption.

This may be set instead of [RecipientKey](#recipientkey-property-rsa-component). This allows a [Certificate](#certificate-type) object to be used instead of a [RSAKey](#rsakey-type) object. This certificate is used when calling [Encrypt](#encrypt-method-rsa-component).

If both this property and [RecipientKey](#recipientkey-property-rsa-component) are specified, [RecipientKey](#recipientkey-property-rsa-component) will be used and this property will be ignored.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# RecipientKey Property ([RSA](#rsa-component) Component)

The recipient's public key used when encrypting.

## Syntax

```text
public RSAKey RecipientKey { get; set; }
```

## Remarks

This property specifies the recipient's public key. This property must be set before calling [Encrypt](#encrypt-method-rsa-component). Alternatively, a certificate may be specified by setting [RecipientCert](#recipientcert-property-rsa-component)

**RSA Keys**

A RSA key is made up of a number of individual parameters.

The public key consists of the following parameters:

- [Modulus](#RSAKey_f_Modulus)
- [Exponent](#RSAKey_f_Exponent)

The component also includes the [PublicKey](#RSAKey_f_PublicKey) field which holds the PEM formatted public key for ease of use. This is helpful if you are in control of both sides of the encryption/signing and decryption/signature verification process. When sending the public key to a recipient note that not all implementations will support using the PEM formatted value in [PublicKey](#RSAKey_f_PublicKey) in which case the individual parameters must be sent.

The private key may be represented in one of two ways. Both are mathematically equivalent. Private key format 1:

- [Modulus](#RSAKey_f_Modulus)
- [P](#RSAKey_f_P)
- [Q](#RSAKey_f_Q)
- [DP](#RSAKey_f_DP)
- [DQ](#RSAKey_f_DQ)

 Private key format 2 is simpler but has decreased performance when decrypting and signing. This format is:

- [Modulus](#RSAKey_f_Modulus)
- [D](#RSAKey_f_D)

 The component also include the [PrivateKey](#RSAKey_f_PrivateKey) field which holds the PEM formatted private key for ease of use. This is helpful for storing the private key more easily.

 Please refer to the [RSAKey](#rsakey-type) type for a complete list of fields.

# SignerCert Property ([RSA](#rsa-component) Component)

The certificate used for signature verification.

## Syntax

```text
public Certificate SignerCert { get; set; }
```

## Remarks

This property specifies a certificate for signature verification.

This may be set instead of [SignerKey](#signerkey-property-rsa-component). This allows a [Certificate](#certificate-type) object to be used instead of a [RSAKey](#rsakey-type) object. This certificate is used when calling [VerifySignature](#verifysignature-method-rsa-component).

If both this property and [SignerKey](#signerkey-property-rsa-component) are specified, [SignerKey](#signerkey-property-rsa-component) will be used and this property will be ignored.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# SignerKey Property ([RSA](#rsa-component) Component)

The public key used to verify the signature.

## Syntax

```text
public RSAKey SignerKey { get; set; }
```

## Remarks

This property specifies the public key used to verify the signature. This public key corresponds to the private key used when creating the signature. This must be set before calling [VerifySignature](#verifysignature-method-rsa-component). Alternatively, a certificate may be specified by setting [SignerCert](#signercert-property-rsa-component)

**RSA Keys**

A RSA key is made up of a number of individual parameters.

The public key consists of the following parameters:

- [Modulus](#RSAKey_f_Modulus)
- [Exponent](#RSAKey_f_Exponent)

The component also includes the [PublicKey](#RSAKey_f_PublicKey) field which holds the PEM formatted public key for ease of use. This is helpful if you are in control of both sides of the encryption/signing and decryption/signature verification process. When sending the public key to a recipient note that not all implementations will support using the PEM formatted value in [PublicKey](#RSAKey_f_PublicKey) in which case the individual parameters must be sent.

The private key may be represented in one of two ways. Both are mathematically equivalent. Private key format 1:

- [Modulus](#RSAKey_f_Modulus)
- [P](#RSAKey_f_P)
- [Q](#RSAKey_f_Q)
- [DP](#RSAKey_f_DP)
- [DQ](#RSAKey_f_DQ)

 Private key format 2 is simpler but has decreased performance when decrypting and signing. This format is:

- [Modulus](#RSAKey_f_Modulus)
- [D](#RSAKey_f_D)

 The component also include the [PrivateKey](#RSAKey_f_PrivateKey) field which holds the PEM formatted private key for ease of use. This is helpful for storing the private key more easily.

 Please refer to the [RSAKey](#rsakey-type) type for a complete list of fields.

# UseHex Property ([RSA](#rsa-component) Component)

Whether input or output is hex encoded.

## Syntax

```text
public bool UseHex { get; set; }
```

## Default Value

False

## Remarks

This property specifies whether the encrypted data, [HashValue](#hashvalue-property-rsa-component), and [HashSignature](#hashsignature-property-rsa-component) are hex encoded.

If set to True, when [Encrypt](#encrypt-method-rsa-component) is called the component will perform the encryption as normal and then hex encode the output. [OutputMessage](#outputmessage-property-rsa-component) or [OutputFile](#outputfile-property-rsa-component) will hold hex encoded data.

If set to True, when [Decrypt](#decrypt-method-rsa-component) is called the component will expect [InputMessage](#inputmessage-property-rsa-component) or [InputFile](#inputfile-property-rsa-component) to hold hex encoded data. The component will then hex decode the data and perform decryption as normal.

If set to True, when [Sign](#sign-method-rsa-component) is called the component will compute the hash for the specified file and populate [HashValue](#hashvalue-property-rsa-component) with the hex encoded hash value. It will then create the hash signature and populate [HashSignature](#hashsignature-property-rsa-component) with the hex encoded hash signature value. If [HashValue](#hashvalue-property-rsa-component) is specified directly, it must be a hex encoded value.

If set to True, when [VerifySignature](#verifysignature-method-rsa-component) is called the component will compute the hash value for the specified file and populate [HashValue](#hashvalue-property-rsa-component) with the hex encoded hash value. It will then hex decode [HashSignature](#hashsignature-property-rsa-component) and verify the signature. [HashSignature](#hashsignature-property-rsa-component) must hold a hex encoded value. If [HashValue](#hashvalue-property-rsa-component) is specified directly, it must be a hex encoded value.

# UseOAEP Property ([RSA](#rsa-component) Component)

Whether to use Optimal Asymmetric Encryption Padding (OAEP).

## Syntax

```text
public bool UseOAEP { get; set; }
```

## Default Value

False

## Remarks

Whether to use Optimal Asymmetric Encryption Padding (OAEP). By default this value is False and the component will use PKCS1.

Note: When set to True the [HashAlgorithm](#hashalgorithm-property-rsa-component) is also applicable when calling [Encrypt](#encrypt-method-rsa-component) and [Decrypt](#decrypt-method-rsa-component).

# UsePSS Property ([RSA](#rsa-component) Component)

Whether to use RSA-PSS during signing and verification.

## Syntax

```text
public bool UsePSS { get; set; }
```

## Default Value

False

## Remarks

This property specifies whether RSA-PSS will be used when signing and verifying messages. The default value is False.

# Config Method ([RSA](#rsa-component) Component)

Sets or retrieves a configuration setting.

## Syntax

```text
public string Config(string configurationString);

Async Version
public async Task<string> Config(string configurationString);
public async Task<string> Config(string configurationString, CancellationToken cancellationToken);
```

## Remarks

Config is a generic method available in every component. It is used to set and retrieve [configuration settings](#config-settings-rsa-component) for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the Config method.

To set a configuration setting named *PROPERTY*, you must call *Config("PROPERTY=VALUE")*, where *VALUE* is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a [configuration setting](#config-settings-rsa-component), you must call *Config("PROPERTY")*. The value will be returned as a string.

# CreateKey Method ([RSA](#rsa-component) Component)

Creates a new key.

## Syntax

```text
public void CreateKey();

Async Version
public async Task CreateKey();
public async Task CreateKey(CancellationToken cancellationToken);
```

## Remarks

This method creates a new public and private key.

When calling CreateKey the [Key](#key-property-rsa-component) property is populated with a new private and public key.

**RSA Keys**

A RSA key is made up of a number of individual parameters.

The public key consists of the following parameters:

- [Modulus](#RSAKey_f_Modulus)
- [Exponent](#RSAKey_f_Exponent)

The component also includes the [PublicKey](#RSAKey_f_PublicKey) field which holds the PEM formatted public key for ease of use. This is helpful if you are in control of both sides of the encryption/signing and decryption/signature verification process. When sending the public key to a recipient note that not all implementations will support using the PEM formatted value in [PublicKey](#RSAKey_f_PublicKey) in which case the individual parameters must be sent.

The private key may be represented in one of two ways. Both are mathematically equivalent. Private key format 1:

- [Modulus](#RSAKey_f_Modulus)
- [P](#RSAKey_f_P)
- [Q](#RSAKey_f_Q)
- [DP](#RSAKey_f_DP)
- [DQ](#RSAKey_f_DQ)

 Private key format 2 is simpler but has decreased performance when decrypting and signing. This format is:

- [Modulus](#RSAKey_f_Modulus)
- [D](#RSAKey_f_D)

 The component also include the [PrivateKey](#RSAKey_f_PrivateKey) field which holds the PEM formatted private key for ease of use. This is helpful for storing the private key more easily.

# Decrypt Method ([RSA](#rsa-component) Component)

Decrypts the input data using the specified private key.

## Syntax

```text
public void Decrypt();

Async Version
public async Task Decrypt();
public async Task Decrypt(CancellationToken cancellationToken);
```

## Remarks

This method decrypts the input data using the private key specified in [Key](#key-property-rsa-component). Alternatively, a certificate may be specified by setting [Certificate](#certificate-property-rsa-component).

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**Key Size and the Maximum Length of Data**

RSA has an upper limit to the amount of data that can be encrypted or decrypted, also known as message length. This can typically be calculated as the size of the key minus the size of the RSA header and padding.

When not using OAEP, the following formula and table can be referenced. (RSA Key Bytes) - (Header Bytes) = Length of data, where Header Bytes is always 11.

| RSA Key Length (bits) | Length (bits) | Length (bytes) |
| --- | --- | --- |
| 1024 | 936 | 117 |
| 2048 | 1960 | 245 |
| 3072 | 2984 | 373 |
| 4096 | 4008 | 501 |

When using OAEP, the following formula and table can be referenced. (RSA Key Bytes) - (2 * Hash Length Bytes) - 2 = Length of data. The table below assumes SHA-256 for the hash, so Hash Length Bytes is 32.

| RSA Key Length (bits) | Length (bits) | Length (bytes) |
| --- | --- | --- |
| 1024 | 496 | 62 |
| 2048 | 1520 | 190 |
| 3072 | 2544 | 318 |
| 4096 | 3568 | 446 |

# Encrypt Method ([RSA](#rsa-component) Component)

Encrypts the input data using the recipient's public key.

## Syntax

```text
public void Encrypt();

Async Version
public async Task Encrypt();
public async Task Encrypt(CancellationToken cancellationToken);
```

## Remarks

This method encrypts the input data using the public key specified in [RecipientKey](#recipientkey-property-rsa-component). Alternatively, a certificate may be specified by setting [RecipientCert](#recipientcert-property-rsa-component).

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**Key Size and the Maximum Length of Data**

RSA has an upper limit to the amount of data that can be encrypted or decrypted, also known as message length. This can typically be calculated as the size of the key minus the size of the RSA header and padding.

When not using OAEP, the following formula and table can be referenced. (RSA Key Bytes) - (Header Bytes) = Length of data, where Header Bytes is always 11.

| RSA Key Length (bits) | Length (bits) | Length (bytes) |
| --- | --- | --- |
| 1024 | 936 | 117 |
| 2048 | 1960 | 245 |
| 3072 | 2984 | 373 |
| 4096 | 4008 | 501 |

When using OAEP, the following formula and table can be referenced. (RSA Key Bytes) - (2 * Hash Length Bytes) - 2 = Length of data. The table below assumes SHA-256 for the hash, so Hash Length Bytes is 32.

| RSA Key Length (bits) | Length (bits) | Length (bytes) |
| --- | --- | --- |
| 1024 | 496 | 62 |
| 2048 | 1520 | 190 |
| 3072 | 2544 | 318 |
| 4096 | 3568 | 446 |

# Reset Method ([RSA](#rsa-component) Component)

Resets the component.

## Syntax

```text
public void Reset();

Async Version
public async Task Reset();
public async Task Reset(CancellationToken cancellationToken);
```

## Remarks

When called, the component will reset all of its properties to their default values.

# SetInputStream Method ([RSA](#rsa-component) Component)

Sets the stream from which the component will read data to encrypt or decrypt.

## Syntax

```text
public void SetInputStream(System.IO.Stream inputStream);

Async Version
public async Task SetInputStream(System.IO.Stream inputStream);
public async Task SetInputStream(System.IO.Stream inputStream, CancellationToken cancellationToken);
```

## Remarks

This method sets the stream from which the component will read data to encrypt or decrypt.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- SetInputStream
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-rsa-component)
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# SetOutputStream Method ([RSA](#rsa-component) Component)

Sets the stream to which the component will write encrypted or decrypted data.

## Syntax

```text
public void SetOutputStream(System.IO.Stream outputStream);

Async Version
public async Task SetOutputStream(System.IO.Stream outputStream);
public async Task SetOutputStream(System.IO.Stream outputStream, CancellationToken cancellationToken);
```

## Remarks

This method sets the stream to which the component will write encrypted or decrypted data.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-rsa-component)
- [InputFile](#inputfile-property-rsa-component)
- [InputMessage](#inputmessage-property-rsa-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- SetOutputStream
- [OutputFile](#outputfile-property-rsa-component)
- [OutputMessage](#outputmessage-property-rsa-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# Sign Method ([RSA](#rsa-component) Component)

Creates a hash signature.

## Syntax

```text
public void Sign();

Async Version
public async Task Sign();
public async Task Sign(CancellationToken cancellationToken);
```

## Remarks

This method will create a hash signature.

Before calling this method specify the input file by setting [SetInputStream](#setinputstream-method-rsa-component), [InputFile](#inputfile-property-rsa-component), or [InputMessage](#inputmessage-property-rsa-component).

A key is required to create the hash signature. You may create a new key by calling [CreateKey](#createkey-method-rsa-component), or specify an existing key pair in [Key](#key-property-rsa-component). Alternatively, a certificate may be specified by setting [Certificate](#certificate-property-rsa-component). When this method is called the component will compute the hash for the specified file and populate [HashValue](#hashvalue-property-rsa-component). It will then create the hash signature using the specified [Key](#key-property-rsa-component) and populate [HashSignature](#hashsignature-property-rsa-component).

To create the hash signature without first computing the hash simply specify [HashValue](#hashvalue-property-rsa-component) before calling this method.

The [Progress](#progress-event-rsa-component) event will fire with updates for the hash computation progress only. The hash signature creation process is quick and does not require progress updates.

# VerifySignature Method ([RSA](#rsa-component) Component)

Verifies the signature for the specified data.

## Syntax

```text
public bool VerifySignature();

Async Version
public async Task<bool> VerifySignature();
public async Task<bool> VerifySignature(CancellationToken cancellationToken);
```

## Remarks

This method will verify a hash signature.

Before calling this method specify the input file by setting [SetInputStream](#setinputstream-method-rsa-component), [InputFile](#inputfile-property-rsa-component), or [InputMessage](#inputmessage-property-rsa-component).

A public key and the hash signature are required to perform the signature verification. Specify the public key in [SignerKey](#signerkey-property-rsa-component). Alternatively, a certificate may be specified by setting [SignerCert](#signercert-property-rsa-component). Specify the hash signature in [HashSignature](#hashsignature-property-rsa-component).

When this method is called the component will compute the hash for the specified file and populate [HashValue](#hashvalue-property-rsa-component). It will verify the signature using the specified [SignerKey](#signerkey-property-rsa-component) and [HashSignature](#hashsignature-property-rsa-component).

To verify the hash signature without first computing the hash simply specify [HashValue](#hashvalue-property-rsa-component) before calling this method.

The [Progress](#progress-event-rsa-component) event will fire with updates for the hash computation progress only. The hash signature verification process is quick and does not require progress updates.

# Error Event ([RSA](#rsa-component) Component)

Fired when information is available about errors during data delivery.

## Syntax

```text
public event OnErrorHandler OnError;

public delegate void OnErrorHandler(object sender, RSAErrorEventArgs e);

public class RSAErrorEventArgs : EventArgs {
  public int ErrorCode { get; }
  public string Description { get; }
}
```

## Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component throws an exception.

The *ErrorCode* parameter contains an error code, and the *Description* parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-rsa-component) section.

# Progress Event ([RSA](#rsa-component) Component)

Fired as progress is made.

## Syntax

```text
public event OnProgressHandler OnProgress;

public delegate void OnProgressHandler(object sender, RSAProgressEventArgs e);

public class RSAProgressEventArgs : EventArgs {
  public long BytesProcessed { get; }
  public int PercentProcessed { get; }
}
```

## Remarks

This event is fired automatically as data is processed by the component.

The *PercentProcessed* parameter indicates the current status of the operation.

The *BytesProcessed* parameter holds the total number of bytes processed so far.

# Certificate Type

This is the digital certificate being used.

## Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

The following fields are available:

- [EffectiveDate](#Certificate_f_EffectiveDate)

- [ExpirationDate](#Certificate_f_ExpirationDate)

- [ExtendedKeyUsage](#Certificate_f_ExtendedKeyUsage)

- [Fingerprint](#Certificate_f_Fingerprint)

- [FingerprintSHA1](#Certificate_f_FingerprintSHA1)

- [FingerprintSHA256](#Certificate_f_FingerprintSHA256)

- [Issuer](#Certificate_f_Issuer)

- [PrivateKey](#Certificate_f_PrivateKey)

- [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable)

- [PrivateKeyContainer](#Certificate_f_PrivateKeyContainer)

- [PublicKey](#Certificate_f_PublicKey)

- [PublicKeyAlgorithm](#Certificate_f_PublicKeyAlgorithm)

- [PublicKeyLength](#Certificate_f_PublicKeyLength)

- [SerialNumber](#Certificate_f_SerialNumber)

- [SignatureAlgorithm](#Certificate_f_SignatureAlgorithm)

- [Store](#Certificate_f_Store)

- [StorePassword](#Certificate_f_StorePassword)

- [StoreType](#Certificate_f_StoreType)

- [SubjectAltNames](#Certificate_f_SubjectAltNames)

- [ThumbprintMD5](#Certificate_f_ThumbprintMD5)

- [ThumbprintSHA1](#Certificate_f_ThumbprintSHA1)

- [ThumbprintSHA256](#Certificate_f_ThumbprintSHA256)

- [Usage](#Certificate_f_Usage)

- [UsageFlags](#Certificate_f_UsageFlags)

- [Version](#Certificate_f_Version)

- [Subject](#Certificate_f_Subject)

- [Encoded](#Certificate_f_Encoded)

## Fields

 **EffectiveDate** *string (read-only)*
Default: ""

The date on which this certificate becomes valid. Before this date, it is not valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:

23-Jan-2000 15:00:00.

 **ExpirationDate** *string (read-only)*
Default: ""

The date on which the certificate expires. After this date, the certificate will no longer be valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:

23-Jan-2001 15:00:00.

 **ExtendedKeyUsage** *string (read-only)*
Default: ""

A comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs).

 **Fingerprint** *string (read-only)*
Default: ""

The hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02*

 **FingerprintSHA1** *string (read-only)*
Default: ""

The hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84*

 **FingerprintSHA256** *string (read-only)*
Default: ""

The hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53*

 **Issuer** *string (read-only)*
Default: ""

The issuer of the certificate. This field contains a string representation of the name of the issuing authority for the certificate.

 **PrivateKey** *string (read-only)*
Default: ""

The private key of the certificate (if available). The key is provided as PEM/Base64-encoded data.

NOTE: The [PrivateKey](#Certificate_f_PrivateKey) may be available but not exportable. In this case, [PrivateKey](#Certificate_f_PrivateKey) returns an empty string.

 **PrivateKeyAvailable** *bool (read-only)*
Default: False

Whether a [PrivateKey](#Certificate_f_PrivateKey) is available for the selected certificate. If [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable) is True, the certificate may be used for authentication purposes (e.g., server authentication).

 **PrivateKeyContainer** *string (read-only)*
Default: ""

The name of the [PrivateKey](#Certificate_f_PrivateKey) container for the certificate (if available). This functionality is available only on Windows platforms.

 **PublicKey** *string (read-only)*
Default: ""

The public key of the certificate. The key is provided as PEM/Base64-encoded data.

 **PublicKeyAlgorithm** *string (read-only)*
Default: ""

The textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm.

 **PublicKeyLength** *int (read-only)*
Default: 0

The length of the certificate's public key (in bits). Common values are 512, 1024, and 2048.

 **SerialNumber** *string (read-only)*
Default: ""

The serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number.

 **SignatureAlgorithm** *string (read-only)*
Default: ""

The text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm.

 **Store** *string*
Default: "MY"

The name of the certificate store for the client certificate.

The [StoreType](#Certificate_f_StoreType) field denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword).

[Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) field to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) field for details.

 Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

 **StoreB** *byte []*
Default: "MY"

The name of the certificate store for the client certificate.

The [StoreType](#Certificate_f_StoreType) field denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword).

[Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) field to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) field for details.

 Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

 **StorePassword** *string*
Default: ""

If the type of certificate store requires a password, this field is used to specify the password needed to open the certificate store.

 **StoreType** *CertStoreTypes*
Default: 0

The type of certificate store for this certificate.

 The component supports both public and private keys in a variety of formats. When the *cstAuto* value is used, the component will automatically determine the type. This field can take one of the following values:

```csharp
sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11,
                               @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll",
                               "123456", // PIN
                               "CN=cert_subject");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

```csharp
certmgr.CertStoreType = CertStoreTypes.cstPKCS11;
certmgr.OnCertList += (s, e) => {
  secKeyBlob = e.CertEncoded;
};
certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll";
certmgr.CertStorePassword = "123456"; // PIN
certmgr.ListStoreCertificates();

sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

|  |  |
| --- | --- |
| 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. |
| 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. |
| 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
| 3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
| 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is only available in Java. |
| 5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is only available in Java. |
| 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| 7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
| 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| 9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
| 11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
| 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
| 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
| 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
| 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
| 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
| 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
| 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
| 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
| 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). NOTE: This store type is only available in Java and .NET. |
| 22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. NOTE: This store type is only available in Java and .NET. |
| 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, create a new [Certificate](#certificate-type) object and pass cstPKCS11 as the [StoreType](#Certificate_f_StoreType), the full path of the PKCS#11 DLL as the [Store](#Certificate_f_Store), and the PIN as the [StorePassword](#Certificate_f_StorePassword). Code Example. SSH Authentication with Security Key (without CertMgr): Alternatively, collect the necessary data using the [CertMgr](CertMgr.md#CertMgr) component by calling the [ListStoreCertificates](CertMgr.md#CertMgr_m_ListStoreCertificates) method after setting the corresponding properties accordingly. The certificate information returned in the [CertList](CertMgr.md#CertMgr_e_CertList) event's CertEncoded parameter may be saved for later use. When using a certificate obtained with this approach, pass the previously saved security key information as the [Store](#Certificate_f_Store) and set [StorePassword](#Certificate_f_StorePassword) to the PIN. Code Example. SSH Authentication with Security Key (with CertMgr): |
| 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |

 **SubjectAltNames** *string (read-only)*
Default: ""

Comma-separated lists of alternative subject names for the certificate.

 **ThumbprintMD5** *string (read-only)*
Default: ""

The MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **ThumbprintSHA1** *string (read-only)*
Default: ""

The SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **ThumbprintSHA256** *string (read-only)*
Default: ""

The SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **Usage** *string (read-only)*
Default: ""

The text description of [UsageFlags](#Certificate_f_UsageFlags).

This value will be one or more of the following strings and will be separated by commas:

- Digital Signature
- Non-Repudiation
- Key Encipherment
- Data Encipherment
- Key Agreement
- Certificate Signing
- CRL Signing
- Encipher Only

If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names.

 **UsageFlags** *int (read-only)*
Default: 0

The flags that show intended use for the certificate. The value of [UsageFlags](#Certificate_f_UsageFlags) is a combination of the following flags:

|  |  |
| --- | --- |
| 0x80 | Digital Signature |
| 0x40 | Non-Repudiation |
| 0x20 | Key Encipherment |
| 0x10 | Data Encipherment |
| 0x08 | Key Agreement |
| 0x04 | Certificate Signing |
| 0x02 | CRL Signing |
| 0x01 | Encipher Only |

Please see the [Usage](#Certificate_f_Usage) field for a text representation of [UsageFlags](#Certificate_f_UsageFlags).

This functionality currently is not available when the provider is OpenSSL.

 **Version** *string (read-only)*
Default: ""

The certificate's version number. The possible values are the strings "V1", "V2", and "V3".

 **Subject** *string*
Default: ""

The subject of the certificate used for client authentication.

This field will be populated with the full subject of the loaded certificate. When loading a certificate, the subject is used to locate the certificate in the store.

If an exact match is not found, the store is searched for subjects containing the value of the property.

If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=example@email.com". Common fields and their meanings are as follows:

| Field | Meaning |
| --- | --- |
| CN | Common Name. This is commonly a hostname like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |

If a field value contains a comma, it must be quoted.

 **Encoded** *string*
Default: ""

The certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) fields also may be used to specify a certificate.

When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string.

 **EncodedB** *byte []*
Default: ""

The certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) fields also may be used to specify a certificate.

When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string.

## Constructors

```text
public Certificate();
```

 Creates a instance whose properties can be set.

```text
public Certificate(string certificateFile);
```

 Opens * CertificateFile * and reads out the contents as an X.509 public key.

```text
public Certificate(byte[] encoded);
```

 Parses * Encoded * as an X.509 public key.

```text
public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject, string configurationString);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 * ConfigurationString * is a newline-separated list of name-value pairs that may be used to modify the default behavior. Possible values include "PersistPFXKey", which shows whether or not the PFX key is persisted after performing operations with the private key. This correlates to the PKCS12_NO_PERSIST_KEY CryptoAPI option. The default value is True (the key is persisted). "Thumbprint" - an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load. When specified, this value is used to select the certificate in the store. This is applicable to the * cstUser * , * cstMachine * , * cstPublicKeyFile * , and * cstPFXFile * store types. "UseInternalSecurityAPI" shows whether the platform (default) or the internal security API is used when performing certificate-related operations.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, string store, string storePassword, byte[] encoded);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will load * Encoded * as an X.509 certificate and search the opened store for a corresponding private key.

```text
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject, string configurationString);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, byte[] encoded);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will load * Encoded * as an X.509 certificate and search the opened store for a corresponding private key.

# RSAKey Type

Contains the typical parameters for the RSA algorithm.

## Remarks

This type is made up of fields that represent the private and public key parameters used by the RSA algorithm.

**RSA Keys**

A RSA key is made up of a number of individual parameters.

The public key consists of the following parameters:

- [Modulus](#RSAKey_f_Modulus)
- [Exponent](#RSAKey_f_Exponent)

The component also includes the [PublicKey](#RSAKey_f_PublicKey) field which holds the PEM formatted public key for ease of use. This is helpful if you are in control of both sides of the encryption/signing and decryption/signature verification process. When sending the public key to a recipient note that not all implementations will support using the PEM formatted value in [PublicKey](#RSAKey_f_PublicKey) in which case the individual parameters must be sent.

The private key may be represented in one of two ways. Both are mathematically equivalent. Private key format 1:

- [Modulus](#RSAKey_f_Modulus)
- [P](#RSAKey_f_P)
- [Q](#RSAKey_f_Q)
- [DP](#RSAKey_f_DP)
- [DQ](#RSAKey_f_DQ)

 Private key format 2 is simpler but has decreased performance when decrypting and signing. This format is:

- [Modulus](#RSAKey_f_Modulus)
- [D](#RSAKey_f_D)

 The component also include the [PrivateKey](#RSAKey_f_PrivateKey) field which holds the PEM formatted private key for ease of use. This is helpful for storing the private key more easily.

The following fields are available:

- [D](#RSAKey_f_D)

- [DP](#RSAKey_f_DP)

- [DQ](#RSAKey_f_DQ)

- [Exponent](#RSAKey_f_Exponent)

- [InverseQ](#RSAKey_f_InverseQ)

- [Modulus](#RSAKey_f_Modulus)

- [P](#RSAKey_f_P)

- [PrivateKey](#RSAKey_f_PrivateKey)

- [PublicKey](#RSAKey_f_PublicKey)

- [Q](#RSAKey_f_Q)

## Fields

 **D** *string*
Default: ""

Represents the D parameter for the RSA algorithm.

 **DB** *byte []*
Default: ""

Represents the D parameter for the RSA algorithm.

 **DP** *string*
Default: ""

Represents the DP parameter for the RSA algorithm.

 **DPB** *byte []*
Default: ""

Represents the DP parameter for the RSA algorithm.

 **DQ** *string*
Default: ""

Represents the DQ parameter for the RSA algorithm.

 **DQB** *byte []*
Default: ""

Represents the DQ parameter for the RSA algorithm.

 **Exponent** *string*
Default: ""

Represents the Exponent parameter for the RSA algorithm.

 **ExponentB** *byte []*
Default: ""

Represents the Exponent parameter for the RSA algorithm.

 **InverseQ** *string*
Default: ""

Represents the InverseQ parameter for the RSA algorithm. This parameter is optional and is automatically calculated as necessary.

 **InverseQB** *byte []*
Default: ""

Represents the InverseQ parameter for the RSA algorithm. This parameter is optional and is automatically calculated as necessary.

 **Modulus** *string*
Default: ""

Represents the Modulus parameter for the RSA algorithm.

 **ModulusB** *byte []*
Default: ""

Represents the Modulus parameter for the RSA algorithm.

 **P** *string*
Default: ""

Represents the P parameter for the RSA algorithm.

 **PB** *byte []*
Default: ""

Represents the P parameter for the RSA algorithm.

 **PrivateKey** *string*
Default: ""

This field is a PEM formatted private key. The purpose of this field is to allow easier management of the private key parameters by using only a single value.

 **PublicKey** *string*
Default: ""

This field is a PEM formatted public key. The purpose of this field is to allow easier management of the public key parameters by using only a single value.

 **Q** *string*
Default: ""

Represents the Q parameter for the RSA algorithm.

 **QB** *byte []*
Default: ""

Represents the Q parameter for the RSA algorithm.

## Constructors

```text
public RSAKey();
```

 The default constructor creates a new RSAKey instance but does not assign a public or private key.

```text
public RSAKey(byte[] modulus, byte[] exponent);
```

 The public key constructor assigns an existing public key.

```text
public RSAKey(byte[] modulus, byte[] D, byte[] P, byte[] Q, byte[] DP, byte[] DQ);
```

 The private key constructor assigns an existing private key. Any valid combination of parameters representing a private key may be supplied. See the description at the top of this page for details on RSA private key formats.

# Config Settings ([RSA](#rsa-component) Component)

 The component accepts one or more of the following *configuration settings*. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the [Config](#config-method-rsa-component) method.

### RSA Config Settings

**CloseInputStreamAfterProcessing**: Determines whether or not the input stream is closed after processing.Determines whether or not the input stream set by [SetInputStream](#setinputstream-method-rsa-component) is closed after processing is complete. The default value is True.

**CloseOutputStreamAfterProcessing**: Determines whether or not the output stream is closed after processing.Determines whether or not the output stream set by [SetOutputStream](#setoutputstream-method-rsa-component) is closed after processing is complete. The default value is True.

**KeyFormat**: How the public and private key are formatted.This setting controls the format of [PublicKey](#RSAKey_f_PublicKey) and [PrivateKey](#RSAKey_f_PrivateKey). By default these fields hold PEM formatted public and private key data. When set to 1 (XML) the keys are stored in a XML format. This only affects the values returned by the component; the actual keys remain the same regardless of this setting. Possible values are:

- 0 (PEM - PKCS#1)
- 1 (XML)
- 2 (PEM - PKCS#8 - default)

 The default value is 2 (PEM - PKCS#8).

**KeySize**: The size, in bits, of the secret key.This specifies the size, in bits, of the secret key. The minimum key size for RSA is 384. The maximum key size is 4096. Note that large values such as 4096 will impact performance. The default value is 1024.

**OAEPMGF1HashAlgorithm**: The MGF1 hash algorithm used with OAEP.This configuration setting specifies the MGF1 hash algorithm used when [UseOAEP](#useoaep-property-rsa-component) is set to True. The default value is *SHA256*. Possible values are as follows:

- "SHA1"
- "SHA224"
- "SHA256" (default)
- "SHA384"
- "SHA512"
- "RIPEMD160"
- "MD2"
- "MD5"
- "MD5SHA1"

Note: The RSA hash algorithm used for OAEP is controlled via the [HashAlgorithm](#hashalgorithm-property-rsa-component) property.

**OAEPParams**: The hex encoded OAEP parameters.This configuration setting optionally specifies Optimal Asymmetric Encryption Padding (OAEP) parameters to be used when [UseOAEP](#useoaep-property-rsa-component) is set to True. The value is an optional application-defined label and should be hex encoded. In most cases this does not need to be set; both sides must use the same value for encryption and decryption to succeed.

**UsePrimitive**: Enables primitive RSA encryption with no padding scheme or output modification.Instructs the component to use primitive RSA encryption with no padding scheme and without stripping leading zeros from the output of [Encrypt](#encrypt-method-rsa-component). The output size will match the modulus length, as defined by the original RSA specification.

 Overrides the [UseOAEP](#useoaep-property-rsa-component) property if specified.

 **Warning:** This configuration is not considered cryptographically secure on its own. Padding schemes play a critical role in the security of modern RSA implementations. Use only when necessary for compatibility, and note that the user assumes all responsibility when enabling this option.

### Base Config Settings

**BuildInfo**: Information about the product's build.When queried, this setting will return a string containing information about the product's build.

**GUIAvailable**: Whether or not a message loop is available for processing events.In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.

In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting [GUIAvailable](#GUIAvailable) to *false* will ensure that the component does not attempt to process external events.

**LicenseInfo**: Information about the current license.When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.

**MaskSensitiveData**: Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to *true* to mask sensitive data. The default is *true*.

**UseFIPSCompliantAPI**: Tells the component whether or not to use FIPS certified APIs.When set to *true*, the component will utilize the underlying operating system's certified APIs. Java editions, regardless of OS, utilize Bouncy Castle Federal Information Processing Standards (FIPS), while all other Windows editions make use of Microsoft security libraries.

FIPS mode can be enabled by setting the *UseFIPSCompliantAPI* configuration setting to *true*. This is a static setting that applies to all instances of all components of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior.

For more details, please see the [FIPS 140-2 Compliance](https://www.nsoftware.com/kb/articles/fips.rst) article.

NOTE: This setting is applicable only on Windows.

NOTE: Enabling FIPS compliance requires a special license; please contact [sales@nsoftware.com](mailto:sales@nsoftware.com) for details.

**UseInternalSecurityAPI**: Whether or not to use the system security libraries or an internal implementation. When set to *false*, the component will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments, this is not desirable. To use a completely managed security implementation, set this setting to *true*.

Setting this configuration setting to *true* tells the component to use the internal implementation instead of using the system security libraries.

 On Windows, this setting is set to *false* by default. On Linux/macOS, this setting is set to *true* by default.

NOTE: This setting is static. The value set is applicable to all components used in the application.

When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file.

# Trappable Errors ([RSA](#rsa-component) Component)

### RSA Errors

|  |  |
| --- | --- |
| 102 | No Key specified. |
| 104 | Cannot read or write file. |
| 105 | key parameters incorrect. |
| 106 | Cannot create hash. |
| 111 | OutputFile already exists and Overwrite is False. |
| 113 | Input data or HashValue must be specified. |
| 121 | Invalid certificate. |
| 124 | HashSignature must be specified. |
| 304 | Cannot write file. |
| 305 | Cannot read file. |
| 306 | Cannot create file. |
