HP 3PAR StoreServ 7400 2-node HP 3PAR Command Line Interface Administrator& - Page 55

HP 3PAR Common Criteria, Administrator's Reference, ssh-keygen, the password

Page 55 highlights

CAUTION: For security purposes, the file containing the private key must be protected from unauthorized access. Failure to protect the file can cause the key to be compromised. CAUTION: If the system is operating in Common Criteria mode, LDAP users must not use a public key. For more information about Common Criteria, see the HP 3PAR Common Criteria Administrator's Reference. • The public key must be stored on the system using the setsshkey command to enable users to log in without a password. • The private key must be kept in a file accessible by scripts that use CLI commands. The key pair is generated by using the ssh-keygen utility (typically included in an SSH client software package and available on UNIX and Windows platforms). NOTE: The following screen examples show output for UNIX systems. Windows screens are simlar, with DOS prompts replacing UNIX prompts. The following steps describe setting up CLI scripting through SSH: 1. Create a CLI user and password using the createuser command. $ssh user1@system1 3paradm's password: ****** system1 cli% createuser -c testpw3 user3 all browse User created In the previous example, user user1 logs into system system1 and creates user user3 with the password testpw3. 2. Create a key pair using the ssh-keygen utility. Both rsa and dsa key formats are supported by the system, and the recommended key length is at least 1024 characters. NOTE: For additional information about the ssh-keygen utility and rsa and dsa key formats, consult the SSH client documentation. To create a key pair using rsa format: $ ssh-keygen -b 1024 -t rsa To create a key pair using dsa format: $ ssh-keygen -b 1024 -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/home/usr/user3/.ssh/id_dsa): Created directory '/home/usr/user3/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/usr/user3/.ssh/id_dsa. Your public key has been saved in /home/usr/user3/.ssh/id_dsa.pub. The key fingerprint is: 3f:a0:b5:6a:4d:dd:45:76:37:fb:a3:3e:52:44:55:32 [email protected] SSH 55

  • 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
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

CAUTION:
For security purposes, the file containing the private key must be protected from
unauthorized access. Failure to protect the file can cause the key to be compromised.
CAUTION:
If the system is operating in Common Criteria mode, LDAP users must not use a public
key. For more information about Common Criteria, see the
HP 3PAR Common Criteria
Administrator’s Reference
.
The public key must be stored on the system using the
setsshkey
command to enable users
to log in without a password.
The private key must be kept in a file accessible by scripts that use CLI commands.
The key pair is generated by using the
ssh–keygen
utility (typically included in an SSH client
software package and available on UNIX and Windows platforms).
NOTE:
The following screen examples show output for UNIX systems. Windows screens are
simlar, with DOS prompts replacing UNIX prompts.
The following steps describe setting up CLI scripting through SSH:
1.
Create a CLI user and password using the
createuser
command.
$ssh user1@system1
3paradm
s password: ******
system1 cli% createuser
c testpw3 user3 all browse
User created
In the previous example, user
user1
logs into system
system1
and creates user
user3
with
the password
testpw3
.
2.
Create a key pair using the
ssh–keygen
utility. Both
rsa
and
dsa
key formats are supported
by the system, and the recommended key length is at least 1024 characters.
NOTE:
For additional information about the
ssh–keygen
utility and
rsa
and
dsa
key formats,
consult the SSH client documentation.
To create a key pair using
rsa
format:
$ ssh
keygen
b 1024
t rsa
To create a key pair using
dsa
format:
$ ssh
keygen
b 1024
t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/home/usr/user3/.ssh/id_dsa):
Created directory '/home/usr/user3/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/usr/user3/.ssh/id_dsa.
Your public key has been saved in /home/usr/user3/.ssh/id_dsa.pub.
The key fingerprint is:
3f:a0:b5:6a:4d:dd:45:76:37:fb:a3:3e:52:44:55:32 [email protected]
SSH
55