1 .\" $OpenBSD: ssh-keygen.1,v 1.100 2010/09/10 15:19:29 naddy 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: September 10 2010 $
45 .Nd authentication key generation, management and conversion
52 .Op Fl N Ar new_passphrase
54 .Op Fl f Ar output_keyfile
57 .Op Fl P Ar old_passphrase
58 .Op Fl N Ar new_passphrase
62 .Op Fl m Ar key_format
63 .Op Fl f Ar input_keyfile
66 .Op Fl m Ar key_format
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
103 .Op Fl S Ar start_point
108 .Op Fl a Ar num_trials
109 .Op Fl W Ar generator
112 .Fl I Ar certificate_identity
114 .Op Fl n Ar principals
116 .Op Fl V Ar validity_interval
117 .Op Fl z Ar serial_number
121 .Op Fl f Ar input_keyfile
125 generates, manages and converts authentication keys for
128 can create RSA keys for use by SSH protocol version 1 and DSA, ECDSA or RSA
129 keys for use by SSH protocol version 2.
130 The type of key to be generated is specified with the
133 If invoked without any arguments,
135 will generate an RSA key for use in SSH protocol 2 connections.
138 is also used to generate groups for use in Diffie-Hellman group
141 .Sx MODULI GENERATION
144 Normally each user wishing to use SSH
145 with public key authentication runs this once to create the authentication
147 .Pa ~/.ssh/identity ,
148 .Pa ~/.ssh/id_ecdsa ,
152 Additionally, the system administrator may use this to generate host keys,
156 Normally this program generates the key and asks for a file in which
157 to store the private key.
158 The public key is stored in a file with the same name but
161 The program also asks for a passphrase.
162 The passphrase may be empty to indicate no passphrase
163 (host keys must have an empty passphrase), or it may be a string of
165 A passphrase is similar to a password, except it can be a phrase with a
166 series of words, punctuation, numbers, whitespace, or any string of
168 Good passphrases are 10-30 characters long, are
169 not simple sentences or otherwise easily guessable (English
170 prose has only 1-2 bits of entropy per character, and provides very bad
171 passphrases), and contain a mix of upper and lowercase letters,
172 numbers, and non-alphanumeric characters.
173 The passphrase can be changed later by using the
177 There is no way to recover a lost passphrase.
179 lost or forgotten, a new key must be generated and copied to the
180 corresponding public key to other machines.
183 there is also a comment field in the key file that is only for
184 convenience to the user to help identify the key.
185 The comment can tell what the key is for, or whatever is useful.
186 The comment is initialized to
188 when the key is created, but can be changed using the
192 After a key is generated, instructions below detail where the keys
193 should be placed to be activated.
195 The options are as follows:
198 Specifies the number of primality tests to perform when screening DH-GEX
203 Show the bubblebabble digest of specified private or public key file.
205 Specifies the number of bits in the key to create.
206 For RSA keys, the minimum size is 768 bits and the default is 2048 bits.
207 Generally, 2048 bits is considered sufficient.
208 DSA keys must be exactly 1024 bits as specified by FIPS 186-2.
210 Provides a new comment.
212 Requests changing the comment in the private and public key files.
213 This operation is only supported for RSA1 keys.
214 The program will prompt for the file containing the private keys, for
215 the passphrase if the key has one, and for the new comment.
217 Download the RSA public keys provided by the PKCS#11 shared library
219 When used in combination with
221 this option indicates that a CA key resides in a PKCS#11 token (see the
223 section for details).
225 This option will read a private or public OpenSSH key file and
226 print to stdout the key in one of the formats specified by the
229 The default export format is
231 This option allows exporting OpenSSH keys for use by other programs, including
232 several commercial SSH implementations.
234 Search for the specified
238 file, listing any occurrences found.
239 This option is useful to find hashed host names or addresses and may also be
240 used in conjunction with the
242 option to print found keys in a hashed format.
244 Specifies the filename of the key file.
245 .It Fl G Ar output_file
246 Generate candidate primes for DH-GEX.
247 These primes must be screened for
252 Use generic DNS format when printing fingerprint resource records using the
259 This replaces all hostnames and addresses with hashed representations
260 within the specified file; the original content is moved to a file with
262 These hashes may be used normally by
266 but they do not reveal identifying information should the file's contents
268 This option will not modify existing hashed hostnames and is therefore safe
269 to use on files that mix hashed and non-hashed names.
271 When signing a key, create a host certificate instead of a user
276 .It Fl I Ar certificate_identity
277 Specify the key identity when signing a public key.
282 This option will read an unencrypted private (or public) key file
283 in the format specified by the
285 option and print an OpenSSH compatible private
286 (or public) key to stdout.
287 This option allows importing keys from other software, including several
288 commercial SSH implementations.
289 The default import format is
292 Prints the contents of a certificate.
294 Show fingerprint of specified public key file.
295 Private RSA1 keys are also supported.
298 tries to find the matching public key file and prints its fingerprint.
301 an ASCII art representation of the key is supplied with the fingerprint.
303 Specify the amount of memory to use (in megabytes) when generating
304 candidate moduli for DH-GEX.
305 .It Fl m Ar key_format
306 Specify a key format for the
310 (export) conversion options.
311 The supported key formats are:
313 (RFC 4716/SSH2 public or private key),
315 (PEM PKCS8 public key)
319 The default conversion format is
321 .It Fl N Ar new_passphrase
322 Provides the new passphrase.
323 .It Fl n Ar principals
324 Specify one or more principals (user or host names) to be included in
325 a certificate when signing a key.
326 Multiple principals may be specified, separated by commas.
331 Specify a certificate option when signing a key.
332 This option may be specified multiple times.
336 The options that are valid for user certificates are:
339 Clear all enabled permissions.
340 This is useful for clearing the default set of permissions so permissions may
341 be added individually.
342 .It Ic force-command Ns = Ns Ar command
343 Forces the execution of
345 instead of any shell or command specified by the user when
346 the certificate is used for authentication.
347 .It Ic no-agent-forwarding
350 forwarding (permitted by default).
351 .It Ic no-port-forwarding
352 Disable port forwarding (permitted by default).
354 Disable PTY allocation (permitted by default).
360 (permitted by default).
361 .It Ic no-x11-forwarding
362 Disable X11 forwarding (permitted by default).
363 .It Ic permit-agent-forwarding
367 .It Ic permit-port-forwarding
368 Allows port forwarding.
370 Allows PTY allocation.
371 .It Ic permit-user-rc
376 .It Ic permit-x11-forwarding
377 Allows X11 forwarding.
378 .It Ic source-address Ns = Ns Ar address_list
379 Restrict the source addresses from which the certificate is considered valid.
382 is a comma-separated list of one or more address/netmask pairs in CIDR
386 At present, no options are valid for host keys.
387 .It Fl P Ar passphrase
388 Provides the (old) passphrase.
390 Requests changing the passphrase of a private key file instead of
391 creating a new private key.
392 The program will prompt for the file
393 containing the private key, for the old passphrase, and twice for the
400 when creating a new key.
402 Removes all keys belonging to
407 This option is useful to delete hashed hosts (see the
411 Print the SSHFP fingerprint resource record named
413 for the specified public key file.
415 Specify start point (in hex) when generating candidate moduli for DH-GEX.
417 Certify (sign) a public key using the specified CA key.
421 .It Fl T Ar output_file
422 Test DH group exchange candidate primes (generated using the
426 Specifies the type of key to create.
427 The possible values are
429 for protocol version 1 and
434 for protocol version 2.
435 .It Fl V Ar validity_interval
436 Specify a validity interval when signing a certificate.
437 A validity interval may consist of a single time, indicating that the
438 certificate is valid beginning now and expiring at that time, or may consist
439 of two times separated by a colon to indicate an explicit time interval.
440 The start time may be specified as a date in YYYYMMDD format, a time
441 in YYYYMMDDHHMMSS format or a relative time (to the current time) consisting
442 of a minus sign followed by a relative time in the format described in the
446 The end time may be specified as a YYYYMMDD date, a YYYYMMDDHHMMSS time or
447 a relative time starting with a plus character.
451 (valid from now to 52 weeks and one day from now),
453 (valid from four weeks ago to four weeks from now),
454 .Dq 20100101123000:20110101123000
455 (valid from 12:30 PM, January 1st, 2010 to 12:30 PM, January 1st, 2011),
457 (valid from yesterday to midnight, January 1st, 2011).
462 to print debugging messages about its progress.
463 This is helpful for debugging moduli generation.
466 options increase the verbosity.
468 .It Fl W Ar generator
469 Specify desired generator when testing candidate moduli for DH-GEX.
471 This option will read a private
472 OpenSSH format file and print an OpenSSH public key to stdout.
473 .It Fl z Ar serial_number
474 Specifies a serial number to be embedded in the certificate to distinguish
475 this certificate from others from the same CA.
476 The default serial number is zero.
478 .Sh MODULI GENERATION
480 may be used to generate groups for the Diffie-Hellman Group Exchange
482 Generating these groups is a two-step process: first, candidate
483 primes are generated using a fast, but memory intensive process.
484 These candidate primes are then tested for suitability (a CPU-intensive
487 Generation of primes is performed using the
490 The desired length of the primes may be specified by the
495 .Dl # ssh-keygen -G moduli-2048.candidates -b 2048
497 By default, the search for primes begins at a random point in the
498 desired length range.
499 This may be overridden using the
501 option, which specifies a different start point (in hex).
503 Once a set of candidates have been generated, they must be tested for
505 This may be performed using the
510 will read candidates from standard input (or a file specified using the
515 .Dl # ssh-keygen -T moduli-2048 -f moduli-2048.candidates
517 By default, each candidate will be subjected to 100 primality tests.
518 This may be overridden using the
521 The DH generator value will be chosen automatically for the
522 prime under consideration.
523 If a specific generator is desired, it may be requested using the
526 Valid generator values are 2, 3, and 5.
528 Screened DH groups may be installed in
530 It is important that this file contains moduli of a range of bit lengths and
531 that both ends of a connection share common moduli.
534 supports signing of keys to produce certificates that may be used for
535 user or host authentication.
536 Certificates consist of a public key, some identity information, zero or
537 more principal (user or host) names and a set of options that
538 are signed by a Certification Authority (CA) key.
539 Clients or servers may then trust only the CA key and verify its signature
540 on a certificate rather than trusting many user/host keys.
541 Note that OpenSSH certificates are a different, and much simpler, format to
542 the X.509 certificates used in
546 supports two types of certificates: user and host.
547 User certificates authenticate users to servers, whereas host certificates
548 authenticate server hosts to users.
549 To generate a user certificate:
551 .Dl $ ssh-keygen -s /path/to/ca_key -I key_id /path/to/user_key.pub
553 The resultant certificate will be placed in
554 .Pa /path/to/user_key-cert.pub .
555 A host certificate requires the
559 .Dl $ ssh-keygen -s /path/to/ca_key -I key_id -h /path/to/host_key.pub
561 The host certificate will be output to
562 .Pa /path/to/host_key-cert.pub .
564 It is possible to sign using a CA key stored in a PKCS#11 token by
565 providing the token library using
567 and identifying the CA key by providing its public half as an argument
571 .Dl $ ssh-keygen -s ca_key.pub -D libpkcs11.so -I key_id host_key.pub
575 is a "key identifier" that is logged by the server when the certificate
576 is used for authentication.
578 Certificates may be limited to be valid for a set of principal (user/host)
580 By default, generated certificates are valid for all users or hosts.
581 To generate a certificate for a specified set of principals:
583 .Dl $ ssh-keygen -s ca_key -I key_id -n user1,user2 user_key.pub
584 .Dl "$ ssh-keygen -s ca_key -I key_id -h -n host.domain user_key.pub"
586 Additional limitations on the validity and use of user certificates may
587 be specified through certificate options.
588 A certificate option may disable features of the SSH session, may be
589 valid only when presented from particular source addresses or may
590 force the use of a specific command.
591 For a list of valid certificate options, see the documentation for the
595 Finally, certificates may be defined with a validity lifetime.
598 option allows specification of certificate start and end times.
599 A certificate that is presented at a time outside this range will not be
601 By default, certificates have a maximum validity interval.
603 For certificates to be used for user or host authentication, the CA
604 public key must be trusted by
608 Please refer to those manual pages for details.
610 .Bl -tag -width Ds -compact
611 .It Pa ~/.ssh/identity
612 Contains the protocol version 1 RSA authentication identity of the user.
613 This file should not be readable by anyone but the user.
615 specify a passphrase when generating the key; that passphrase will be
616 used to encrypt the private part of this file using 3DES.
617 This file is not automatically accessed by
619 but it is offered as the default file for the private key.
621 will read this file when a login attempt is made.
623 .It Pa ~/.ssh/identity.pub
624 Contains the protocol version 1 RSA public key for authentication.
625 The contents of this file should be added to
626 .Pa ~/.ssh/authorized_keys
628 where the user wishes to log in using RSA authentication.
629 There is no need to keep the contents of this file secret.
632 .It Pa ~/.ssh/id_ecdsa
634 Contains the protocol version 2 DSA, ECDSA or RSA authentication identity of the user.
635 This file should not be readable by anyone but the user.
637 specify a passphrase when generating the key; that passphrase will be
638 used to encrypt the private part of this file using 128-bit AES.
639 This file is not automatically accessed by
641 but it is offered as the default file for the private key.
643 will read this file when a login attempt is made.
645 .It Pa ~/.ssh/id_dsa.pub
646 .It Pa ~/.ssh/id_ecdsa.pub
647 .It Pa ~/.ssh/id_rsa.pub
648 Contains the protocol version 2 DSA, ECDSA or RSA public key for authentication.
649 The contents of this file should be added to
650 .Pa ~/.ssh/authorized_keys
652 where the user wishes to log in using public key authentication.
653 There is no need to keep the contents of this file secret.
656 Contains Diffie-Hellman groups used for DH-GEX.
657 The file format is described in
668 .%T "The Secure Shell (SSH) Public Key File Format"
672 OpenSSH is a derivative of the original and free
673 ssh 1.2.12 release by Tatu Ylonen.
674 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
675 Theo de Raadt and Dug Song
676 removed many bugs, re-added newer features and
678 Markus Friedl contributed the support for SSH
679 protocol versions 1.5 and 2.0.