Age | Commit message (Collapse) | Author |
|
characters; GHPR236 bz3385, fix from Dmitry Belyavskiy
|
|
based on GHPR393
|
|
the user know what's going on when ssh-keygen is invoked via other
tools. Requested in GHPR503
|
|
"rsa") in user-interface code and require full SSH protocol names (e.g.
"ssh-rsa") everywhere else.
Prompted by bz3725; ok markus@
|
|
unconverted as it will be removed within six months.
Based on patches originally from Dmitry Belyavskiy, but significantly
reworked based on feedback from Bob Beck, Joel Sing and especially
Theo Buehler (apologies to anyone I've missed).
ok tb@
|
|
ok markus@
|
|
Ed25519 public keys are very convenient due to their small size.
OpenSSH has supported Ed25519 since version 6.5 (January 2014).
OK djm@ markus@ sthen@ deraadt@
|
|
When the KRL format was originally defined, it included support for
signing of KRL objects. However, the code to sign KRLs and verify KRL
signatues was never completed in OpenSSH.
Now, some years later, we have SSHSIG support in ssh-keygen that is
more general, well tested and actually works. So this removes the
semi-finished KRL signing/verification support from OpenSSH and
refactors the remaining code to realise the benefit - primarily, we
no longer need to perform multiple parsing passes over KRL objects.
ok markus@
|
|
reported by Yair Mizrahi @ JFrog; feedback/ok millert@
|
|
not showing on when running `ssh-keygen -l` on multiple keys where one
has a comment and other following keys do not. Patch from Markus Kuhn
via GHPR407, bz3580
|
|
ok dtucker@
|
|
based on fix in bz3546 by Dmitry Belyavskiy; with/ok dtucker
|
|
If multiple -Ocheckpoint= options are passed, the earlier ones would
be overwritten and leaked. If we use an input file that wasn't stdin,
close that. From Coverity CIDs 291884 and 291894.
|
|
From Coverity CID 291894.
|
|
prevent warning.
|
|
outputting SSHFP fingerprints to allow algorithm selection.
bz3493 ok dtucker@
|
|
getopt(3) returns '?' when it encounters a flag not present in the in
the optstring or if a flag is missing its option argument. We can
handle this case with the "default" failure case with no loss of
legibility. Hence, remove all the redundant "case '?':" lines.
Prompted by dlg@. With help from dlg@ and millert@.
Link: https://marc.info/?l=openbsd-tech&m=167011979726449&w=2
ok naddy@ millert@ dlg@
|
|
start time began with "0x", not the expiry time.
from Ed Maste
|
|
authorized_keys expiry-time options to accept dates in the UTC time
zone in addition to the default of interpreting them in the system
time zone. YYYYMMDD and YYMMDDHHMM[SS] dates/times will be
interpreted as UTC if suffixed with a 'Z' character.
Also allow certificate validity intervals to be specified in raw
seconds-since-epoch as hex value, e.g. -V 0x1234:0x4567890. This
is intended for use by regress tests and other tools that call
ssh-keygen as part of a CA workflow.
bz3468 ok dtucker
|
|
credential, just let the enroll operating fail and we'll attempt
to get a PIN anyway. Might avoid some unneccessary PIN prompts.
Part of GHPR#302 from Corinna Vinschen; ok dtucker@
|
|
part of GHPR329 from Pedro Martelletto
|
|
credential with matching application and user ID strings already
exists. if so, prompt the user for confirmation before overwriting
the credential.
patch from Pedro Martelletto via GHPR329
NB. cranks SSH_SK_VERSION_MAJOR, so any third-party FIDO middleware
implementations will need to adjust
|
|
so it can be used for FIDO2 PINs; no functional change
|
|
from jsegitz with man page text from jmc@, ok markus@ djm@
|
|
This was already documented when support for user-verified FIDO
keys was added, but the ssh-keygen(1) code was missing.
ok djm@
|
|
where it will be interpreted to require that the private keys is
hosted in an agent; bz3429, suggested by Adam Szkoda; ok dtucker@
|
|
private key; bz3429, reported by Adam Szkoda ok dtucker@
|
|
|
|
Patch from Mateusz Adamowski via GHPR#307
|
|
static const char *array => static const char * const array
from Mike Frysinger
|
|
|
|
|
|
either sha512 (default) or sha256, but plumbing wasn't there
mostly by Linus Nordberg
|
|
from Linus Nordberg
|
|
|
|
|
|
principals names against an allowed signers file.
Requested by and mostly written by Fabian Stelzer, towards a TOFU
model for SSH signatures in git. Some tweaks by me.
"doesn't bother me" deraadt@
|
|
From Fabian Stelzer
|
|
user ID that was used when the key was created and append it to
the filename the key is written to (if it is not the default).
Avoids keys being clobbered if the user created multiple
resident keys with the same application string but different
user IDs.
feedback Pedro Martelletto; ok markus
NB. increments SSH_SK_VERSION_MAJOR
|
|
Saves 1k of static storage and prevents snprintf "possible truncation"
warnings from newer compilers (although in this case it's false positive
since the actual sizes are limited by the output size of the SHA1).
ok djm@
|
|
|
|
Carlo Marcelo Arenas Belón
|
|
to dump the full public key to stdout; based on patch from Fabian
Stelzer; ok markus@
|
|
actually available, albeit only for ed25519 keys.
|
|
since those are not available, similar to what we currently do with
the moduli screening options. We can also use this to skip the
conversion regression tests in this case.
|
|
lifetimes, and allow the verification mode to specify a signature time
to check at. This is intended for use by git to support signing
objects using ssh keys. ok dtucker@
|
|
|
|
removes a handful of diffs between the two.
|
|
indentation on continuation lines. Prompted by GHPR#185
|
|
library calls; bz3273 ok dtucker@
|