xref: /openssh-portable/PROTOCOL.certkeys (revision 46925ae2)
1This document describes a simple public-key certificate authentication
2system for use by SSH.
7The SSH protocol currently supports a simple public key authentication
8mechanism. Unlike other public key implementations, SSH eschews the use
9of X.509 certificates and uses raw keys. This approach has some benefits
10relating to simplicity of configuration and minimisation of attack
11surface, but it does not support the important use-cases of centrally
12managed, passwordless authentication and centrally certified host keys.
14These protocol extensions build on the simple public key authentication
15system already in SSH to allow certificate-based authentication. The
16certificates used are not traditional X.509 certificates, with numerous
17options and complex encoding rules, but something rather more minimal: a
18key, some identity information and usage options that have been signed
19with some other trusted key.
21A sshd server may be configured to allow authentication via certified
22keys, by extending the existing ~/.ssh/authorized_keys mechanism to
23allow specification of certification authority keys in addition to
24raw user keys. The ssh client will support automatic verification of
25acceptance of certified host keys, by adding a similar ability to
26specify CA keys in ~/.ssh/known_hosts.
28All certificate types include certification information along with the
29public key that is used to sign challenges. In OpenSSH, ssh-keygen
30performs the CA signing operation.
32Certified keys are represented using new key types:
34    ssh-rsa-cert-v01@openssh.com
35    ssh-dss-cert-v01@openssh.com
36    ecdsa-sha2-nistp256-cert-v01@openssh.com
37    ecdsa-sha2-nistp384-cert-v01@openssh.com
38    ecdsa-sha2-nistp521-cert-v01@openssh.com
39    ssh-ed25519-cert-v01@openssh.com
41Two additional types exist for RSA certificates to force use of
42SHA-2 signatures (SHA-256 and SHA-512 respectively):
44    rsa-sha2-256-cert-v01@openssh.com
45    rsa-sha2-512-cert-v01@openssh.com
47These RSA/SHA-2 types should not appear in keys at rest or transmitted
48on their wire, but do appear in a SSH_MSG_KEXINIT's host-key algorithms
49field or in the "public key algorithm name" field of a "publickey"
50SSH_USERAUTH_REQUEST to indicate that the signature will use the
51specified algorithm.
53Protocol extensions
56The SSH wire protocol includes several extensibility mechanisms.
57These modifications shall take advantage of namespaced public key
58algorithm names to add support for certificate authentication without
59breaking the protocol - implementations that do not support the
60extensions will simply ignore them.
62Authentication using the new key formats described below proceeds
63using the existing SSH "publickey" authentication method described
64in RFC4252 section 7.
66New public key formats
69The certificate key types take a similar high-level format (note: data
70types and encoding are as per RFC4251 section 5). The serialised wire
71encoding of these certificates is also used for storing them on disk.
73#define SSH_CERT_TYPE_USER    1
74#define SSH_CERT_TYPE_HOST    2
76RSA certificate
78    string    "ssh-rsa-cert-v01@openssh.com"
79    string    nonce
80    mpint     e
81    mpint     n
82    uint64    serial
83    uint32    type
84    string    key id
85    string    valid principals
86    uint64    valid after
87    uint64    valid before
88    string    critical options
89    string    extensions
90    string    reserved
91    string    signature key
92    string    signature
94DSA certificate
96    string    "ssh-dss-cert-v01@openssh.com"
97    string    nonce
98    mpint     p
99    mpint     q
100    mpint     g
101    mpint     y
102    uint64    serial
103    uint32    type
104    string    key id
105    string    valid principals
106    uint64    valid after
107    uint64    valid before
108    string    critical options
109    string    extensions
110    string    reserved
111    string    signature key
112    string    signature
114ECDSA certificate
116    string    "ecdsa-sha2-nistp256-cert-v01@openssh.com" |
117              "ecdsa-sha2-nistp384-cert-v01@openssh.com" |
118              "ecdsa-sha2-nistp521-cert-v01@openssh.com"
119    string    nonce
120    string    curve
121    string    public_key
122    uint64    serial
123    uint32    type
124    string    key id
125    string    valid principals
126    uint64    valid after
127    uint64    valid before
128    string    critical options
129    string    extensions
130    string    reserved
131    string    signature key
132    string    signature
134ED25519 certificate
136    string    "ssh-ed25519-cert-v01@openssh.com"
137    string    nonce
138    string    pk
139    uint64    serial
140    uint32    type
141    string    key id
142    string    valid principals
143    uint64    valid after
144    uint64    valid before
145    string    critical options
146    string    extensions
147    string    reserved
148    string    signature key
149    string    signature
151The nonce field is a CA-provided random bitstring of arbitrary length
152(but typically 16 or 32 bytes) included to make attacks that depend on
153inducing collisions in the signature hash infeasible.
155e and n are the RSA exponent and public modulus respectively.
157p, q, g, y are the DSA parameters as described in FIPS-186-2.
159curve and public key are respectively the ECDSA "[identifier]" and "Q"
160defined in section 3.1 of RFC5656.
162pk is the encoded Ed25519 public key as defined by
165serial is an optional certificate serial number set by the CA to
166provide an abbreviated way to refer to certificates from that CA.
167If a CA does not wish to number its certificates it must set this
168field to zero.
170type specifies whether this certificate is for identification of a user
171or a host using a SSH_CERT_TYPE_... value.
173key id is a free-form text field that is filled in by the CA at the time
174of signing; the intention is that the contents of this field are used to
175identify the identity principal in log messages.
177"valid principals" is a string containing zero or more principals as
178strings packed inside it. These principals list the names for which this
179certificate is valid; hostnames for SSH_CERT_TYPE_HOST certificates and
180usernames for SSH_CERT_TYPE_USER certificates. As a special case, a
181zero-length "valid principals" field means the certificate is valid for
182any principal of the specified type.
184"valid after" and "valid before" specify a validity period for the
185certificate. Each represents a time in seconds since 1970-01-01
18600:00:00. A certificate is considered valid if:
188    valid after <= current time < valid before
190critical options is a set of zero or more key options encoded as
191below. All such options are "critical" in the sense that an implementation
192must refuse to authorise a key that has an unrecognised option.
194extensions is a set of zero or more optional extensions. These extensions
195are not critical, and an implementation that encounters one that it does
196not recognise may safely ignore it.
198Generally, critical options are used to control features that restrict
199access where extensions are used to enable features that grant access.
200This ensures that certificates containing unknown restrictions do not
201inadvertently grant access while allowing new protocol features to be
202enabled via extensions without breaking certificates' backwards
205The reserved field is currently unused and is ignored in this version of
206the protocol.
208The signature key field contains the CA key used to sign the
209certificate. The valid key types for CA keys are ssh-rsa,
210ssh-dss, ssh-ed25519 and the ECDSA types ecdsa-sha2-nistp256,
211ecdsa-sha2-nistp384, ecdsa-sha2-nistp521. "Chained" certificates, where
212the signature key type is a certificate type itself are NOT supported.
213Note that it is possible for a RSA certificate key to be signed by a
214Ed25519 or ECDSA CA key and vice-versa.
216signature is computed over all preceding fields from the initial string
217up to, and including the signature key. Signatures are computed and
218encoded according to the rules defined for the CA's public key algorithm
219(RFC4253 section 6.6 for ssh-rsa and ssh-dss, RFC5656 for the ECDSA
220types), and draft-josefsson-eddsa-ed25519-03 for Ed25519.
222Critical options
225The critical options section of the certificate specifies zero or more
226options on the certificates validity. The format of this field
227is a sequence of zero or more tuples:
229    string       name
230    string       data
232Options must be lexically ordered by "name" if they appear in the
233sequence. Each named option may only appear once in a certificate.
235The name field identifies the option and the data field encodes
236option-specific information (see below). All options are
237"critical", if an implementation does not recognise a option
238then the validating party should refuse to accept the certificate.
240Custom options should append the originating author or organisation's
241domain name to the option name, e.g. "my-option@example.com".
243No critical options are defined for host certificates at present. The
244supported user certificate options and the contents and structure of
245their data fields are:
247Name                    Format        Description
249force-command           string        Specifies a command that is executed
250                                      (replacing any the user specified on the
251                                      ssh command-line) whenever this key is
252                                      used for authentication.
254source-address          string        Comma-separated list of source addresses
255                                      from which this certificate is accepted
256                                      for authentication. Addresses are
257                                      specified in CIDR format (nn.nn.nn.nn/nn
258                                      or hhhh::hhhh/nn).
259                                      If this option is not present then
260                                      certificates may be presented from any
261                                      source address.
266The extensions section of the certificate specifies zero or more
267non-critical certificate extensions. The encoding and ordering of
268extensions in this field is identical to that of the critical options,
269as is the requirement that each name appear only once.
271If an implementation does not recognise an extension, then it should
272ignore it.
274Custom options should append the originating author or organisation's
275domain name to the option name, e.g. "my-option@example.com".
277No extensions are defined for host certificates at present. The
278supported user certificate extensions and the contents and structure of
279their data fields are:
281Name                    Format        Description
283permit-X11-forwarding   empty         Flag indicating that X11 forwarding
284                                      should be permitted. X11 forwarding will
285                                      be refused if this option is absent.
287permit-agent-forwarding empty         Flag indicating that agent forwarding
288                                      should be allowed. Agent forwarding
289                                      must not be permitted unless this
290                                      option is present.
292permit-port-forwarding  empty         Flag indicating that port-forwarding
293                                      should be allowed. If this option is
294                                      not present then no port forwarding will
295                                      be allowed.
297permit-pty              empty         Flag indicating that PTY allocation
298                                      should be permitted. In the absence of
299                                      this option PTY allocation will be
300                                      disabled.
302permit-user-rc          empty         Flag indicating that execution of
303                                      ~/.ssh/rc should be permitted. Execution
304                                      of this script will not be permitted if
305                                      this option is not present.
307$OpenBSD: PROTOCOL.certkeys,v 1.16 2018/10/26 01:23:03 djm Exp $