Minicom Advanced Systems 5UM20114 - Manual (Page 43)

OPERATING GUIDE
.
42
Figure 30 Security Settings
SSL settings
Force HTTPS - Access the Web front-end only using an HTTPS connection.
Smart 16 IP won't listen on the HTTP port for incoming connections.
KVM encryption - Controls the encrypting of the RFB protocol, used by the
Remote Console to transmit the screen data to the administrator machine and
keyboard and mouse data back to the host.
Off - No encrypting used.
Try - Tries to make an encrypted connection. If unsuccessful, an unencrypted
connection is used.
Force - Tries to make an encrypted connection.
SSL Certificate Management
Smart 16 IP uses the SSL (Secure Socket Layer) protocol for any encrypted
network traffic between itself and a connected client. When connecting, Smart 16
IP reveals its identity to a client using a cryptographic certificate. This is the same
for all Smart 16 IPs and won't match the network configurations applied to the
card by its user. The certificate's underlying secret key is also used for securing
the SSL handshake. Hence, this is a security risk (but better than no encryption at
all).
You can generate and install a new certificate unique to a particular card. Smart
16 IP can generate a new cryptographic key and the associated Certificate Signing
Request that needs to be certified by a certification authority (CA). A CA verifies
you are who you claim to be and signs and issues a SSL certificate to you.
To create and install a Smart 16 IP SSL certificate: