HP T5730 TeemTalk 6.0 for Windows User Manual - Page 100

Host Connection Settings 2 Client certificates. These are sent by the client, only if the server requests them, and validate the client's identity. The client will need to store these locally. Usually a client will only have one certificate to validate it on a particular server but different servers may require different client certificates. 3 CA (Certificate Authority) or root certificates. These are used to authenticate the other two types. The client will need to store these locally. Storage of Certificates TeemTalk stores its certificates in the Registry as binary values. The following keys are used: HKEY_CURRENT_USER\Software\Neoware\Security\SSL\CA Certificates HKEY_CURRENT_USER\Software\Neoware\Security\SSL\Client Certificates CA (root) Certificates are stored unencrypted. The value name in the registry is in the form HHHHHHHH.UU where HHHHHHHH is the hash of the certificate's internal name and UU is a unique number. The UU section is to allow different certificates which happen to have the same hash value co-exist. This follows the convention used by openSSL file based system. TeemTalk will automatically discard any duplicate certificates. Client Certificates are stored encrypted. The value name may be any valid string of characters. Acquiring New Certificates There are two ways a client may acquire new certificates. They may be added directly to the registry keys detailed above or they may be installed on the file system and imported manually by TeemTalk. Adding to the Registry New CA (root) Certificates should be added to the CA Certificates key with a value name in the form NEWXXXXXXXX where XXXXXXXX is a unique number. Whenever it uses its certificate's, TeemTalk first scans the registry for any value name NEW*. If it 78 SSL Connection Settings