1 .\" $OpenBSD: ssh-keygen.1,v 1.61 2003/12/22 09:16:58 djm Exp $
5 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
6 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
7 .\" All rights reserved
9 .\" As far as I am concerned, the code I have written for this software
10 .\" can be used freely for any purpose. Any derived versions of this
11 .\" software must be clearly marked as such, and if the derived work is
12 .\" incompatible with the protocol description in the RFC file, it must be
13 .\" called by a name other than "ssh" or "Secure Shell".
16 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
17 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
18 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
20 .\" Redistribution and use in source and binary forms, with or without
21 .\" modification, are permitted provided that the following conditions
23 .\" 1. Redistributions of source code must retain the above copyright
24 .\" notice, this list of conditions and the following disclaimer.
25 .\" 2. Redistributions in binary form must reproduce the above copyright
26 .\" notice, this list of conditions and the following disclaimer in the
27 .\" documentation and/or other materials provided with the distribution.
29 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
30 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
31 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
32 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
33 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
34 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
35 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
36 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
37 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
38 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
40 .Dd September 25, 1999
45 .Nd authentication key generation, management and conversion
52 .Op Fl N Ar new_passphrase
54 .Op Fl f Ar output_keyfile
58 .Op Fl P Ar old_passphrase
59 .Op Fl N Ar new_passphrase
63 .Op Fl f Ar input_keyfile
66 .Op Fl f Ar input_keyfile
69 .Op Fl f Ar input_keyfile
72 .Op Fl P Ar passphrase
77 .Op Fl f Ar input_keyfile
80 .Op Fl f Ar input_keyfile
85 .Op Fl f Ar input_keyfile
88 .Op Fl f Ar input_keyfile
95 .Op Fl S Ar start_point
100 .Op Fl a Ar num_trials
101 .Op Fl W Ar generator
104 generates, manages and converts authentication keys for
107 can create RSA keys for use by SSH protocol version 1 and RSA or DSA
108 keys for use by SSH protocol version 2.
109 The type of key to be generated is specified with the
114 is also used to generate groups for use in Diffie-Hellman group
117 .Sx MODULI GENERATION
120 Normally each user wishing to use SSH
121 with RSA or DSA authentication runs this once to create the authentication
123 .Pa $HOME/.ssh/identity ,
124 .Pa $HOME/.ssh/id_dsa
126 .Pa $HOME/.ssh/id_rsa .
127 Additionally, the system administrator may use this to generate host keys,
131 Normally this program generates the key and asks for a file in which
132 to store the private key.
133 The public key is stored in a file with the same name but
136 The program also asks for a passphrase.
137 The passphrase may be empty to indicate no passphrase
138 (host keys must have an empty passphrase), or it may be a string of
140 A passphrase is similar to a password, except it can be a phrase with a
141 series of words, punctuation, numbers, whitespace, or any string of
143 Good passphrases are 10-30 characters long, are
144 not simple sentences or otherwise easily guessable (English
145 prose has only 1-2 bits of entropy per character, and provides very bad
146 passphrases), and contain a mix of upper and lowercase letters,
147 numbers, and non-alphanumeric characters.
148 The passphrase can be changed later by using the
152 There is no way to recover a lost passphrase.
154 lost or forgotten, a new key must be generated and copied to the
155 corresponding public key to other machines.
158 there is also a comment field in the key file that is only for
159 convenience to the user to help identify the key.
160 The comment can tell what the key is for, or whatever is useful.
161 The comment is initialized to
163 when the key is created, but can be changed using the
167 After a key is generated, instructions below detail where the keys
168 should be placed to be activated.
170 The options are as follows:
173 Specifies the number of primality tests to perform when screening DH-GEX
178 Specifies the number of bits in the key to create.
180 Generally, 1024 bits is considered sufficient.
181 The default is 1024 bits.
183 Requests changing the comment in the private and public key files.
184 This operation is only supported for RSA1 keys.
185 The program will prompt for the file containing the private keys, for
186 the passphrase if the key has one, and for the new comment.
188 This option will read a private or public OpenSSH key file and
190 .Sq SECSH Public Key File Format
192 This option allows exporting keys for use by several commercial
195 Use generic DNS resource record format.
197 Specifies the filename of the key file.
199 This option will read an unencrypted private (or public) key file
200 in SSH2-compatible format and print an OpenSSH compatible private
201 (or public) key to stdout.
204 .Sq SECSH Public Key File Format .
205 This option allows importing keys from several commercial
208 Show fingerprint of specified public key file.
209 Private RSA1 keys are also supported.
212 tries to find the matching public key file and prints its fingerprint.
214 Requests changing the passphrase of a private key file instead of
215 creating a new private key.
216 The program will prompt for the file
217 containing the private key, for the old passphrase, and twice for the
224 when creating a new key.
226 This option will read a private
227 OpenSSH format file and print an OpenSSH public key to stdout.
229 Specifies the type of the key to create.
230 The possible values are
232 for protocol version 1 and
236 for protocol version 2.
238 Show the bubblebabble digest of specified private or public key file.
240 Provides the new comment.
242 Download the RSA public key stored in the smartcard in
244 .It Fl G Ar output_file
245 Generate candidate primes for DH-GEX.
246 These primes must be screened for
251 Specify the amount of memory to use (in megabytes) when generating
252 candidate moduli for DH-GEX.
253 .It Fl N Ar new_passphrase
254 Provides the new passphrase.
255 .It Fl P Ar passphrase
256 Provides the (old) passphrase.
258 Specify start point (in hex) when generating candidate moduli for DH-GEX.
259 .It Fl T Ar output_file
260 Test DH group exchange candidate primes (generated using the
263 .It Fl W Ar generator
264 Specify desired generator when testing candidate moduli for DH-GEX.
266 Upload an existing RSA private key into the smartcard in
272 to print debugging messages about its progress.
273 This is helpful for debugging moduli generation.
276 options increase the verbosity.
279 Print DNS resource record with the specified
282 .Sh MODULI GENERATION
284 may be used to generate groups for the Diffie-Hellman Group Exchange
286 Generating these groups is a two-step process: first, candidate
287 primes are generated using a fast, but memory intensive process.
288 These candidate primes are then tested for suitability (a CPU-intensive
291 Generation of primes is performed using the
294 The desired length of the primes may be specified by the
299 .Dl ssh-keygen -G moduli-2048.candidates -b 2048
301 By default, the search for primes begins at a random point in the
302 desired length range.
303 This may be overridden using the
305 option, which specifies a different start point (in hex).
307 Once a set of candidates have been generated, they must be tested for
309 This may be performed using the
314 will read candidates from standard input (or a file specified using the
319 .Dl ssh-keygen -T moduli-2048 -f moduli-2048.candidates
321 By default, each candidate will be subjected to 100 primality tests.
322 This may be overridden using the
325 The DH generator value will be chosen automatically for the
326 prime under consideration.
327 If a specific generator is desired, it may be requested using the
330 Valid generator values are 2, 3 and 5.
332 Screened DH groups may be installed in
334 It is important that this file contains moduli of a range of bit lengths and
335 that both ends of a connection share common moduli.
338 .It Pa $HOME/.ssh/identity
339 Contains the protocol version 1 RSA authentication identity of the user.
340 This file should not be readable by anyone but the user.
342 specify a passphrase when generating the key; that passphrase will be
343 used to encrypt the private part of this file using 3DES.
344 This file is not automatically accessed by
346 but it is offered as the default file for the private key.
348 will read this file when a login attempt is made.
349 .It Pa $HOME/.ssh/identity.pub
350 Contains the protocol version 1 RSA public key for authentication.
351 The contents of this file should be added to
352 .Pa $HOME/.ssh/authorized_keys
354 where the user wishes to log in using RSA authentication.
355 There is no need to keep the contents of this file secret.
356 .It Pa $HOME/.ssh/id_dsa
357 Contains the protocol version 2 DSA authentication identity of the user.
358 This file should not be readable by anyone but the user.
360 specify a passphrase when generating the key; that passphrase will be
361 used to encrypt the private part of this file using 3DES.
362 This file is not automatically accessed by
364 but it is offered as the default file for the private key.
366 will read this file when a login attempt is made.
367 .It Pa $HOME/.ssh/id_dsa.pub
368 Contains the protocol version 2 DSA public key for authentication.
369 The contents of this file should be added to
370 .Pa $HOME/.ssh/authorized_keys
372 where the user wishes to log in using public key authentication.
373 There is no need to keep the contents of this file secret.
374 .It Pa $HOME/.ssh/id_rsa
375 Contains the protocol version 2 RSA authentication identity of the user.
376 This file should not be readable by anyone but the user.
378 specify a passphrase when generating the key; that passphrase will be
379 used to encrypt the private part of this file using 3DES.
380 This file is not automatically accessed by
382 but it is offered as the default file for the private key.
384 will read this file when a login attempt is made.
385 .It Pa $HOME/.ssh/id_rsa.pub
386 Contains the protocol version 2 RSA public key for authentication.
387 The contents of this file should be added to
388 .Pa $HOME/.ssh/authorized_keys
390 where the user wishes to log in using public key authentication.
391 There is no need to keep the contents of this file secret.
393 Contains Diffie-Hellman groups used for DH-GEX.
394 The file format is described in
406 .%T "SECSH Public Key File Format"
407 .%N draft-ietf-secsh-publickeyfile-01.txt
409 .%O work in progress material
412 OpenSSH is a derivative of the original and free
413 ssh 1.2.12 release by Tatu Ylonen.
414 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
415 Theo de Raadt and Dug Song
416 removed many bugs, re-added newer features and
418 Markus Friedl contributed the support for SSH
419 protocol versions 1.5 and 2.0.