1 .\" $OpenBSD: ssh-keygen.1,v 1.69 2005/06/08 03:50:00 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 known_hosts_file
88 .Op Fl f Ar known_hosts_file
91 .Op Fl f Ar known_hosts_file
94 .Op Fl f Ar input_keyfile
97 .Op Fl f Ar input_keyfile
104 .Op Fl S Ar start_point
109 .Op Fl a Ar num_trials
110 .Op Fl W Ar generator
113 generates, manages and converts authentication keys for
116 can create RSA keys for use by SSH protocol version 1 and RSA or DSA
117 keys for use by SSH protocol version 2.
118 The type of key to be generated is specified with the
123 is also used to generate groups for use in Diffie-Hellman group
126 .Sx MODULI GENERATION
129 Normally each user wishing to use SSH
130 with RSA or DSA authentication runs this once to create the authentication
132 .Pa ~/.ssh/identity ,
136 Additionally, the system administrator may use this to generate host keys,
140 Normally this program generates the key and asks for a file in which
141 to store the private key.
142 The public key is stored in a file with the same name but
145 The program also asks for a passphrase.
146 The passphrase may be empty to indicate no passphrase
147 (host keys must have an empty passphrase), or it may be a string of
149 A passphrase is similar to a password, except it can be a phrase with a
150 series of words, punctuation, numbers, whitespace, or any string of
152 Good passphrases are 10-30 characters long, are
153 not simple sentences or otherwise easily guessable (English
154 prose has only 1-2 bits of entropy per character, and provides very bad
155 passphrases), and contain a mix of upper and lowercase letters,
156 numbers, and non-alphanumeric characters.
157 The passphrase can be changed later by using the
161 There is no way to recover a lost passphrase.
163 lost or forgotten, a new key must be generated and copied to the
164 corresponding public key to other machines.
167 there is also a comment field in the key file that is only for
168 convenience to the user to help identify the key.
169 The comment can tell what the key is for, or whatever is useful.
170 The comment is initialized to
172 when the key is created, but can be changed using the
176 After a key is generated, instructions below detail where the keys
177 should be placed to be activated.
179 The options are as follows:
182 Specifies the number of primality tests to perform when screening DH-GEX
187 Show the bubblebabble digest of specified private or public key file.
189 Specifies the number of bits in the key to create.
191 Generally, 2048 bits is considered sufficient.
192 The default is 2048 bits.
194 Provides a new comment.
196 Requests changing the comment in the private and public key files.
197 This operation is only supported for RSA1 keys.
198 The program will prompt for the file containing the private keys, for
199 the passphrase if the key has one, and for the new comment.
201 Download the RSA public key stored in the smartcard in
204 This option will read a private or public OpenSSH key file and
206 .Sq SECSH Public Key File Format
208 This option allows exporting keys for use by several commercial
211 Search for the specified
215 file, listing any occurrences found.
216 This option is useful to find hashed host names or addresses and may also be
217 used in conjunction with the
219 option to print found keys in a hashed format.
221 Specifies the filename of the key file.
222 .It Fl G Ar output_file
223 Generate candidate primes for DH-GEX.
224 These primes must be screened for
229 Use generic DNS format when printing fingerprint resource records using the
236 This replaces all hostnames and addresses with hashed representations
237 within the specified file; the original content is moved to a file with
239 These hashes may be used normally by
243 but they do not reveal identifying information should the file's contents
245 This option will not modify existing hashed hostnames and is therefore safe
246 to use on files that mix hashed and non-hashed names.
248 This option will read an unencrypted private (or public) key file
249 in SSH2-compatible format and print an OpenSSH compatible private
250 (or public) key to stdout.
253 .Sq SECSH Public Key File Format .
254 This option allows importing keys from several commercial
257 Show fingerprint of specified public key file.
258 Private RSA1 keys are also supported.
261 tries to find the matching public key file and prints its fingerprint.
263 Specify the amount of memory to use (in megabytes) when generating
264 candidate moduli for DH-GEX.
265 .It Fl N Ar new_passphrase
266 Provides the new passphrase.
267 .It Fl P Ar passphrase
268 Provides the (old) passphrase.
270 Requests changing the passphrase of a private key file instead of
271 creating a new private key.
272 The program will prompt for the file
273 containing the private key, for the old passphrase, and twice for the
280 when creating a new key.
282 Removes all keys belonging to
287 This option is useful to delete hashed hosts (see the
291 Print the SSHFP fingerprint resource record named
293 for the specified public key file.
295 Specify start point (in hex) when generating candidate moduli for DH-GEX.
296 .It Fl T Ar output_file
297 Test DH group exchange candidate primes (generated using the
301 Specifies the type of key to create.
302 The possible values are
304 for protocol version 1 and
308 for protocol version 2.
310 Upload an existing RSA private key into the smartcard in
316 to print debugging messages about its progress.
317 This is helpful for debugging moduli generation.
320 options increase the verbosity.
322 .It Fl W Ar generator
323 Specify desired generator when testing candidate moduli for DH-GEX.
325 This option will read a private
326 OpenSSH format file and print an OpenSSH public key to stdout.
328 .Sh MODULI GENERATION
330 may be used to generate groups for the Diffie-Hellman Group Exchange
332 Generating these groups is a two-step process: first, candidate
333 primes are generated using a fast, but memory intensive process.
334 These candidate primes are then tested for suitability (a CPU-intensive
337 Generation of primes is performed using the
340 The desired length of the primes may be specified by the
345 .Dl # ssh-keygen -G moduli-2048.candidates -b 2048
347 By default, the search for primes begins at a random point in the
348 desired length range.
349 This may be overridden using the
351 option, which specifies a different start point (in hex).
353 Once a set of candidates have been generated, they must be tested for
355 This may be performed using the
360 will read candidates from standard input (or a file specified using the
365 .Dl # ssh-keygen -T moduli-2048 -f moduli-2048.candidates
367 By default, each candidate will be subjected to 100 primality tests.
368 This may be overridden using the
371 The DH generator value will be chosen automatically for the
372 prime under consideration.
373 If a specific generator is desired, it may be requested using the
376 Valid generator values are 2, 3, and 5.
378 Screened DH groups may be installed in
380 It is important that this file contains moduli of a range of bit lengths and
381 that both ends of a connection share common moduli.
384 .It Pa ~/.ssh/identity
385 Contains the protocol version 1 RSA authentication identity of the user.
386 This file should not be readable by anyone but the user.
388 specify a passphrase when generating the key; that passphrase will be
389 used to encrypt the private part of this file using 3DES.
390 This file is not automatically accessed by
392 but it is offered as the default file for the private key.
394 will read this file when a login attempt is made.
395 .It Pa ~/.ssh/identity.pub
396 Contains the protocol version 1 RSA public key for authentication.
397 The contents of this file should be added to
398 .Pa ~/.ssh/authorized_keys
400 where the user wishes to log in using RSA authentication.
401 There is no need to keep the contents of this file secret.
403 Contains the protocol version 2 DSA authentication identity of the user.
404 This file should not be readable by anyone but the user.
406 specify a passphrase when generating the key; that passphrase will be
407 used to encrypt the private part of this file using 3DES.
408 This file is not automatically accessed by
410 but it is offered as the default file for the private key.
412 will read this file when a login attempt is made.
413 .It Pa ~/.ssh/id_dsa.pub
414 Contains the protocol version 2 DSA public key for authentication.
415 The contents of this file should be added to
416 .Pa ~/.ssh/authorized_keys
418 where the user wishes to log in using public key authentication.
419 There is no need to keep the contents of this file secret.
421 Contains the protocol version 2 RSA authentication identity of the user.
422 This file should not be readable by anyone but the user.
424 specify a passphrase when generating the key; that passphrase will be
425 used to encrypt the private part of this file using 3DES.
426 This file is not automatically accessed by
428 but it is offered as the default file for the private key.
430 will read this file when a login attempt is made.
431 .It Pa ~/.ssh/id_rsa.pub
432 Contains the protocol version 2 RSA public key for authentication.
433 The contents of this file should be added to
434 .Pa ~/.ssh/authorized_keys
436 where the user wishes to log in using public key authentication.
437 There is no need to keep the contents of this file secret.
439 Contains Diffie-Hellman groups used for DH-GEX.
440 The file format is described in
452 .%T "SECSH Public Key File Format"
453 .%N draft-ietf-secsh-publickeyfile-01.txt
455 .%O work in progress material
458 OpenSSH is a derivative of the original and free
459 ssh 1.2.12 release by Tatu Ylonen.
460 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
461 Theo de Raadt and Dug Song
462 removed many bugs, re-added newer features and
464 Markus Friedl contributed the support for SSH
465 protocol versions 1.5 and 2.0.