If you don't plan to deal with certificates or
private keys, most probably you will never use this
property. But - if you plan to connect to servers that
require client certificate for the connection, or you plan
to create and use private/public keys for connecting for
SSH servers, you will need to specify this property.
This property should be set to valid ICertificate object which is part of our
'Certificate Management library' shipped with the
installation package of wodTelnetDLX. It will allow you to
Load, Save,
Generate... keys and certificates
which can be used directly by the server, or should by
signed by 3rd party authority and then used with the
server. It can combine both OpenSSL type certificates, as
well ones located in your Microsoft Windows crypto stores -
and handle them transparently.
Setting certificate is really easy. Typically, you could
do it like this:
Set Telnet1.Certificate =
New Certificate
Telnet1.Certificate.GenerateKey 0 'RSAkey
Telnet1.Certificate.SaveKey "C:\mykey.txt"
or later on
Set Telnet1.Certificate =
New Certificate
Telnet1.Certificate.LoadKey "C:\mykey.txt"
wodTelnetDLX internally will never create this object
(it only uses it), so if you don't plan to use
ICertificate object, you don't have to distribute
wodCertificate.DLL with your application.