<p>The DH-8192 / Shacal-256 Secured Transport is a so-called Wrapper Transport. It encrypts requests and responses before they are sent via another regular transport like TCP/IP or Named Pipes. It has the following options:</p>
<p class=h3><span>Respond to Broadcast</span></p>
<p>When this option is active, it instructs the server to send back its identification and version number on broadcast requests received via the regular transport being used.</p>
<p class=h3><span>Key Pair Expires</span></p>
<p>All DH transports will generate a private/public key pair when activated for the first time. The private key of this key pair must be kept absolutely secret 
and private to the server instance that uses it for authentication. However, even 
if the server is kept secure, the private key run a risk of leaking to an 
adversary. This might in some cases happen due to crypto-analysis, but with an
even higher probability when the server instance system data 
is backed up or copied to a new hard drive. Therefore, all key pairs are set to 
expire, by default one year after generation. If the expiration date has passed when
the component is activated, a new key pair is automatically generated. </p>
<p class=h3><span>Public Key</span></p>
<p>The public key is the public part of the server key pair. This value must be 
copied and transported securely out-of-band to the each client, where it is 
assigned to the RemotePublicKey property of the client side transport. Alternatively, the server public key might be embedded in a certificate, which is 
issued by the authority assigned by the software manufacturer.</p>
<p class=h3><span>Certificate</span></p>
<p>A certificate is a public key signed by an authority that is trusted by the 
clients. The certificate contains the server public key, an expiration date and
a unique name that identifies the server to the client. The server must enter
the certificate in the edit box on this page after it has been signed by the 
authority.</p>