1 .\" $OpenBSD: ssh-keygen.1,v 1.79 2008/07/24 23:55:30 sthen 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 $Mdocdate: July 24 2008 $
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
89 .Op Fl f Ar known_hosts_file
92 .Op Fl f Ar known_hosts_file
95 .Op Fl f Ar input_keyfile
98 .Op Fl f Ar input_keyfile
105 .Op Fl S Ar start_point
110 .Op Fl a Ar num_trials
111 .Op Fl W Ar generator
114 generates, manages and converts authentication keys for
117 can create RSA keys for use by SSH protocol version 1 and RSA or DSA
118 keys for use by SSH protocol version 2.
119 The type of key to be generated is specified with the
122 If invoked without any arguments,
124 will generate an RSA key for use in SSH protocol 2 connections.
127 is also used to generate groups for use in Diffie-Hellman group
130 .Sx MODULI GENERATION
133 Normally each user wishing to use SSH
134 with RSA or DSA authentication runs this once to create the authentication
136 .Pa ~/.ssh/identity ,
140 Additionally, the system administrator may use this to generate host keys,
144 Normally this program generates the key and asks for a file in which
145 to store the private key.
146 The public key is stored in a file with the same name but
149 The program also asks for a passphrase.
150 The passphrase may be empty to indicate no passphrase
151 (host keys must have an empty passphrase), or it may be a string of
153 A passphrase is similar to a password, except it can be a phrase with a
154 series of words, punctuation, numbers, whitespace, or any string of
156 Good passphrases are 10-30 characters long, are
157 not simple sentences or otherwise easily guessable (English
158 prose has only 1-2 bits of entropy per character, and provides very bad
159 passphrases), and contain a mix of upper and lowercase letters,
160 numbers, and non-alphanumeric characters.
161 The passphrase can be changed later by using the
165 There is no way to recover a lost passphrase.
167 lost or forgotten, a new key must be generated and copied to the
168 corresponding public key to other machines.
171 there is also a comment field in the key file that is only for
172 convenience to the user to help identify the key.
173 The comment can tell what the key is for, or whatever is useful.
174 The comment is initialized to
176 when the key is created, but can be changed using the
180 After a key is generated, instructions below detail where the keys
181 should be placed to be activated.
183 The options are as follows:
186 Specifies the number of primality tests to perform when screening DH-GEX
191 Show the bubblebabble digest of specified private or public key file.
193 Specifies the number of bits in the key to create.
194 For RSA keys, the minimum size is 768 bits and the default is 2048 bits.
195 Generally, 2048 bits is considered sufficient.
196 DSA keys must be exactly 1024 bits as specified by FIPS 186-2.
198 Provides a new comment.
200 Requests changing the comment in the private and public key files.
201 This operation is only supported for RSA1 keys.
202 The program will prompt for the file containing the private keys, for
203 the passphrase if the key has one, and for the new comment.
205 Download the RSA public key stored in the smartcard in
208 This option will read a private or public OpenSSH key file and
210 RFC 4716 SSH Public Key File Format
212 This option allows exporting keys for use by several commercial
215 Search for the specified
219 file, listing any occurrences found.
220 This option is useful to find hashed host names or addresses and may also be
221 used in conjunction with the
223 option to print found keys in a hashed format.
225 Specifies the filename of the key file.
226 .It Fl G Ar output_file
227 Generate candidate primes for DH-GEX.
228 These primes must be screened for
233 Use generic DNS format when printing fingerprint resource records using the
240 This replaces all hostnames and addresses with hashed representations
241 within the specified file; the original content is moved to a file with
243 These hashes may be used normally by
247 but they do not reveal identifying information should the file's contents
249 This option will not modify existing hashed hostnames and is therefore safe
250 to use on files that mix hashed and non-hashed names.
252 This option will read an unencrypted private (or public) key file
253 in SSH2-compatible format and print an OpenSSH compatible private
254 (or public) key to stdout.
257 RFC 4716 SSH Public Key File Format.
258 This option allows importing keys from several commercial
261 Show fingerprint of specified public key file.
262 Private RSA1 keys are also supported.
265 tries to find the matching public key file and prints its fingerprint.
268 an ASCII art representation of the key is supplied with the fingerprint.
270 Specify the amount of memory to use (in megabytes) when generating
271 candidate moduli for DH-GEX.
272 .It Fl N Ar new_passphrase
273 Provides the new passphrase.
274 .It Fl P Ar passphrase
275 Provides the (old) passphrase.
277 Requests changing the passphrase of a private key file instead of
278 creating a new private key.
279 The program will prompt for the file
280 containing the private key, for the old passphrase, and twice for the
287 when creating a new key.
289 Removes all keys belonging to
294 This option is useful to delete hashed hosts (see the
298 Print the SSHFP fingerprint resource record named
300 for the specified public key file.
302 Specify start point (in hex) when generating candidate moduli for DH-GEX.
303 .It Fl T Ar output_file
304 Test DH group exchange candidate primes (generated using the
308 Specifies the type of key to create.
309 The possible values are
311 for protocol version 1 and
315 for protocol version 2.
317 Upload an existing RSA private key into the smartcard in
323 to print debugging messages about its progress.
324 This is helpful for debugging moduli generation.
327 options increase the verbosity.
329 .It Fl W Ar generator
330 Specify desired generator when testing candidate moduli for DH-GEX.
332 This option will read a private
333 OpenSSH format file and print an OpenSSH public key to stdout.
335 .Sh MODULI GENERATION
337 may be used to generate groups for the Diffie-Hellman Group Exchange
339 Generating these groups is a two-step process: first, candidate
340 primes are generated using a fast, but memory intensive process.
341 These candidate primes are then tested for suitability (a CPU-intensive
344 Generation of primes is performed using the
347 The desired length of the primes may be specified by the
352 .Dl # ssh-keygen -G moduli-2048.candidates -b 2048
354 By default, the search for primes begins at a random point in the
355 desired length range.
356 This may be overridden using the
358 option, which specifies a different start point (in hex).
360 Once a set of candidates have been generated, they must be tested for
362 This may be performed using the
367 will read candidates from standard input (or a file specified using the
372 .Dl # ssh-keygen -T moduli-2048 -f moduli-2048.candidates
374 By default, each candidate will be subjected to 100 primality tests.
375 This may be overridden using the
378 The DH generator value will be chosen automatically for the
379 prime under consideration.
380 If a specific generator is desired, it may be requested using the
383 Valid generator values are 2, 3, and 5.
385 Screened DH groups may be installed in
387 It is important that this file contains moduli of a range of bit lengths and
388 that both ends of a connection share common moduli.
391 .It Pa ~/.ssh/identity
392 Contains the protocol version 1 RSA authentication identity of the user.
393 This file should not be readable by anyone but the user.
395 specify a passphrase when generating the key; that passphrase will be
396 used to encrypt the private part of this file using 3DES.
397 This file is not automatically accessed by
399 but it is offered as the default file for the private key.
401 will read this file when a login attempt is made.
402 .It Pa ~/.ssh/identity.pub
403 Contains the protocol version 1 RSA public key for authentication.
404 The contents of this file should be added to
405 .Pa ~/.ssh/authorized_keys
407 where the user wishes to log in using RSA authentication.
408 There is no need to keep the contents of this file secret.
410 Contains the protocol version 2 DSA authentication identity of the user.
411 This file should not be readable by anyone but the user.
413 specify a passphrase when generating the key; that passphrase will be
414 used to encrypt the private part of this file using 3DES.
415 This file is not automatically accessed by
417 but it is offered as the default file for the private key.
419 will read this file when a login attempt is made.
420 .It Pa ~/.ssh/id_dsa.pub
421 Contains the protocol version 2 DSA public key for authentication.
422 The contents of this file should be added to
423 .Pa ~/.ssh/authorized_keys
425 where the user wishes to log in using public key authentication.
426 There is no need to keep the contents of this file secret.
428 Contains the protocol version 2 RSA authentication identity of the user.
429 This file should not be readable by anyone but the user.
431 specify a passphrase when generating the key; that passphrase will be
432 used to encrypt the private part of this file using 3DES.
433 This file is not automatically accessed by
435 but it is offered as the default file for the private key.
437 will read this file when a login attempt is made.
438 .It Pa ~/.ssh/id_rsa.pub
439 Contains the protocol version 2 RSA public key for authentication.
440 The contents of this file should be added to
441 .Pa ~/.ssh/authorized_keys
443 where the user wishes to log in using public key authentication.
444 There is no need to keep the contents of this file secret.
446 Contains Diffie-Hellman groups used for DH-GEX.
447 The file format is described in
458 .%T "The Secure Shell (SSH) Public Key File Format"
462 OpenSSH is a derivative of the original and free
463 ssh 1.2.12 release by Tatu Ylonen.
464 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
465 Theo de Raadt and Dug Song
466 removed many bugs, re-added newer features and
468 Markus Friedl contributed the support for SSH
469 protocol versions 1.5 and 2.0.