Annotation of src/usr.bin/ssh/ssh-keygen.1, Revision 1.225
1.225 ! jmc 1: .\" $OpenBSD: ssh-keygen.1,v 1.224 2022/08/11 01:56:51 djm Exp $
1.1 deraadt 2: .\"
3: .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4: .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5: .\" All rights reserved
6: .\"
1.22 deraadt 7: .\" As far as I am concerned, the code I have written for this software
8: .\" can be used freely for any purpose. Any derived versions of this
9: .\" software must be clearly marked as such, and if the derived work is
10: .\" incompatible with the protocol description in the RFC file, it must be
11: .\" called by a name other than "ssh" or "Secure Shell".
12: .\"
13: .\"
1.33 deraadt 14: .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
15: .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
16: .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
1.22 deraadt 17: .\"
18: .\" Redistribution and use in source and binary forms, with or without
19: .\" modification, are permitted provided that the following conditions
20: .\" are met:
21: .\" 1. Redistributions of source code must retain the above copyright
22: .\" notice, this list of conditions and the following disclaimer.
23: .\" 2. Redistributions in binary form must reproduce the above copyright
24: .\" notice, this list of conditions and the following disclaimer in the
25: .\" documentation and/or other materials provided with the distribution.
1.1 deraadt 26: .\"
1.22 deraadt 27: .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
28: .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
29: .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
30: .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
31: .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
32: .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
33: .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
34: .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
35: .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
36: .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1.1 deraadt 37: .\"
1.225 ! jmc 38: .Dd $Mdocdate: August 11 2022 $
1.2 deraadt 39: .Dt SSH-KEYGEN 1
40: .Os
41: .Sh NAME
42: .Nm ssh-keygen
1.179 jmc 43: .Nd OpenSSH authentication key utility
1.2 deraadt 44: .Sh SYNOPSIS
45: .Nm ssh-keygen
1.25 markus 46: .Op Fl q
1.205 solene 47: .Op Fl a Ar rounds
1.2 deraadt 48: .Op Fl b Ar bits
49: .Op Fl C Ar comment
1.20 markus 50: .Op Fl f Ar output_keyfile
1.155 djm 51: .Op Fl m Ar format
1.171 jmc 52: .Op Fl N Ar new_passphrase
1.191 naddy 53: .Op Fl O Ar option
1.205 solene 54: .Op Fl t Cm dsa | ecdsa | ecdsa-sk | ed25519 | ed25519-sk | rsa
1.173 naddy 55: .Op Fl w Ar provider
1.212 dtucker 56: .Op Fl Z Ar cipher
1.2 deraadt 57: .Nm ssh-keygen
58: .Fl p
1.205 solene 59: .Op Fl a Ar rounds
1.9 markus 60: .Op Fl f Ar keyfile
1.155 djm 61: .Op Fl m Ar format
1.171 jmc 62: .Op Fl N Ar new_passphrase
63: .Op Fl P Ar old_passphrase
1.212 dtucker 64: .Op Fl Z Ar cipher
1.2 deraadt 65: .Nm ssh-keygen
1.37 markus 66: .Fl i
1.171 jmc 67: .Op Fl f Ar input_keyfile
1.95 djm 68: .Op Fl m Ar key_format
1.16 deraadt 69: .Nm ssh-keygen
1.37 markus 70: .Fl e
1.171 jmc 71: .Op Fl f Ar input_keyfile
1.95 djm 72: .Op Fl m Ar key_format
1.16 deraadt 73: .Nm ssh-keygen
1.17 markus 74: .Fl y
1.20 markus 75: .Op Fl f Ar input_keyfile
1.17 markus 76: .Nm ssh-keygen
1.2 deraadt 77: .Fl c
1.205 solene 78: .Op Fl a Ar rounds
1.2 deraadt 79: .Op Fl C Ar comment
1.9 markus 80: .Op Fl f Ar keyfile
1.171 jmc 81: .Op Fl P Ar passphrase
1.9 markus 82: .Nm ssh-keygen
83: .Fl l
1.125 naddy 84: .Op Fl v
1.124 djm 85: .Op Fl E Ar fingerprint_hash
1.35 markus 86: .Op Fl f Ar input_keyfile
87: .Nm ssh-keygen
88: .Fl B
1.20 markus 89: .Op Fl f Ar input_keyfile
1.48 jakob 90: .Nm ssh-keygen
1.82 jmc 91: .Fl D Ar pkcs11
1.48 jakob 92: .Nm ssh-keygen
1.64 djm 93: .Fl F Ar hostname
1.170 jmc 94: .Op Fl lv
1.64 djm 95: .Op Fl f Ar known_hosts_file
96: .Nm ssh-keygen
97: .Fl H
98: .Op Fl f Ar known_hosts_file
99: .Nm ssh-keygen
1.187 djm 100: .Fl K
1.205 solene 101: .Op Fl a Ar rounds
1.187 djm 102: .Op Fl w Ar provider
103: .Nm ssh-keygen
1.64 djm 104: .Fl R Ar hostname
105: .Op Fl f Ar known_hosts_file
1.57 jakob 106: .Nm ssh-keygen
107: .Fl r Ar hostname
1.170 jmc 108: .Op Fl g
1.57 jakob 109: .Op Fl f Ar input_keyfile
1.60 djm 110: .Nm ssh-keygen
1.184 djm 111: .Fl M Cm generate
112: .Op Fl O Ar option
1.191 naddy 113: .Ar output_file
1.60 djm 114: .Nm ssh-keygen
1.184 djm 115: .Fl M Cm screen
1.191 naddy 116: .Op Fl f Ar input_file
1.184 djm 117: .Op Fl O Ar option
1.191 naddy 118: .Ar output_file
1.84 djm 119: .Nm ssh-keygen
1.171 jmc 120: .Fl I Ar certificate_identity
1.84 djm 121: .Fl s Ar ca_key
1.170 jmc 122: .Op Fl hU
1.142 djm 123: .Op Fl D Ar pkcs11_provider
1.84 djm 124: .Op Fl n Ar principals
1.93 djm 125: .Op Fl O Ar option
1.84 djm 126: .Op Fl V Ar validity_interval
1.93 djm 127: .Op Fl z Ar serial_number
1.84 djm 128: .Ar
1.86 djm 129: .Nm ssh-keygen
130: .Fl L
131: .Op Fl f Ar input_keyfile
1.102 stevesk 132: .Nm ssh-keygen
133: .Fl A
1.205 solene 134: .Op Fl a Ar rounds
1.143 djm 135: .Op Fl f Ar prefix_path
1.111 djm 136: .Nm ssh-keygen
137: .Fl k
138: .Fl f Ar krl_file
139: .Op Fl u
1.112 jmc 140: .Op Fl s Ar ca_public
141: .Op Fl z Ar version_number
1.111 djm 142: .Ar
143: .Nm ssh-keygen
144: .Fl Q
1.203 djm 145: .Op Fl l
1.111 djm 146: .Fl f Ar krl_file
147: .Ar
1.163 djm 148: .Nm ssh-keygen
1.196 djm 149: .Fl Y Cm find-principals
1.214 djm 150: .Op Fl O Ar option
1.194 djm 151: .Fl s Ar signature_file
152: .Fl f Ar allowed_signers_file
153: .Nm ssh-keygen
1.217 djm 154: .Fl Y Cm match-principals
155: .Fl I Ar signer_identity
156: .Fl f Ar allowed_signers_file
157: .Nm ssh-keygen
1.171 jmc 158: .Fl Y Cm check-novalidate
1.214 djm 159: .Op Fl O Ar option
1.171 jmc 160: .Fl n Ar namespace
161: .Fl s Ar signature_file
162: .Nm ssh-keygen
1.163 djm 163: .Fl Y Cm sign
1.219 djm 164: .Op Fl O Ar option
1.163 djm 165: .Fl f Ar key_file
166: .Fl n Ar namespace
167: .Ar
168: .Nm ssh-keygen
169: .Fl Y Cm verify
1.214 djm 170: .Op Fl O Ar option
1.171 jmc 171: .Fl f Ar allowed_signers_file
1.163 djm 172: .Fl I Ar signer_identity
173: .Fl n Ar namespace
174: .Fl s Ar signature_file
175: .Op Fl r Ar revocation_file
1.13 aaron 176: .Sh DESCRIPTION
1.2 deraadt 177: .Nm
1.37 markus 178: generates, manages and converts authentication keys for
1.2 deraadt 179: .Xr ssh 1 .
1.15 deraadt 180: .Nm
1.140 jmc 181: can create keys for use by SSH protocol version 2.
1.130 jmc 182: .Pp
1.58 jmc 183: The type of key to be generated is specified with the
1.25 markus 184: .Fl t
1.52 djm 185: option.
1.70 djm 186: If invoked without any arguments,
187: .Nm
1.141 naddy 188: will generate an RSA key.
1.15 deraadt 189: .Pp
1.60 djm 190: .Nm
191: is also used to generate groups for use in Diffie-Hellman group
192: exchange (DH-GEX).
193: See the
194: .Sx MODULI GENERATION
195: section for details.
196: .Pp
1.111 djm 197: Finally,
198: .Nm
199: can be used to generate and update Key Revocation Lists, and to test whether
1.112 jmc 200: given keys have been revoked by one.
201: See the
1.111 djm 202: .Sx KEY REVOCATION LISTS
203: section for details.
204: .Pp
1.2 deraadt 205: Normally each user wishing to use SSH
1.99 djm 206: with public key authentication runs this once to create the authentication
1.1 deraadt 207: key in
1.118 naddy 208: .Pa ~/.ssh/id_dsa ,
1.99 djm 209: .Pa ~/.ssh/id_ecdsa ,
1.173 naddy 210: .Pa ~/.ssh/id_ecdsa_sk ,
1.176 naddy 211: .Pa ~/.ssh/id_ed25519 ,
212: .Pa ~/.ssh/id_ed25519_sk
1.15 deraadt 213: or
1.68 djm 214: .Pa ~/.ssh/id_rsa .
1.15 deraadt 215: Additionally, the system administrator may use this to generate host keys,
216: as seen in
217: .Pa /etc/rc .
1.2 deraadt 218: .Pp
1.1 deraadt 219: Normally this program generates the key and asks for a file in which
1.12 aaron 220: to store the private key.
221: The public key is stored in a file with the same name but
1.2 deraadt 222: .Dq .pub
1.12 aaron 223: appended.
224: The program also asks for a passphrase.
225: The passphrase may be empty to indicate no passphrase
1.26 markus 226: (host keys must have an empty passphrase), or it may be a string of
1.12 aaron 227: arbitrary length.
1.51 stevesk 228: A passphrase is similar to a password, except it can be a phrase with a
229: series of words, punctuation, numbers, whitespace, or any string of
230: characters you want.
231: Good passphrases are 10-30 characters long, are
1.1 deraadt 232: not simple sentences or otherwise easily guessable (English
1.42 markus 233: prose has only 1-2 bits of entropy per character, and provides very bad
1.51 stevesk 234: passphrases), and contain a mix of upper and lowercase letters,
235: numbers, and non-alphanumeric characters.
1.12 aaron 236: The passphrase can be changed later by using the
1.2 deraadt 237: .Fl p
1.1 deraadt 238: option.
1.2 deraadt 239: .Pp
1.12 aaron 240: There is no way to recover a lost passphrase.
1.105 djm 241: If the passphrase is lost or forgotten, a new key must be generated
242: and the corresponding public key copied to other machines.
1.2 deraadt 243: .Pp
1.153 djm 244: .Nm
245: will by default write keys in an OpenSSH-specific format.
246: This format is preferred as it offers better protection for
247: keys at rest as well as allowing storage of key comments within
248: the private key file itself.
249: The key comment may be useful to help identify the key.
1.12 aaron 250: The comment is initialized to
1.2 deraadt 251: .Dq user@host
252: when the key is created, but can be changed using the
253: .Fl c
1.1 deraadt 254: option.
1.153 djm 255: .Pp
256: It is still possible for
257: .Nm
258: to write the previously-used PEM format private keys using the
259: .Fl m
260: flag.
261: This may be used when generating new keys, and existing new-format
262: keys may be converted using this option in conjunction with the
263: .Fl p
264: (change passphrase) flag.
1.2 deraadt 265: .Pp
1.205 solene 266: After a key is generated,
267: .Nm
268: will ask where the keys
1.15 deraadt 269: should be placed to be activated.
270: .Pp
1.2 deraadt 271: The options are as follows:
272: .Bl -tag -width Ds
1.102 stevesk 273: .It Fl A
1.223 dtucker 274: Generate host keys of all default key types (rsa, ecdsa, and
275: ed25519) if they do not already exist.
276: The host keys are generated with the default key file path,
1.102 stevesk 277: an empty passphrase, default bits for the key type, and default comment.
1.144 jmc 278: If
1.143 djm 279: .Fl f
1.144 jmc 280: has also been specified, its argument is used as a prefix to the
1.143 djm 281: default path for the resulting host key files.
1.104 jmc 282: This is used by
1.102 stevesk 283: .Pa /etc/rc
284: to generate new host keys.
1.117 djm 285: .It Fl a Ar rounds
1.169 jmc 286: When saving a private key, this option specifies the number of KDF
1.211 dtucker 287: (key derivation function, currently
288: .Xr bcrypt_pbkdf 3 )
289: rounds used.
1.117 djm 290: Higher numbers result in slower passphrase verification and increased
291: resistance to brute-force password cracking (should the keys be stolen).
1.204 dtucker 292: The default is 16 rounds.
1.66 jmc 293: .It Fl B
294: Show the bubblebabble digest of specified private or public key file.
1.2 deraadt 295: .It Fl b Ar bits
1.12 aaron 296: Specifies the number of bits in the key to create.
1.158 dtucker 297: For RSA keys, the minimum size is 1024 bits and the default is 3072 bits.
298: Generally, 3072 bits is considered sufficient.
1.72 dtucker 299: DSA keys must be exactly 1024 bits as specified by FIPS 186-2.
1.106 djm 300: For ECDSA keys, the
301: .Fl b
1.107 deraadt 302: flag determines the key length by selecting from one of three elliptic
1.106 djm 303: curve sizes: 256, 384 or 521 bits.
304: Attempting to use bit lengths other than these three values for ECDSA keys
305: will fail.
1.176 naddy 306: ECDSA-SK, Ed25519 and Ed25519-SK keys have a fixed length and the
1.118 naddy 307: .Fl b
308: flag will be ignored.
1.66 jmc 309: .It Fl C Ar comment
310: Provides a new comment.
1.2 deraadt 311: .It Fl c
1.1 deraadt 312: Requests changing the comment in the private and public key files.
313: The program will prompt for the file containing the private keys, for
1.41 stevesk 314: the passphrase if the key has one, and for the new comment.
1.81 markus 315: .It Fl D Ar pkcs11
1.157 naddy 316: Download the public keys provided by the PKCS#11 shared library
1.83 markus 317: .Ar pkcs11 .
1.98 djm 318: When used in combination with
319: .Fl s ,
320: this option indicates that a CA key resides in a PKCS#11 token (see the
321: .Sx CERTIFICATES
322: section for details).
1.124 djm 323: .It Fl E Ar fingerprint_hash
324: Specifies the hash algorithm used when displaying key fingerprints.
325: Valid options are:
326: .Dq md5
327: and
328: .Dq sha256 .
329: The default is
330: .Dq sha256 .
1.37 markus 331: .It Fl e
1.40 markus 332: This option will read a private or public OpenSSH key file and
1.154 djm 333: print to stdout a public key in one of the formats specified by the
1.95 djm 334: .Fl m
335: option.
336: The default export format is
337: .Dq RFC4716 .
1.96 jmc 338: This option allows exporting OpenSSH keys for use by other programs, including
1.95 djm 339: several commercial SSH implementations.
1.151 djm 340: .It Fl F Ar hostname | [hostname]:port
1.66 jmc 341: Search for the specified
342: .Ar hostname
1.151 djm 343: (with optional port number)
1.66 jmc 344: in a
345: .Pa known_hosts
346: file, listing any occurrences found.
347: This option is useful to find hashed host names or addresses and may also be
348: used in conjunction with the
349: .Fl H
350: option to print found keys in a hashed format.
351: .It Fl f Ar filename
352: Specifies the filename of the key file.
1.57 jakob 353: .It Fl g
1.62 jakob 354: Use generic DNS format when printing fingerprint resource records using the
1.63 jmc 355: .Fl r
1.62 jakob 356: command.
1.66 jmc 357: .It Fl H
358: Hash a
359: .Pa known_hosts
1.67 dtucker 360: file.
361: This replaces all hostnames and addresses with hashed representations
362: within the specified file; the original content is moved to a file with
363: a .old suffix.
1.66 jmc 364: These hashes may be used normally by
365: .Nm ssh
366: and
367: .Nm sshd ,
368: but they do not reveal identifying information should the file's contents
369: be disclosed.
370: This option will not modify existing hashed hostnames and is therefore safe
371: to use on files that mix hashed and non-hashed names.
1.84 djm 372: .It Fl h
373: When signing a key, create a host certificate instead of a user
374: certificate.
1.220 jsg 375: See the
1.84 djm 376: .Sx CERTIFICATES
377: section for details.
1.85 jmc 378: .It Fl I Ar certificate_identity
1.84 djm 379: Specify the key identity when signing a public key.
1.220 jsg 380: See the
1.84 djm 381: .Sx CERTIFICATES
382: section for details.
1.37 markus 383: .It Fl i
384: This option will read an unencrypted private (or public) key file
1.95 djm 385: in the format specified by the
386: .Fl m
387: option and print an OpenSSH compatible private
1.37 markus 388: (or public) key to stdout.
1.122 jmc 389: This option allows importing keys from other software, including several
390: commercial SSH implementations.
391: The default import format is
392: .Dq RFC4716 .
1.188 jmc 393: .It Fl K
1.187 djm 394: Download resident keys from a FIDO authenticator.
395: Public and private key files will be written to the current directory for
396: each downloaded key.
1.207 djm 397: If multiple FIDO authenticators are attached, keys will be downloaded from
398: the first touched authenticator.
1.221 florian 399: See the
400: .Sx FIDO AUTHENTICATOR
401: section for more information.
1.111 djm 402: .It Fl k
403: Generate a KRL file.
404: In this mode,
405: .Nm
406: will generate a KRL file at the location specified via the
407: .Fl f
1.114 jmc 408: flag that revokes every key or certificate presented on the command line.
1.111 djm 409: Keys/certificates to be revoked may be specified by public key file or
410: using the format described in the
411: .Sx KEY REVOCATION LISTS
412: section.
1.86 djm 413: .It Fl L
1.129 djm 414: Prints the contents of one or more certificates.
1.9 markus 415: .It Fl l
1.77 grunk 416: Show fingerprint of specified public key file.
1.50 markus 417: For RSA and DSA keys
418: .Nm
1.78 jmc 419: tries to find the matching public key file and prints its fingerprint.
420: If combined with
421: .Fl v ,
1.132 jmc 422: a visual ASCII art representation of the key is supplied with the
1.131 djm 423: fingerprint.
1.184 djm 424: .It Fl M Cm generate
425: Generate candidate Diffie-Hellman Group Exchange (DH-GEX) parameters for
426: eventual use by the
427: .Sq diffie-hellman-group-exchange-*
428: key exchange methods.
429: The numbers generated by this operation must be further screened before
430: use.
431: See the
432: .Sx MODULI GENERATION
433: section for more information.
434: .It Fl M Cm screen
435: Screen candidate parameters for Diffie-Hellman Group Exchange.
436: This will accept a list of candidate numbers and test that they are
437: safe (Sophie Germain) primes with acceptable group generators.
438: The results of this operation may be added to the
439: .Pa /etc/moduli
440: file.
441: See the
442: .Sx MODULI GENERATION
443: section for more information.
1.95 djm 444: .It Fl m Ar key_format
1.155 djm 445: Specify a key format for key generation, the
1.95 djm 446: .Fl i
1.155 djm 447: (import),
1.95 djm 448: .Fl e
1.155 djm 449: (export) conversion options, and the
450: .Fl p
451: change passphrase operation.
452: The latter may be used to convert between OpenSSH private key and PEM
453: private key formats.
1.95 djm 454: The supported key formats are:
455: .Dq RFC4716
1.96 jmc 456: (RFC 4716/SSH2 public or private key),
1.95 djm 457: .Dq PKCS8
1.161 djm 458: (PKCS8 public or private key)
1.95 djm 459: or
460: .Dq PEM
461: (PEM public key).
1.161 djm 462: By default OpenSSH will write newly-generated private keys in its own
463: format, but when converting public keys for export the default format is
1.95 djm 464: .Dq RFC4716 .
1.148 djm 465: Setting a format of
466: .Dq PEM
467: when generating or updating a supported private key type will cause the
468: key to be stored in the legacy PEM private key format.
1.66 jmc 469: .It Fl N Ar new_passphrase
470: Provides the new passphrase.
1.84 djm 471: .It Fl n Ar principals
472: Specify one or more principals (user or host names) to be included in
473: a certificate when signing a key.
474: Multiple principals may be specified, separated by commas.
1.220 jsg 475: See the
1.84 djm 476: .Sx CERTIFICATES
477: section for details.
1.93 djm 478: .It Fl O Ar option
1.184 djm 479: Specify a key/value option.
480: These are specific to the operation that
481: .Nm
482: has been requested to perform.
483: .Pp
484: When signing certificates, one of the options listed in the
1.183 djm 485: .Sx CERTIFICATES
1.184 djm 486: section may be specified here.
487: .Pp
488: When performing moduli generation or screening, one of the options
489: listed in the
490: .Sx MODULI GENERATION
491: section may be specified.
492: .Pp
1.221 florian 493: When generating FIDO authenticator-backed keys, the options listed in the
494: .Sx FIDO AUTHENTICATOR
495: section may be specified.
1.185 djm 496: .Pp
1.214 djm 497: When performing signature-related options using the
498: .Fl Y
499: flag, the following options are accepted:
500: .Bl -tag -width Ds
1.219 djm 501: .It Cm hashalg Ns = Ns Ar algorithm
502: Selects the hash algorithm to use for hashing the message to be signed.
503: Valid algorithms are
504: .Dq sha256
505: and
506: .Dq sha512.
507: The default is
508: .Dq sha512.
1.216 djm 509: .It Cm print-pubkey
510: Print the full public key to standard output after signature verification.
1.214 djm 511: .It Cm verify-time Ns = Ns Ar timestamp
512: Specifies a time to use when validating signatures instead of the current
513: time.
1.224 djm 514: The time may be specified as a date or time in the YYYYMMDD[Z] or
515: in YYYYMMDDHHMM[SS][Z] formats.
516: Dates and times will be interpreted in the current system time zone unless
517: suffixed with a Z character, which causes them to be interpreted in the
518: UTC time zone.
1.214 djm 519: .El
520: .Pp
1.185 djm 521: The
522: .Fl O
523: option may be specified multiple times.
1.66 jmc 524: .It Fl P Ar passphrase
525: Provides the (old) passphrase.
1.2 deraadt 526: .It Fl p
1.1 deraadt 527: Requests changing the passphrase of a private key file instead of
1.12 aaron 528: creating a new private key.
529: The program will prompt for the file
1.1 deraadt 530: containing the private key, for the old passphrase, and twice for the
531: new passphrase.
1.113 jmc 532: .It Fl Q
533: Test whether keys have been revoked in a KRL.
1.203 djm 534: If the
535: .Fl l
536: option is also specified then the contents of the KRL will be printed.
1.5 aaron 537: .It Fl q
538: Silence
539: .Nm ssh-keygen .
1.152 djm 540: .It Fl R Ar hostname | [hostname]:port
1.151 djm 541: Removes all keys belonging to the specified
1.64 djm 542: .Ar hostname
1.151 djm 543: (with optional port number)
1.65 jmc 544: from a
1.64 djm 545: .Pa known_hosts
546: file.
1.65 jmc 547: This option is useful to delete hashed hosts (see the
1.64 djm 548: .Fl H
549: option above).
1.66 jmc 550: .It Fl r Ar hostname
551: Print the SSHFP fingerprint resource record named
552: .Ar hostname
553: for the specified public key file.
1.84 djm 554: .It Fl s Ar ca_key
555: Certify (sign) a public key using the specified CA key.
1.220 jsg 556: See the
1.84 djm 557: .Sx CERTIFICATES
558: section for details.
1.111 djm 559: .Pp
560: When generating a KRL,
561: .Fl s
1.112 jmc 562: specifies a path to a CA public key file used to revoke certificates directly
1.111 djm 563: by key ID or serial number.
564: See the
565: .Sx KEY REVOCATION LISTS
566: section for details.
1.175 djm 567: .It Fl t Cm dsa | ecdsa | ecdsa-sk | ed25519 | ed25519-sk | rsa
1.66 jmc 568: Specifies the type of key to create.
569: The possible values are
1.100 naddy 570: .Dq dsa ,
1.118 naddy 571: .Dq ecdsa ,
1.173 naddy 572: .Dq ecdsa-sk ,
1.118 naddy 573: .Dq ed25519 ,
1.175 djm 574: .Dq ed25519-sk ,
1.100 naddy 575: or
1.139 jmc 576: .Dq rsa .
1.159 djm 577: .Pp
578: This flag may also be used to specify the desired signature type when
1.160 jmc 579: signing certificates using an RSA CA key.
1.159 djm 580: The available RSA signature variants are
581: .Dq ssh-rsa
582: (SHA1 signatures, not recommended),
1.160 jmc 583: .Dq rsa-sha2-256 ,
584: and
1.159 djm 585: .Dq rsa-sha2-512
586: (the default).
1.142 djm 587: .It Fl U
588: When used in combination with
1.222 djm 589: .Fl s
590: or
1.225 ! jmc 591: .Fl Y Cm sign ,
1.142 djm 592: this option indicates that a CA key resides in a
593: .Xr ssh-agent 1 .
594: See the
595: .Sx CERTIFICATES
596: section for more information.
1.112 jmc 597: .It Fl u
598: Update a KRL.
599: When specified with
600: .Fl k ,
1.114 jmc 601: keys listed via the command line are added to the existing KRL rather than
1.112 jmc 602: a new KRL being created.
1.84 djm 603: .It Fl V Ar validity_interval
604: Specify a validity interval when signing a certificate.
605: A validity interval may consist of a single time, indicating that the
606: certificate is valid beginning now and expiring at that time, or may consist
607: of two times separated by a colon to indicate an explicit time interval.
1.145 djm 608: .Pp
1.224 djm 609: The start time may be specified as:
610: .Bl -bullet -compact
611: .It
612: The string
1.145 djm 613: .Dq always
1.224 djm 614: to indicate the certificate has no specified start time.
615: .It
616: A date or time in the system time zone formatted as YYYYMMDD or
617: YYYYMMDDHHMM[SS].
618: .It
619: A date or time in the UTC time zone as YYYYMMDDZ or YYYYMMDDHHMM[SS]Z.
620: .It
621: A relative time before the current system time consisting of a minus sign
622: followed by an interval in the format described in the
1.116 jmc 623: TIME FORMATS section of
1.90 jmc 624: .Xr sshd_config 5 .
1.224 djm 625: .It
626: A raw seconds since epoch (Jan 1 1970 00:00:00 UTC) as a hexadecimal
627: number beginning with
628: .Dq 0x .
629: .El
1.145 djm 630: .Pp
1.224 djm 631: The end time may be specified similarly to the start time:
632: .Bl -bullet -compact
633: .It
634: The string
1.145 djm 635: .Dq forever
1.224 djm 636: to indicate the certificate has no specified end time.
637: .It
638: A date or time in the system time zone formatted as YYYYMMDD or
639: YYYYMMDDHHMM[SS].
640: .It
641: A date or time in the UTC time zone as YYYYMMDDZ or YYYYMMDDHHMM[SS]Z.
642: .It
643: A relative time after the current system time consisting of a plus sign
644: followed by an interval in the format described in the
645: TIME FORMATS section of
646: .Xr sshd_config 5 .
647: .It
648: A raw seconds since epoch (Jan 1 1970 00:00:00 UTC) as a hexadecimal
649: number beginning with
650: .Dq 0x .
651: .El
1.84 djm 652: .Pp
653: For example:
1.224 djm 654: .Bl -tag -width Ds
655: .It +52w1d
656: Valid from now to 52 weeks and one day from now.
657: .It -4w:+4w
658: Valid from four weeks ago to four weeks from now.
659: .It 20100101123000:20110101123000
660: Valid from 12:30 PM, January 1st, 2010 to 12:30 PM, January 1st, 2011.
661: .It 20100101123000Z:20110101123000Z
662: Similar, but interpreted in the UTC time zone rather than the system time zone.
663: .It -1d:20110101
664: Valid from yesterday to midnight, January 1st, 2011.
665: .It 0x1:0x2000000000
666: Valid from roughly early 1970 to May 2033.
667: .It -1m:forever
668: Valid from one minute ago and never expiring.
669: .El
1.61 djm 670: .It Fl v
671: Verbose mode.
672: Causes
673: .Nm
674: to print debugging messages about its progress.
675: This is helpful for debugging moduli generation.
676: Multiple
677: .Fl v
678: options increase the verbosity.
679: The maximum is 3.
1.173 naddy 680: .It Fl w Ar provider
1.180 naddy 681: Specifies a path to a library that will be used when creating
682: FIDO authenticator-hosted keys, overriding the default of using
683: the internal USB HID support.
1.196 djm 684: .It Fl Y Cm find-principals
685: Find the principal(s) associated with the public key of a signature,
1.194 djm 686: provided using the
687: .Fl s
688: flag in an authorized signers file provided using the
689: .Fl f
690: flag.
691: The format of the allowed signers file is documented in the
692: .Sx ALLOWED SIGNERS
1.195 jmc 693: section below.
1.217 djm 694: If one or more matching principals are found, they are returned on
695: standard output.
696: .It Fl Y Cm match-principals
697: Find principal matching the principal name provided using the
698: .Fl I
699: flag in the authorized signers file specified using the
700: .Fl f
701: flag.
1.196 djm 702: If one or more matching principals are found, they are returned on
703: standard output.
1.182 jmc 704: .It Fl Y Cm check-novalidate
705: Checks that a signature generated using
706: .Nm
707: .Fl Y Cm sign
708: has a valid structure.
709: This does not validate if a signature comes from an authorized signer.
710: When testing a signature,
711: .Nm
712: accepts a message on standard input and a signature namespace using
713: .Fl n .
714: A file containing the corresponding signature must also be supplied using the
715: .Fl s
716: flag.
717: Successful testing of the signature is signalled by
718: .Nm
719: returning a zero exit status.
1.166 jmc 720: .It Fl Y Cm sign
1.163 djm 721: Cryptographically sign a file or some data using a SSH key.
722: When signing,
723: .Nm
724: accepts zero or more files to sign on the command-line - if no files
725: are specified then
726: .Nm
727: will sign data presented on standard input.
728: Signatures are written to the path of the input file with
729: .Dq .sig
730: appended, or to standard output if the message to be signed was read from
731: standard input.
732: .Pp
733: The key used for signing is specified using the
734: .Fl f
735: option and may refer to either a private key, or a public key with the private
736: half available via
737: .Xr ssh-agent 1 .
738: An additional signature namespace, used to prevent signature confusion across
739: different domains of use (e.g. file signing vs email signing) must be provided
740: via the
741: .Fl n
742: flag.
743: Namespaces are arbitrary strings, and may include:
744: .Dq file
745: for file signing,
746: .Dq email
747: for email signing.
748: For custom uses, it is recommended to use names following a
749: NAMESPACE@YOUR.DOMAIN pattern to generate unambiguous namespaces.
1.166 jmc 750: .It Fl Y Cm verify
1.163 djm 751: Request to verify a signature generated using
752: .Nm
1.166 jmc 753: .Fl Y Cm sign
1.163 djm 754: as described above.
755: When verifying a signature,
756: .Nm
757: accepts a message on standard input and a signature namespace using
758: .Fl n .
759: A file containing the corresponding signature must also be supplied using the
760: .Fl s
761: flag, along with the identity of the signer using
762: .Fl I
763: and a list of allowed signers via the
764: .Fl f
765: flag.
766: The format of the allowed signers file is documented in the
767: .Sx ALLOWED SIGNERS
768: section below.
769: A file containing revoked keys can be passed using the
770: .Fl r
1.165 jmc 771: flag.
772: The revocation file may be a KRL or a one-per-line list of public keys.
1.163 djm 773: Successful verification by an authorized signer is signalled by
774: .Nm
775: returning a zero exit status.
1.181 jmc 776: .It Fl y
777: This option will read a private
778: OpenSSH format file and print an OpenSSH public key to stdout.
1.212 dtucker 779: .It Fl Z Ar cipher
780: Specifies the cipher to use for encryption when writing an OpenSSH-format
781: private key file.
782: The list of available ciphers may be obtained using
783: .Qq ssh -Q cipher .
784: The default is
785: .Dq aes256-ctr .
1.93 djm 786: .It Fl z Ar serial_number
787: Specifies a serial number to be embedded in the certificate to distinguish
788: this certificate from others from the same CA.
1.156 djm 789: If the
790: .Ar serial_number
791: is prefixed with a
792: .Sq +
793: character, then the serial number will be incremented for each certificate
794: signed on a single command-line.
1.93 djm 795: The default serial number is zero.
1.111 djm 796: .Pp
797: When generating a KRL, the
798: .Fl z
799: flag is used to specify a KRL version number.
1.2 deraadt 800: .El
1.60 djm 801: .Sh MODULI GENERATION
802: .Nm
803: may be used to generate groups for the Diffie-Hellman Group Exchange
804: (DH-GEX) protocol.
805: Generating these groups is a two-step process: first, candidate
806: primes are generated using a fast, but memory intensive process.
807: These candidate primes are then tested for suitability (a CPU-intensive
808: process).
809: .Pp
810: Generation of primes is performed using the
1.184 djm 811: .Fl M Cm generate
1.60 djm 812: option.
813: The desired length of the primes may be specified by the
1.184 djm 814: .Fl O Cm bits
1.60 djm 815: option.
816: For example:
817: .Pp
1.184 djm 818: .Dl # ssh-keygen -M generate -O bits=2048 moduli-2048.candidates
1.60 djm 819: .Pp
820: By default, the search for primes begins at a random point in the
821: desired length range.
822: This may be overridden using the
1.184 djm 823: .Fl O Cm start
1.60 djm 824: option, which specifies a different start point (in hex).
825: .Pp
1.109 dtucker 826: Once a set of candidates have been generated, they must be screened for
1.60 djm 827: suitability.
828: This may be performed using the
1.184 djm 829: .Fl M Cm screen
1.60 djm 830: option.
831: In this mode
832: .Nm
833: will read candidates from standard input (or a file specified using the
834: .Fl f
835: option).
836: For example:
837: .Pp
1.184 djm 838: .Dl # ssh-keygen -M screen -f moduli-2048.candidates moduli-2048
1.60 djm 839: .Pp
840: By default, each candidate will be subjected to 100 primality tests.
841: This may be overridden using the
1.184 djm 842: .Fl O Cm prime-tests
1.60 djm 843: option.
844: The DH generator value will be chosen automatically for the
845: prime under consideration.
846: If a specific generator is desired, it may be requested using the
1.184 djm 847: .Fl O Cm generator
1.60 djm 848: option.
1.66 jmc 849: Valid generator values are 2, 3, and 5.
1.60 djm 850: .Pp
851: Screened DH groups may be installed in
852: .Pa /etc/moduli .
1.213 dtucker 853: It is important that this file contains moduli of a range of bit lengths.
1.184 djm 854: .Pp
855: A number of options are available for moduli generation and screening via the
856: .Fl O
857: flag:
1.186 jmc 858: .Bl -tag -width Ds
1.184 djm 859: .It Ic lines Ns = Ns Ar number
860: Exit after screening the specified number of lines while performing DH
861: candidate screening.
862: .It Ic start-line Ns = Ns Ar line-number
863: Start screening at the specified line number while performing DH candidate
864: screening.
865: .It Ic checkpoint Ns = Ns Ar filename
866: Write the last line processed to the specified file while performing DH
867: candidate screening.
868: This will be used to skip lines in the input file that have already been
869: processed if the job is restarted.
870: .It Ic memory Ns = Ns Ar mbytes
871: Specify the amount of memory to use (in megabytes) when generating
872: candidate moduli for DH-GEX.
873: .It Ic start Ns = Ns Ar hex-value
874: Specify start point (in hex) when generating candidate moduli for DH-GEX.
875: .It Ic generator Ns = Ns Ar value
876: Specify desired generator (in decimal) when testing candidate moduli for DH-GEX.
877: .El
1.84 djm 878: .Sh CERTIFICATES
879: .Nm
880: supports signing of keys to produce certificates that may be used for
881: user or host authentication.
882: Certificates consist of a public key, some identity information, zero or
1.94 jmc 883: more principal (user or host) names and a set of options that
1.84 djm 884: are signed by a Certification Authority (CA) key.
885: Clients or servers may then trust only the CA key and verify its signature
886: on a certificate rather than trusting many user/host keys.
887: Note that OpenSSH certificates are a different, and much simpler, format to
888: the X.509 certificates used in
889: .Xr ssl 8 .
890: .Pp
891: .Nm
892: supports two types of certificates: user and host.
893: User certificates authenticate users to servers, whereas host certificates
1.85 jmc 894: authenticate server hosts to users.
895: To generate a user certificate:
1.84 djm 896: .Pp
897: .Dl $ ssh-keygen -s /path/to/ca_key -I key_id /path/to/user_key.pub
898: .Pp
899: The resultant certificate will be placed in
1.91 djm 900: .Pa /path/to/user_key-cert.pub .
1.84 djm 901: A host certificate requires the
902: .Fl h
903: option:
904: .Pp
905: .Dl $ ssh-keygen -s /path/to/ca_key -I key_id -h /path/to/host_key.pub
906: .Pp
907: The host certificate will be output to
1.91 djm 908: .Pa /path/to/host_key-cert.pub .
1.98 djm 909: .Pp
910: It is possible to sign using a CA key stored in a PKCS#11 token by
911: providing the token library using
912: .Fl D
913: and identifying the CA key by providing its public half as an argument
914: to
915: .Fl s :
916: .Pp
1.127 naddy 917: .Dl $ ssh-keygen -s ca_key.pub -D libpkcs11.so -I key_id user_key.pub
1.142 djm 918: .Pp
919: Similarly, it is possible for the CA key to be hosted in a
920: .Xr ssh-agent 1 .
921: This is indicated by the
922: .Fl U
923: flag and, again, the CA key must be identified by its public half.
924: .Pp
925: .Dl $ ssh-keygen -Us ca_key.pub -I key_id user_key.pub
1.98 djm 926: .Pp
927: In all cases,
1.84 djm 928: .Ar key_id
929: is a "key identifier" that is logged by the server when the certificate
930: is used for authentication.
931: .Pp
932: Certificates may be limited to be valid for a set of principal (user/host)
933: names.
934: By default, generated certificates are valid for all users or hosts.
935: To generate a certificate for a specified set of principals:
936: .Pp
937: .Dl $ ssh-keygen -s ca_key -I key_id -n user1,user2 user_key.pub
1.127 naddy 938: .Dl "$ ssh-keygen -s ca_key -I key_id -h -n host.domain host_key.pub"
1.84 djm 939: .Pp
940: Additional limitations on the validity and use of user certificates may
1.94 jmc 941: be specified through certificate options.
1.93 djm 942: A certificate option may disable features of the SSH session, may be
1.84 djm 943: valid only when presented from particular source addresses or may
944: force the use of a specific command.
1.183 djm 945: .Pp
946: The options that are valid for user certificates are:
947: .Pp
948: .Bl -tag -width Ds -compact
949: .It Ic clear
950: Clear all enabled permissions.
951: This is useful for clearing the default set of permissions so permissions may
952: be added individually.
953: .Pp
954: .It Ic critical : Ns Ar name Ns Op Ns = Ns Ar contents
955: .It Ic extension : Ns Ar name Ns Op Ns = Ns Ar contents
956: Includes an arbitrary certificate critical option or extension.
957: The specified
958: .Ar name
959: should include a domain suffix, e.g.\&
960: .Dq name@example.com .
961: If
962: .Ar contents
963: is specified then it is included as the contents of the extension/option
964: encoded as a string, otherwise the extension/option is created with no
965: contents (usually indicating a flag).
966: Extensions may be ignored by a client or server that does not recognise them,
967: whereas unknown critical options will cause the certificate to be refused.
968: .Pp
969: .It Ic force-command Ns = Ns Ar command
970: Forces the execution of
971: .Ar command
972: instead of any shell or command specified by the user when
973: the certificate is used for authentication.
974: .Pp
975: .It Ic no-agent-forwarding
976: Disable
977: .Xr ssh-agent 1
978: forwarding (permitted by default).
979: .Pp
980: .It Ic no-port-forwarding
981: Disable port forwarding (permitted by default).
982: .Pp
983: .It Ic no-pty
984: Disable PTY allocation (permitted by default).
985: .Pp
986: .It Ic no-user-rc
987: Disable execution of
988: .Pa ~/.ssh/rc
989: by
990: .Xr sshd 8
991: (permitted by default).
992: .Pp
993: .It Ic no-x11-forwarding
994: Disable X11 forwarding (permitted by default).
995: .Pp
996: .It Ic permit-agent-forwarding
997: Allows
998: .Xr ssh-agent 1
999: forwarding.
1000: .Pp
1001: .It Ic permit-port-forwarding
1002: Allows port forwarding.
1003: .Pp
1004: .It Ic permit-pty
1005: Allows PTY allocation.
1006: .Pp
1007: .It Ic permit-user-rc
1008: Allows execution of
1009: .Pa ~/.ssh/rc
1010: by
1011: .Xr sshd 8 .
1012: .Pp
1013: .It Ic permit-X11-forwarding
1014: Allows X11 forwarding.
1015: .Pp
1016: .It Ic no-touch-required
1.206 djm 1017: Do not require signatures made using this key include demonstration
1.193 naddy 1018: of user presence (e.g. by having the user touch the authenticator).
1.192 naddy 1019: This option only makes sense for the FIDO authenticator algorithms
1.183 djm 1020: .Cm ecdsa-sk
1021: and
1022: .Cm ed25519-sk .
1023: .Pp
1024: .It Ic source-address Ns = Ns Ar address_list
1025: Restrict the source addresses from which the certificate is considered valid.
1026: The
1027: .Ar address_list
1028: is a comma-separated list of one or more address/netmask pairs in CIDR
1029: format.
1.206 djm 1030: .Pp
1031: .It Ic verify-required
1032: Require signatures made using this key indicate that the user was first
1033: verified.
1034: This option only makes sense for the FIDO authenticator algorithms
1035: .Cm ecdsa-sk
1036: and
1037: .Cm ed25519-sk .
1038: Currently PIN authentication is the only supported verification method,
1039: but other methods may be supported in the future.
1.183 djm 1040: .El
1041: .Pp
1042: At present, no standard options are valid for host keys.
1.84 djm 1043: .Pp
1044: Finally, certificates may be defined with a validity lifetime.
1045: The
1046: .Fl V
1047: option allows specification of certificate start and end times.
1048: A certificate that is presented at a time outside this range will not be
1049: considered valid.
1.210 dtucker 1050: By default, certificates are valid from the
1.110 jmc 1051: .Ux
1052: Epoch to the distant future.
1.84 djm 1053: .Pp
1054: For certificates to be used for user or host authentication, the CA
1055: public key must be trusted by
1056: .Xr sshd 8
1057: or
1058: .Xr ssh 1 .
1.220 jsg 1059: Refer to those manual pages for details.
1.221 florian 1060: .Sh FIDO AUTHENTICATOR
1061: .Nm
1062: is able to to generate FIDO authenticator-backed keys, after which
1063: they may be used much like any other key type supported by OpenSSH, so
1064: long as the hardware authenticator is attached when the keys are used.
1065: FIDO authenticators generally require the user to explicitly authorise
1066: operations by touching or tapping them.
1067: FIDO keys consist of two parts: a key handle part stored in the
1068: private key file on disk, and a per-device private key that is unique
1069: to each FIDO authenticator and that cannot be exported from the
1070: authenticator hardware.
1071: These are combined by the hardware at authentication time to derive
1072: the real key that is used to sign authentication challenges.
1073: Supported key types are
1074: .Cm ecdsa-sk
1075: and
1076: .Cm ed25519-sk .
1077: .Pp
1078: The options that are valid for FIDO keys are:
1079: .Bl -tag -width Ds
1080: .It Cm application
1081: Override the default FIDO application/origin string of
1082: .Dq ssh: .
1083: This may be useful when generating host or domain-specific resident keys.
1084: The specified application string must begin with
1085: .Dq ssh: .
1086: .It Cm challenge Ns = Ns Ar path
1087: Specifies a path to a challenge string that will be passed to the
1088: FIDO authenticator during key generation.
1089: The challenge string may be used as part of an out-of-band
1090: protocol for key enrollment
1091: (a random challenge is used by default).
1092: .It Cm device
1093: Explicitly specify a
1094: .Xr fido 4
1095: device to use, rather than letting the authenticator middleware select one.
1096: .It Cm no-touch-required
1097: Indicate that the generated private key should not require touch
1098: events (user presence) when making signatures.
1099: Note that
1100: .Xr sshd 8
1101: will refuse such signatures by default, unless overridden via
1102: an authorized_keys option.
1103: .It Cm resident
1104: Indicate that the key handle should be stored on the FIDO
1105: authenticator itself.
1106: This makes it easier to use the authenticator on multiple computers.
1107: Resident keys may be supported on FIDO2 authenticators and typically
1108: require that a PIN be set on the authenticator prior to generation.
1109: Resident keys may be loaded off the authenticator using
1110: .Xr ssh-add 1 .
1111: Storing both parts of a key on a FIDO authenticator increases the likelihood
1112: of an attacker being able to use a stolen authenticator device.
1113: .It Cm user
1114: A username to be associated with a resident key,
1115: overriding the empty default username.
1116: Specifying a username may be useful when generating multiple resident keys
1117: for the same application name.
1118: .It Cm verify-required
1119: Indicate that this private key should require user verification for
1120: each signature.
1121: Not all FIDO authenticators support this option.
1122: Currently PIN authentication is the only supported verification method,
1123: but other methods may be supported in the future.
1124: .It Cm write-attestation Ns = Ns Ar path
1125: May be used at key generation time to record the attestation data
1126: returned from FIDO authenticators during key generation.
1127: This information is potentially sensitive.
1128: By default, this information is discarded.
1129: .El
1.111 djm 1130: .Sh KEY REVOCATION LISTS
1131: .Nm
1132: is able to manage OpenSSH format Key Revocation Lists (KRLs).
1133: These binary files specify keys or certificates to be revoked using a
1.119 tedu 1134: compact format, taking as little as one bit per certificate if they are being
1.111 djm 1135: revoked by serial number.
1136: .Pp
1137: KRLs may be generated using the
1138: .Fl k
1139: flag.
1.114 jmc 1140: This option reads one or more files from the command line and generates a new
1.111 djm 1141: KRL.
1142: The files may either contain a KRL specification (see below) or public keys,
1143: listed one per line.
1144: Plain public keys are revoked by listing their hash or contents in the KRL and
1145: certificates revoked by serial number or key ID (if the serial is zero or
1146: not available).
1147: .Pp
1148: Revoking keys using a KRL specification offers explicit control over the
1149: types of record used to revoke keys and may be used to directly revoke
1150: certificates by serial number or key ID without having the complete original
1151: certificate on hand.
1152: A KRL specification consists of lines containing one of the following directives
1153: followed by a colon and some directive-specific information.
1154: .Bl -tag -width Ds
1.115 jmc 1155: .It Cm serial : Ar serial_number Ns Op - Ns Ar serial_number
1.111 djm 1156: Revokes a certificate with the specified serial number.
1.112 jmc 1157: Serial numbers are 64-bit values, not including zero and may be expressed
1.111 djm 1158: in decimal, hex or octal.
1159: If two serial numbers are specified separated by a hyphen, then the range
1160: of serial numbers including and between each is revoked.
1161: The CA key must have been specified on the
1162: .Nm
1.114 jmc 1163: command line using the
1.111 djm 1164: .Fl s
1165: option.
1166: .It Cm id : Ar key_id
1167: Revokes a certificate with the specified key ID string.
1168: The CA key must have been specified on the
1169: .Nm
1.114 jmc 1170: command line using the
1.111 djm 1171: .Fl s
1172: option.
1173: .It Cm key : Ar public_key
1174: Revokes the specified key.
1.112 jmc 1175: If a certificate is listed, then it is revoked as a plain public key.
1.111 djm 1176: .It Cm sha1 : Ar public_key
1.149 djm 1177: Revokes the specified key by including its SHA1 hash in the KRL.
1178: .It Cm sha256 : Ar public_key
1179: Revokes the specified key by including its SHA256 hash in the KRL.
1180: KRLs that revoke keys by SHA256 hash are not supported by OpenSSH versions
1181: prior to 7.9.
1182: .It Cm hash : Ar fingerprint
1.150 djm 1183: Revokes a key using a fingerprint hash, as obtained from a
1.149 djm 1184: .Xr sshd 8
1185: authentication log message or the
1186: .Nm
1187: .Fl l
1188: flag.
1189: Only SHA256 fingerprints are supported here and resultant KRLs are
1190: not supported by OpenSSH versions prior to 7.9.
1.111 djm 1191: .El
1192: .Pp
1193: KRLs may be updated using the
1194: .Fl u
1195: flag in addition to
1196: .Fl k .
1.114 jmc 1197: When this option is specified, keys listed via the command line are merged into
1.111 djm 1198: the KRL, adding to those already there.
1199: .Pp
1200: It is also possible, given a KRL, to test whether it revokes a particular key
1201: (or keys).
1202: The
1203: .Fl Q
1.128 jmc 1204: flag will query an existing KRL, testing each key specified on the command line.
1.114 jmc 1205: If any key listed on the command line has been revoked (or an error encountered)
1.111 djm 1206: then
1207: .Nm
1208: will exit with a non-zero exit status.
1209: A zero exit status will only be returned if no key was revoked.
1.163 djm 1210: .Sh ALLOWED SIGNERS
1211: When verifying signatures,
1212: .Nm
1213: uses a simple list of identities and keys to determine whether a signature
1214: comes from an authorized source.
1215: This "allowed signers" file uses a format patterned after the
1216: AUTHORIZED_KEYS FILE FORMAT described in
1.165 jmc 1217: .Xr sshd 8 .
1.163 djm 1218: Each line of the file contains the following space-separated fields:
1219: principals, options, keytype, base64-encoded key.
1220: Empty lines and lines starting with a
1221: .Ql #
1222: are ignored as comments.
1223: .Pp
1.210 dtucker 1224: The principals field is a pattern-list (see PATTERNS in
1.163 djm 1225: .Xr ssh_config 5 )
1226: consisting of one or more comma-separated USER@DOMAIN identity patterns
1227: that are accepted for signing.
1228: When verifying, the identity presented via the
1.172 jmc 1229: .Fl I
1230: option must match a principals pattern in order for the corresponding key to be
1.163 djm 1231: considered acceptable for verification.
1232: .Pp
1233: The options (if present) consist of comma-separated option specifications.
1234: No spaces are permitted, except within double quotes.
1235: The following option specifications are supported (note that option keywords
1236: are case-insensitive):
1237: .Bl -tag -width Ds
1238: .It Cm cert-authority
1239: Indicates that this key is accepted as a certificate authority (CA) and
1240: that certificates signed by this CA may be accepted for verification.
1.214 djm 1241: .It Cm namespaces Ns = Ns "namespace-list"
1.163 djm 1242: Specifies a pattern-list of namespaces that are accepted for this key.
1.164 djm 1243: If this option is present, the signature namespace embedded in the
1.163 djm 1244: signature object and presented on the verification command-line must
1245: match the specified list before the key will be considered acceptable.
1.214 djm 1246: .It Cm valid-after Ns = Ns "timestamp"
1247: Indicates that the key is valid for use at or after the specified timestamp,
1.224 djm 1248: which may be a date or time in the YYYYMMDD[Z] or YYYYMMDDHHMM[SS][Z] formats.
1249: Dates and times will be interpreted in the current system time zone unless
1250: suffixed with a Z character, which causes them to be interpreted in the UTC
1251: time zone.
1.214 djm 1252: .It Cm valid-before Ns = Ns "timestamp"
1253: Indicates that the key is valid for use at or before the specified timestamp.
1.163 djm 1254: .El
1255: .Pp
1256: When verifying signatures made by certificates, the expected principal
1257: name must match both the principals pattern in the allowed signers file and
1258: the principals embedded in the certificate itself.
1259: .Pp
1260: An example allowed signers file:
1261: .Bd -literal -offset 3n
1262: # Comments allowed at start of line
1263: user1@example.com,user2@example.com ssh-rsa AAAAX1...
1264: # A certificate authority, trusted for all principals in a domain.
1265: *@example.com cert-authority ssh-ed25519 AAAB4...
1266: # A key that is accepted only for file signing.
1267: user2@example.com namespaces="file" ssh-ed25519 AAA41...
1268: .Ed
1.173 naddy 1269: .Sh ENVIRONMENT
1270: .Bl -tag -width Ds
1271: .It Ev SSH_SK_PROVIDER
1.201 djm 1272: Specifies a path to a library that will be used when loading any
1273: FIDO authenticator-hosted keys, overriding the default of using
1274: the built-in USB HID support.
1.173 naddy 1275: .El
1.2 deraadt 1276: .Sh FILES
1.100 naddy 1277: .Bl -tag -width Ds -compact
1.68 djm 1278: .It Pa ~/.ssh/id_dsa
1.100 naddy 1279: .It Pa ~/.ssh/id_ecdsa
1.173 naddy 1280: .It Pa ~/.ssh/id_ecdsa_sk
1.118 naddy 1281: .It Pa ~/.ssh/id_ed25519
1.176 naddy 1282: .It Pa ~/.ssh/id_ed25519_sk
1.100 naddy 1283: .It Pa ~/.ssh/id_rsa
1.180 naddy 1284: Contains the DSA, ECDSA, authenticator-hosted ECDSA, Ed25519,
1285: authenticator-hosted Ed25519 or RSA authentication identity of the user.
1.15 deraadt 1286: This file should not be readable by anyone but the user.
1287: It is possible to
1288: specify a passphrase when generating the key; that passphrase will be
1.80 dtucker 1289: used to encrypt the private part of this file using 128-bit AES.
1.15 deraadt 1290: This file is not automatically accessed by
1291: .Nm
1292: but it is offered as the default file for the private key.
1.46 markus 1293: .Xr ssh 1
1.15 deraadt 1294: will read this file when a login attempt is made.
1.100 naddy 1295: .Pp
1.68 djm 1296: .It Pa ~/.ssh/id_dsa.pub
1.100 naddy 1297: .It Pa ~/.ssh/id_ecdsa.pub
1.173 naddy 1298: .It Pa ~/.ssh/id_ecdsa_sk.pub
1.118 naddy 1299: .It Pa ~/.ssh/id_ed25519.pub
1.176 naddy 1300: .It Pa ~/.ssh/id_ed25519_sk.pub
1.68 djm 1301: .It Pa ~/.ssh/id_rsa.pub
1.180 naddy 1302: Contains the DSA, ECDSA, authenticator-hosted ECDSA, Ed25519,
1303: authenticator-hosted Ed25519 or RSA public key for authentication.
1.15 deraadt 1304: The contents of this file should be added to
1.68 djm 1305: .Pa ~/.ssh/authorized_keys
1.15 deraadt 1306: on all machines
1.49 deraadt 1307: where the user wishes to log in using public key authentication.
1.12 aaron 1308: There is no need to keep the contents of this file secret.
1.100 naddy 1309: .Pp
1.60 djm 1310: .It Pa /etc/moduli
1311: Contains Diffie-Hellman groups used for DH-GEX.
1312: The file format is described in
1313: .Xr moduli 5 .
1.19 aaron 1314: .El
1.2 deraadt 1315: .Sh SEE ALSO
1316: .Xr ssh 1 ,
1317: .Xr ssh-add 1 ,
1.8 ericj 1318: .Xr ssh-agent 1 ,
1.60 djm 1319: .Xr moduli 5 ,
1.30 itojun 1320: .Xr sshd 8
1.37 markus 1321: .Rs
1.73 markus 1322: .%R RFC 4716
1323: .%T "The Secure Shell (SSH) Public Key File Format"
1324: .%D 2006
1.37 markus 1325: .Re
1.59 jmc 1326: .Sh AUTHORS
1327: OpenSSH is a derivative of the original and free
1328: ssh 1.2.12 release by Tatu Ylonen.
1329: Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1330: Theo de Raadt and Dug Song
1331: removed many bugs, re-added newer features and
1332: created OpenSSH.
1333: Markus Friedl contributed the support for SSH
1334: protocol versions 1.5 and 2.0.
![[BACK]](/icons/back.gif){kind=icon}
Return to ssh-keygen.1 CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / src / usr.bin / ssh