User manual
Table Of Contents
- 1. Welcome
- 2. Introduction
- 3. Features of DX User IP
- 4. DX User IP components
- 5. Cables
- 6. DX User IP front panel
- 7. DX User IP rear panel
- 8. Rack mounting the DX User IP
- 9. Pre-installation guidelines
- 10. Mouse synchronization limitations
- 11. DX User IP connections
- 12. Connecting the DX User IP to the Wan/LAN
- 13. Local User
- 14. Connecting an RS232 terminal
- 15. Order of powering on
- 16. Configuring the system
- 17. The DX User IP system interface
- 18. Logging in
- 19. Timeout
- 20. The Work area
- 21. Remote Console Settings
- 22. Telnet Console
- 23. Status via IPMI
- 24. Event Log via IPMI
- 25. File transfer – Virtual Floppy
- 26. Power Control
- 27. Keyboard & Mouse Settings
- 28. KVM Settings
- 29. KVM Port Settings
- 30. Video Settings
- 31. User/Group Management
- 32. User/Group Permissions
- 33. Network Settings
- 34. Dynamic DNS
- 35. Serial Port Settings
- 36. Security Settings
- 37. SNMP Settings
- 38. IPMI Settings
- 39. LDAP Settings
- 40. Maintenance
- 41. Accessing the remote console
- 42. Keyboard layout
- 43. The Control buttons /toolbar icons
- 44. The Chat window
- 45. The Video settings
- 46. Video Settings access
- 47. Mouse synchronization
- Frequently Asked Questions
- Glossary of terms
- Appendix A: DX User IP Video modes
- Appendix B: Key codes
- Appendix C: Pin assignments
- Appendix D: Disabling mouse acceleration
- Appendix E: Technical specifications
USER GUIDE
42
Figure 34 Security Settings
SSL settings
Force HTTPS - Access the Web front-end only using an HTTPS connection. DX
User 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 encryption used.
Try - Tries to make an encrypted connection. If unsuccessful, an unencrypted
connection is used.
Force - Makes an encrypted connection.
SSL Certificate Management
DX User IP uses the SSL (Secure Socket Layer) protocol for any encrypted network
traffic between itself and a connected client. When connecting, DX User IP reveals
its identity to a client using a cryptographic certificate. This is the same for all DX
User 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. DX User
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.