2 .\" $OpenBSD: ssh-keygen.1,v 1.79 2008/07/24 23:55:30 sthen Exp $
6 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
7 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
8 .\" All rights reserved
10 .\" As far as I am concerned, the code I have written for this software
11 .\" can be used freely for any purpose. Any derived versions of this
12 .\" software must be clearly marked as such, and if the derived work is
13 .\" incompatible with the protocol description in the RFC file, it must be
14 .\" called by a name other than "ssh" or "Secure Shell".
17 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
18 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
19 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
21 .\" Redistribution and use in source and binary forms, with or without
22 .\" modification, are permitted provided that the following conditions
24 .\" 1. Redistributions of source code must retain the above copyright
25 .\" notice, this list of conditions and the following disclaimer.
26 .\" 2. Redistributions in binary form must reproduce the above copyright
27 .\" notice, this list of conditions and the following disclaimer in the
28 .\" documentation and/or other materials provided with the distribution.
30 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
31 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
32 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
33 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
34 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
35 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
36 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
37 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
38 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
39 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
46 .Nd authentication key generation, management and conversion
53 .Op Fl N Ar new_passphrase
55 .Op Fl f Ar output_keyfile
59 .Op Fl P Ar old_passphrase
60 .Op Fl N Ar new_passphrase
64 .Op Fl f Ar input_keyfile
67 .Op Fl f Ar input_keyfile
70 .Op Fl f Ar input_keyfile
73 .Op Fl P Ar passphrase
78 .Op Fl f Ar input_keyfile
81 .Op Fl f Ar input_keyfile
86 .Op Fl f Ar known_hosts_file
90 .Op Fl f Ar known_hosts_file
93 .Op Fl f Ar known_hosts_file
96 .Op Fl f Ar input_keyfile
99 .Op Fl f Ar input_keyfile
106 .Op Fl S Ar start_point
111 .Op Fl a Ar num_trials
112 .Op Fl W Ar generator
115 generates, manages and converts authentication keys for
118 can create RSA keys for use by SSH protocol version 1 and RSA or DSA
119 keys for use by SSH protocol version 2.
120 The type of key to be generated is specified with the
123 If invoked without any arguments,
125 will generate an RSA key for use in SSH protocol 2 connections.
128 is also used to generate groups for use in Diffie-Hellman group
131 .Sx MODULI GENERATION
134 Normally each user wishing to use SSH
135 with RSA or DSA authentication runs this once to create the authentication
137 .Pa ~/.ssh/identity ,
141 Additionally, the system administrator may use this to generate host keys,
145 Normally this program generates the key and asks for a file in which
146 to store the private key.
147 The public key is stored in a file with the same name but
150 The program also asks for a passphrase.
151 The passphrase may be empty to indicate no passphrase
152 (host keys must have an empty passphrase), or it may be a string of
154 A passphrase is similar to a password, except it can be a phrase with a
155 series of words, punctuation, numbers, whitespace, or any string of
157 Good passphrases are 10-30 characters long, are
158 not simple sentences or otherwise easily guessable (English
159 prose has only 1-2 bits of entropy per character, and provides very bad
160 passphrases), and contain a mix of upper and lowercase letters,
161 numbers, and non-alphanumeric characters.
162 The passphrase can be changed later by using the
166 There is no way to recover a lost passphrase.
168 lost or forgotten, a new key must be generated and copied to the
169 corresponding public key to other machines.
172 there is also a comment field in the key file that is only for
173 convenience to the user to help identify the key.
174 The comment can tell what the key is for, or whatever is useful.
175 The comment is initialized to
177 when the key is created, but can be changed using the
181 After a key is generated, instructions below detail where the keys
182 should be placed to be activated.
184 The options are as follows:
187 Specifies the number of primality tests to perform when screening DH-GEX
192 Show the bubblebabble digest of specified private or public key file.
194 Specifies the number of bits in the key to create.
195 For RSA keys, the minimum size is 768 bits and the default is 2048 bits.
196 Generally, 2048 bits is considered sufficient.
197 DSA keys must be exactly 1024 bits as specified by FIPS 186-2.
199 Provides a new comment.
201 Requests changing the comment in the private and public key files.
202 This operation is only supported for RSA1 keys.
203 The program will prompt for the file containing the private keys, for
204 the passphrase if the key has one, and for the new comment.
206 Download the RSA public key stored in the smartcard in
209 This option will read a private or public OpenSSH key file and
211 RFC 4716 SSH Public Key File Format
213 This option allows exporting keys for use by several commercial
216 Search for the specified
220 file, listing any occurrences found.
221 This option is useful to find hashed host names or addresses and may also be
222 used in conjunction with the
224 option to print found keys in a hashed format.
226 Specifies the filename of the key file.
227 .It Fl G Ar output_file
228 Generate candidate primes for DH-GEX.
229 These primes must be screened for
234 Use generic DNS format when printing fingerprint resource records using the
241 This replaces all hostnames and addresses with hashed representations
242 within the specified file; the original content is moved to a file with
244 These hashes may be used normally by
248 but they do not reveal identifying information should the file's contents
250 This option will not modify existing hashed hostnames and is therefore safe
251 to use on files that mix hashed and non-hashed names.
253 This option will read an unencrypted private (or public) key file
254 in SSH2-compatible format and print an OpenSSH compatible private
255 (or public) key to stdout.
258 RFC 4716 SSH Public Key File Format.
259 This option allows importing keys from several commercial
262 Show fingerprint of specified public key file.
263 Private RSA1 keys are also supported.
266 tries to find the matching public key file and prints its fingerprint.
269 an ASCII art representation of the key is supplied with the fingerprint.
271 Specify the amount of memory to use (in megabytes) when generating
272 candidate moduli for DH-GEX.
273 .It Fl N Ar new_passphrase
274 Provides the new passphrase.
275 .It Fl P Ar passphrase
276 Provides the (old) passphrase.
278 Requests changing the passphrase of a private key file instead of
279 creating a new private key.
280 The program will prompt for the file
281 containing the private key, for the old passphrase, and twice for the
288 when creating a new key.
290 Removes all keys belonging to
295 This option is useful to delete hashed hosts (see the
299 Print the SSHFP fingerprint resource record named
301 for the specified public key file.
303 Specify start point (in hex) when generating candidate moduli for DH-GEX.
304 .It Fl T Ar output_file
305 Test DH group exchange candidate primes (generated using the
309 Specifies the type of key to create.
310 The possible values are
312 for protocol version 1 and
316 for protocol version 2.
318 Upload an existing RSA private key into the smartcard in
324 to print debugging messages about its progress.
325 This is helpful for debugging moduli generation.
328 options increase the verbosity.
330 .It Fl W Ar generator
331 Specify desired generator when testing candidate moduli for DH-GEX.
333 This option will read a private
334 OpenSSH format file and print an OpenSSH public key to stdout.
336 .Sh MODULI GENERATION
338 may be used to generate groups for the Diffie-Hellman Group Exchange
340 Generating these groups is a two-step process: first, candidate
341 primes are generated using a fast, but memory intensive process.
342 These candidate primes are then tested for suitability (a CPU-intensive
345 Generation of primes is performed using the
348 The desired length of the primes may be specified by the
353 .Dl # ssh-keygen -G moduli-2048.candidates -b 2048
355 By default, the search for primes begins at a random point in the
356 desired length range.
357 This may be overridden using the
359 option, which specifies a different start point (in hex).
361 Once a set of candidates have been generated, they must be tested for
363 This may be performed using the
368 will read candidates from standard input (or a file specified using the
373 .Dl # ssh-keygen -T moduli-2048 -f moduli-2048.candidates
375 By default, each candidate will be subjected to 100 primality tests.
376 This may be overridden using the
379 The DH generator value will be chosen automatically for the
380 prime under consideration.
381 If a specific generator is desired, it may be requested using the
384 Valid generator values are 2, 3, and 5.
386 Screened DH groups may be installed in
388 It is important that this file contains moduli of a range of bit lengths and
389 that both ends of a connection share common moduli.
392 .It Pa ~/.ssh/identity
393 Contains the protocol version 1 RSA authentication identity of the user.
394 This file should not be readable by anyone but the user.
396 specify a passphrase when generating the key; that passphrase will be
397 used to encrypt the private part of this file using 3DES.
398 This file is not automatically accessed by
400 but it is offered as the default file for the private key.
402 will read this file when a login attempt is made.
403 .It Pa ~/.ssh/identity.pub
404 Contains the protocol version 1 RSA public key for authentication.
405 The contents of this file should be added to
406 .Pa ~/.ssh/authorized_keys
408 where the user wishes to log in using RSA authentication.
409 There is no need to keep the contents of this file secret.
411 Contains the protocol version 2 DSA authentication identity of the user.
412 This file should not be readable by anyone but the user.
414 specify a passphrase when generating the key; that passphrase will be
415 used to encrypt the private part of this file using 3DES.
416 This file is not automatically accessed by
418 but it is offered as the default file for the private key.
420 will read this file when a login attempt is made.
421 .It Pa ~/.ssh/id_dsa.pub
422 Contains the protocol version 2 DSA public key for authentication.
423 The contents of this file should be added to
424 .Pa ~/.ssh/authorized_keys
426 where the user wishes to log in using public key authentication.
427 There is no need to keep the contents of this file secret.
429 Contains the protocol version 2 RSA authentication identity of the user.
430 This file should not be readable by anyone but the user.
432 specify a passphrase when generating the key; that passphrase will be
433 used to encrypt the private part of this file using 3DES.
434 This file is not automatically accessed by
436 but it is offered as the default file for the private key.
438 will read this file when a login attempt is made.
439 .It Pa ~/.ssh/id_rsa.pub
440 Contains the protocol version 2 RSA public key for authentication.
441 The contents of this file should be added to
442 .Pa ~/.ssh/authorized_keys
444 where the user wishes to log in using public key authentication.
445 There is no need to keep the contents of this file secret.
447 Contains Diffie-Hellman groups used for DH-GEX.
448 The file format is described in
459 .%T "The Secure Shell (SSH) Public Key File Format"
463 OpenSSH is a derivative of the original and free
464 ssh 1.2.12 release by Tatu Ylonen.
465 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
466 Theo de Raadt and Dug Song
467 removed many bugs, re-added newer features and
469 Markus Friedl contributed the support for SSH
470 protocol versions 1.5 and 2.0.