ECC Configuration

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

ECC Configuration Settings


	KeySize: The size, in bits, of the secret key. This setting specifies the size, in bits, of the secret key. This is applicable when calling CreateKey. Possible values are: 256 (default) 384 521
	Curve: The elliptic curve. This setting specifies the elliptic curve to use when calling CreateKey. Possible values are: secp256r1 (default) secp384r1 secp521r1
	CNGECDSAKey: The CNG ECDSA key. This setting may be set to specify the key exported from Microsoft's CNG before calling VerifySignature. If key data was obtained from Microsoft's CNG API it can be hex encoded and supplied here. The component will use this key when VerifySignature is called.
	CNGECDHKey: The CNG ECDH key. This setting may be set to specify the key exported from Microsoft's CNG before calling ComputeSecret. If key data was obtained from Microsoft's CNG API it can be hex encoded and supplied here. The component will use this key when ComputeSecret is called.
	PrependSecret: An optional string to prepend to the secret agreement. This setting specifies an optional string to prepend to the secret agreement before hashing it. This is applicable when calling ComputeSecret. Note: This is not applicable when KeyDerivationFunction is set to 12 (ekdTLS).
	AppendSecret: An optional string to append to the secret agreement. This setting specifies an optional string to append to the secret agreement before hashing it. This is applicable when calling ComputeSecret. Note: This is not applicable when KeyDerivationFunction is set to 12 (ekdTLS).
	HMACKey: A key to use when generating a Hash-based Message Authentication Code (HMAC). This key is incorporated into the hashing process to add entropy to the resulting hash code, making the plaintext harder to guess and increasing the message security. The value supplied here must be hex encoded.
	TLSSeed: The TLS PRF Seed. This setting specifies the hex encoded TLS PRF Seed. The seed value must be 64 bytes in length before hex encoding. This setting is required when KeyDerivationFunction set to 12 (ekdTLS). It is only applicable when calling ComputeSecret.
	TLSLabel: The TLS PRF label. This setting specifies a string representing the PRF label. This setting is required when KeyDerivationFunction set to 12 (ekdTLS). It is only applicable when calling ComputeSecret.

Base Configuration Settings


	GUIAvailable: Tells the component 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 to false will ensure that the component does not attempt to process external events.
	UseBackgroundThread: Whether threads created by the component are background threads. If set to True, when the component creates a thread the thread's IsBackground property will be explicitly set to True. By default this setting is False.
	UseManagedSecurityAPI: Tells the component whether or not to use the system security libraries or a managed implementation. By default the component will use the system security libraries to perform cryptographic functions. This means 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 to True tells the component to use the internal managed implementation instead of using the system's security API. Note that when this value is set the product's system dll is no longer required as a reference, as all unmanaged code is stored in this file.