![[BACK]](/icons/back.gif){kind=icon}
Up to [local] / src / usr.bin / ssh
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.19 / (download) - annotate - [select for diffs], Sat Jun 5 13:47:00 2021 UTC (2 years, 10 months ago) by naddy
Branch: MAIN
CVS Tags: OPENBSD_7_5_BASE,
OPENBSD_7_5,
OPENBSD_7_4_BASE,
OPENBSD_7_4,
OPENBSD_7_3_BASE,
OPENBSD_7_3,
OPENBSD_7_2_BASE,
OPENBSD_7_2,
OPENBSD_7_1_BASE,
OPENBSD_7_1,
OPENBSD_7_0_BASE,
OPENBSD_7_0,
HEAD
Changes since 1.18: +11 -12 lines
Diff to previous 1.18 (colored)
PROTOCOL.certkeys: update reference from IETF draft to RFC Also fix some typos. ok djm@
Revision 1.18 / (download) - annotate - [select for diffs], Fri Jun 4 04:02:21 2021 UTC (2 years, 10 months ago) by djm
Branch: MAIN
Changes since 1.17: +13 -5 lines
Diff to previous 1.17 (colored)
correct extension name "no-presence-required" => "no-touch-required" document "verify-required" option
Revision 1.17 / (download) - annotate - [select for diffs], Mon Nov 25 00:57:51 2019 UTC (4 years, 4 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_6_9_BASE,
OPENBSD_6_9,
OPENBSD_6_8_BASE,
OPENBSD_6_8,
OPENBSD_6_7_BASE,
OPENBSD_6_7
Changes since 1.16: +8 -1 lines
Diff to previous 1.16 (colored)
document the "no-touch-required" certificate extension; ok markus, feedback deraadt
Revision 1.16 / (download) - annotate - [select for diffs], Fri Oct 26 01:23:03 2018 UTC (5 years, 5 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_6_6_BASE,
OPENBSD_6_6,
OPENBSD_6_5_BASE,
OPENBSD_6_5
Changes since 1.15: +2 -1 lines
Diff to previous 1.15 (colored)
mention ssh-ed25519-cert-v01@openssh.com in list of cert key type at start of doc
Revision 1.15 / (download) - annotate - [select for diffs], Tue Jul 3 11:39:54 2018 UTC (5 years, 9 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_6_4_BASE,
OPENBSD_6_4
Changes since 1.14: +16 -4 lines
Diff to previous 1.14 (colored)
Improve strictness and control over RSA-SHA2 signature types: In ssh, when an agent fails to return a RSA-SHA2 signature when requested and falls back to RSA-SHA1 instead, retry the signature to ensure that the public key algorithm sent in the SSH_MSG_USERAUTH matches the one in the signature itself. In sshd, strictly enforce that the public key algorithm sent in the SSH_MSG_USERAUTH message matches what appears in the signature. Make the sshd_config PubkeyAcceptedKeyTypes and HostbasedAcceptedKeyTypes options control accepted signature algorithms (previously they selected supported key types). This allows these options to ban RSA-SHA1 in favour of RSA-SHA2. Add new signature algorithms "rsa-sha2-256-cert-v01@openssh.com" and "rsa-sha2-512-cert-v01@openssh.com" to force use of RSA-SHA2 signatures with certificate keys. feedback and ok markus@
Revision 1.14 / (download) - annotate - [select for diffs], Tue Apr 10 00:10:49 2018 UTC (6 years ago) by djm
Branch: MAIN
Changes since 1.13: +2 -2 lines
Diff to previous 1.13 (colored)
lots of typos in comments/docs. Patch from Karsten Weiss after checking with codespell tool (https://github.com/lucasdemarchi/codespell)
Revision 1.13 / (download) - annotate - [select for diffs], Fri Nov 3 02:32:19 2017 UTC (6 years, 5 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_6_3_BASE,
OPENBSD_6_3
Changes since 1.12: +4 -4 lines
Diff to previous 1.12 (colored)
typos in ECDSA certificate names; bz#2787 reported by Mike Gerow
Revision 1.12 / (download) - annotate - [select for diffs], Wed May 31 04:29:44 2017 UTC (6 years, 10 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_6_2_BASE,
OPENBSD_6_2
Changes since 1.11: +7 -1 lines
Diff to previous 1.11 (colored)
spell out that custom options/extensions should follow the usual SSH naming rules, e.g. "extension@example.com"
Revision 1.11 / (download) - annotate - [select for diffs], Tue May 16 16:54:05 2017 UTC (6 years, 11 months ago) by djm
Branch: MAIN
Changes since 1.10: +8 -7 lines
Diff to previous 1.10 (colored)
mention that Ed25519 keys are valid as CA keys; spotted by Jakub Jelen
Revision 1.10 / (download) - annotate - [select for diffs], Tue May 3 10:27:59 2016 UTC (7 years, 11 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_6_1_BASE,
OPENBSD_6_1,
OPENBSD_6_0_BASE,
OPENBSD_6_0
Changes since 1.9: +32 -10 lines
Diff to previous 1.9 (colored)
correct some typos and remove a long-stale XXX note. add specification for ed25519 certificates mention no host certificate options/extensions are currently defined pointed out by Simon Tatham
Revision 1.9 / (download) - annotate - [select for diffs], Wed Mar 28 07:23:22 2012 UTC (12 years ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_5_9_BASE,
OPENBSD_5_9,
OPENBSD_5_8_BASE,
OPENBSD_5_8,
OPENBSD_5_7_BASE,
OPENBSD_5_7,
OPENBSD_5_6_BASE,
OPENBSD_5_6,
OPENBSD_5_5_BASE,
OPENBSD_5_5,
OPENBSD_5_4_BASE,
OPENBSD_5_4,
OPENBSD_5_3_BASE,
OPENBSD_5_3,
OPENBSD_5_2_BASE,
OPENBSD_5_2
Changes since 1.8: +12 -3 lines
Diff to previous 1.8 (colored)
explain certificate extensions/crit split rationale. Mention requirement that each appear at most once per cert.
Revision 1.8 / (download) - annotate - [select for diffs], Tue Aug 31 11:54:45 2010 UTC (13 years, 7 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_5_1_BASE,
OPENBSD_5_1,
OPENBSD_5_0_BASE,
OPENBSD_5_0,
OPENBSD_4_9_BASE,
OPENBSD_4_9
Changes since 1.7: +61 -30 lines
Diff to previous 1.7 (colored)
Implement Elliptic Curve Cryptography modes for key exchange (ECDH) and host/user keys (ECDSA) as specified by RFC5656. ECDH and ECDSA offer better performance than plain DH and DSA at the same equivalent symmetric key length, as well as much shorter keys. Only the mandatory sections of RFC5656 are implemented, specifically the three REQUIRED curves nistp256, nistp384 and nistp521 and only ECDH and ECDSA. Point compression (optional in RFC5656 is NOT implemented). Certificate host and user keys using the new ECDSA key types are supported. Note that this code has not been tested for interoperability and may be subject to change. feedback and ok markus@
Revision 1.7 / (download) - annotate - [select for diffs], Wed Aug 4 05:40:39 2010 UTC (13 years, 8 months ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_4_8_BASE,
OPENBSD_4_8
Changes since 1.6: +8 -4 lines
Diff to previous 1.6 (colored)
tighten the rules for certificate encoding by requiring that options appear in lexical order and make our ssh-keygen comply. ok markus@
Revision 1.6 / (download) - annotate - [select for diffs], Thu May 20 23:46:02 2010 UTC (13 years, 11 months ago) by djm
Branch: MAIN
Changes since 1.5: +24 -11 lines
Diff to previous 1.5 (colored)
Move the permit-* options to the non-critical "extensions" field for v01 certificates. The logic is that if another implementation fails to implement them then the connection just loses features rather than fails outright. ok markus@
Revision 1.5 / (download) - annotate - [select for diffs], Sat May 1 02:50:50 2010 UTC (13 years, 11 months ago) by djm
Branch: MAIN
Changes since 1.4: +2 -2 lines
Diff to previous 1.4 (colored)
typo; jmeltzer@
Revision 1.4 / (download) - annotate - [select for diffs], Fri Apr 16 01:47:25 2010 UTC (14 years ago) by djm
Branch: MAIN
Changes since 1.3: +45 -30 lines
Diff to previous 1.3 (colored)
revised certificate format ssh-{dss,rsa}-cert-v01@openssh.com with the
following changes:
move the nonce field to the beginning of the certificate where it can
better protect against chosen-prefix attacks on the signature hash
Rename "constraints" field to "critical options"
Add a new non-critical "extensions" field
Add a serial number
The older format is still support for authentication and cert generation
(use "ssh-keygen -t v00 -s ca_key ..." to generate a v00 certificate)
ok markus@
Revision 1.3 / (download) - annotate - [select for diffs], Wed Mar 3 22:50:40 2010 UTC (14 years, 1 month ago) by djm
Branch: MAIN
CVS Tags: OPENBSD_4_7_BASE,
OPENBSD_4_7
Changes since 1.2: +2 -2 lines
Diff to previous 1.2 (colored)
s/similar same/similar/; from imorgan AT nas.nasa.gov
Revision 1.2 / (download) - annotate - [select for diffs], Tue Mar 2 23:22:44 2010 UTC (14 years, 1 month ago) by djm
Branch: MAIN
Changes since 1.1: +2 -0 lines
Diff to previous 1.1 (colored)
Add RCS Ident
Revision 1.1 / (download) - annotate - [select for diffs], Fri Feb 26 20:29:54 2010 UTC (14 years, 1 month ago) by djm
Branch: MAIN
Add support for certificate key types for users and hosts. OpenSSH certificate key types are not X.509 certificates, but a much simpler format that encodes a public key, identity information and some validity constraints and signs it with a CA key. CA keys are regular SSH keys. This certificate style avoids the attack surface of X.509 certificates and is very easy to deploy. Certified host keys allow automatic acceptance of new host keys when a CA certificate is marked as trusted in ~/.ssh/known_hosts. see VERIFYING HOST KEYS in ssh(1) for details. Certified user keys allow authentication of users when the signing CA key is marked as trusted in authorized_keys. See "AUTHORIZED_KEYS FILE FORMAT" in sshd(8) for details. Certificates are minted using ssh-keygen(1), documentation is in the "CERTIFICATES" section of that manpage. Documentation on the format of certificates is in the file PROTOCOL.certkeys feedback and ok markus@