Lenovo RD220 User Guide - Page 51

Generating a Secure Shell server key, Enabling the Secure Shell server, Using the configuration file

Page 51 highlights

Generating a Secure Shell server key A Secure Shell server key is used to authenticate the identity of the Secure Shell server to the client. Secure shell must be disabled before you create a new Secure Shell server private key. You must create a server key before you enable the Secure Shell server. When you request a new server key, both a Rivest, Shamir, and Adelman key and a DSA key are created to allow access to the IMM from an SSH version 2 client. For security, the Secure Shell server private key is not backed up during a configuration save and restore operation. To create a new Secure Shell server key, complete the following steps: 1. In the navigation pane, click Security. 2. Scroll to the Secure Shell (SSH) Server area and make sure that the Secure Shell server is disabled. If it is not disabled, select Disabled in the SSH Server field and then click Save. 3. Scroll to the SSH Server Key Management area. 4. Click Generate SSH Server Private Key. A progress window opens. Wait for the operation to be completed. Enabling the Secure Shell server From the Security page you can enable or disable the Secure Shell server. The selection that you make takes effect only after the IMM is restarted. The value that is displayed on the screen (Enabled or Disabled) is the last selected value and is the value that is used when the IMM is restarted. Note: You can enable the Secure Shell server only if a valid Secure Shell server private key is installed. To enable the Secure Shell server, complete the following steps: 1. In the navigation pane, click Security. 2. Scroll to the Secure Shell (SSH) Server area. 3. Click Enabled in the SSH Server field. 4. In the navigation pane, click Restart IMM to restart the IMM. Using the Secure Shell server If you are using the Secure Shell client that is included in Red Hat Linux version 7.3, to start a Secure Shell session to an IMM with network address 192.168.70.132, type a command similar to the following example: ssh -x -l userid 192.168.70.132 where -x indicates no X Window System forwarding and -l indicates that the session should use the user ID userid. Using the configuration file Select Configuration File in the navigation pane to back up and restore the IMM configuration. Important: Security page settings are not saved with the backup operation and cannot be restored with the restore operation. Chapter 3. Configuring the IMM 45

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120

Generating a Secure Shell server key
A Secure Shell server key is used to authenticate the identity of the Secure Shell
server to the client. Secure shell must be disabled before you create a new Secure
Shell server private key. You must create a server key before you enable the Secure
Shell server.
When you request a new server key, both a Rivest, Shamir, andAdelman key and
a DSA key are created to allow access to the IMM from an SSH version 2 client.
For security, the Secure Shell server private key is not backed up during a
configuration save and restore operation.
To create a new Secure Shell server key, complete the following steps:
1.
In the navigation pane, click
Security
.
2.
Scroll to the
Secure Shell (SSH) Server
area and make sure that the Secure
Shell server is disabled. If it is not disabled, select
Disabled
in the
SSH Server
field and then click
Save
.
3.
Scroll to the
SSH Server Key Management
area.
4.
Click
Generate SSH Server Private Key
. A progress window opens. Wait for
the operation to be completed.
Enabling the Secure Shell server
From the Security page you can enable or disable the Secure Shell server. The
selection that you make takes effect only after the IMM is restarted. The value that
is displayed on the screen (Enabled or Disabled) is the last selected value and is
the value that is used when the IMM is restarted.
Note:
You can enable the Secure Shell server only if a valid Secure Shell server
private key is installed.
To enable the Secure Shell server, complete the following steps:
1.
In the navigation pane, click
Security
.
2.
Scroll to the
Secure Shell (SSH) Server
area.
3.
Click
Enabled
in the
SSH Server
field.
4.
In the navigation pane, click
Restart IMM
to restart the IMM.
Using the Secure Shell server
If you are using the Secure Shell client that is included in Red Hat Linux version
7.3, to start a Secure Shell session to an IMM with network address 192.168.70.132,
type a command similar to the following example:
ssh -x -l
userid
192.168.70.132
where -x indicates no X Window System forwarding and -l indicates that the
session should use the user ID
userid
.
Using the configuration file
Select
Configuration File
in the navigation pane to back up and restore the IMM
configuration.
Important:
Security page settings are not saved with the backup operation and
cannot be restored with the restore operation.
Chapter 3. Configuring the IMM
45