Disabling Insecure Access; Configuring Secure Socket Layer - NETGEAR ProSafe GSM7212 Application Note

If a secure connection cannot be established, entries such as the following indicate
the nature of the problem.
In this case, the authentication credentials were invalid and should be regenerated.

Disabling Insecure Access

To disable insecure access to the NETGEAR managed switch, issue the following
command:

Configuring Secure Socket Layer

Optionally or in concert with SSH, SSL may be enabled. Once again the message
log is the best source of feedback for problem determination.
1. To enable SSL, issue the privileged EXEC mode command:
2. Attempt a secure web access using https. Consult the message log for to
determine the success or failure status.
Enabling Management Security
Application Note: Configuring and Enabling Management Security
0 days 00:17:06 Unit: 1 : File: sshd_main.c : Line: 592 :
SSHD: successfully opened file ssh_host_dsa_key
0 days 00:17:06 Unit: 1 : File: sshd_control.c : Line: 400 :
SSHD: sshdListenTask started
0 days 02:30:30 File: ssh_sys_fastpath.c : Line: 584 : tid
40052584, context 0x0x157dba0, deleting 40052584, retval = 1
0 days 02:30:30 File: ssh_sys_fastpath.c : Line: 401 : SSHD:
exiting global context 0x0x157dba0
0 days 02:30:30 File: sshd_main.c : Line: 550 : SSHD: host key
is corrupt (did not decode).
# no telnet
Note: Caution should be exercised before issuing this command as once
the active telnet sessions are terminated, no new telnet sessions
will be allowed. Please consult the appropriate Command
Reference for more information on configuring remote sessions.
# ip http secure-server
v1.0, February 2006
2-3