8304 Nokia Network Voyager for IPSO 4.0 Reference Guide5. If you entered a passphrase when you generated the certificate and private key, you mustenter the passphrase in the Passphrase field.6. Click Submit.Troubleshooting SSL/TLS ConfigurationYou might have trouble accessing Nokia Network Voyager if SSL/TLS is not configuredcorrectly. If you have trouble accessing Network Voyager, try the following remedies. Check that you are using the correct URL. When you enable SSL/TLS, you must use httpsrather than http when you connect through your Web browser, unless the Redirect HTTPRequests to HTTPS option is enabled. Check that you are using the correct PEM-encoded certificate and private key, and that theyare installed properly with the dashed begin and end lines. You can view the certificate andprivate key in the /var/etc/voyager_ssl_server.crt and /var/etc/voyager_ssl_server.key filesrespectively. Check the HTTP daemon error message log. You can find the messages in the followinglogs: /var/log/httpd_error_log and /var/log/ssl_engine_log. The messages can help youtroubleshoot further and might contain important information for Customer Support shouldyou contact them.Secure Shell (SSH)IPSO uses the Secure Shell (SSH) program to provide secure connections for the CLI. SSHallows you to securely log in to another computer over a network, execute commands on aremote platform, and move files from one platform to another platform. SSH provides aconnection similar to Telnet or rlogin, except that the traffic is encrypted and both ends areauthenticated.The Nokia SSH implementation supports both SSHv1and SSHv2. Some of the differencesbetween SSHv1 and SSHv2 include what part of the packet the protocol encrypts and how eachprotocol authenticates: SSHv1 authenticates with server and host keys, while SSHv2authenticates by using only host keys. Even though SSHv1 uses server and host-keyauthentication, SSHv2 is a more secure, faster, and more portable protocol. In some cases,SSHv1 might be more suitable because of your client software or your need to use theauthentication modes of the protocol.Properly used, SSH provides you with session protection from the following security threats: DNS spoofing Interception of passwords IP spoofing IP source routing Person-in-the-middle attacks (SSHv2 only)
