summaryrefslogtreecommitdiff
path: root/sshsig.c
Commit message (Collapse)AuthorAgeFilesLines
* upstream: use the new variant log macros instead of prependingdjm@openbsd.org2020-10-181-59/+55
| | | | | | __func__ and appending ssh_err(r) manually; ok markus@ OpenBSD-Commit-ID: 1f14b80bcfa85414b2a1a6ff714fb5362687ace8
* upstream: Add RCS IDs to the few files that are missing them; fromdjm@openbsd.org2020-08-311-0/+1
| | | | | | Pedro Martelletto OpenBSD-Commit-ID: 39aa37a43d0c75ec87f1659f573d3b5867e4a3b3
* upstream: support for user-verified FIDO keysdjm@openbsd.org2020-08-271-7/+9
| | | | | | | | | | | | | | | | | FIDO2 supports a notion of "user verification" where the user is required to demonstrate their identity to the token before particular operations (e.g. signing). Typically this is done by authenticating themselves using a PIN that has been set on the token. This adds support for generating and using user verified keys where the verification happens via PIN (other options might be added in the future, but none are in common use now). Practically, this adds another key generation option "verify-required" that yields a key that requires a PIN before each authentication. feedback markus@ and Pedro Martelletto; ok markus@ OpenBSD-Commit-ID: 57fd461e4366f87c47502c5614ec08573e6d6a15
* upstream: do not leak oprincipals; ok djmmarkus@openbsd.org2020-03-131-2/+4
| | | | OpenBSD-Commit-ID: 4691d9387eab36f8fda48f5d8009756ed13a7c4c
* upstream: correct return code; ok djmmarkus@openbsd.org2020-03-131-1/+1
| | | | OpenBSD-Commit-ID: 319d09e3b7f4b2bc920c67244d9ff6426b744810
* upstream: principalsp is optional, pubkey required; ok djmmarkus@openbsd.org2020-03-131-3/+3
| | | | OpenBSD-Commit-ID: 2cc3ea5018c28ed97edaccd7f17d2cc796f01024
* upstream: sshsig: return correct error, fix null-deref; ok djmmarkus@openbsd.org2020-03-131-5/+7
| | | | OpenBSD-Commit-ID: 1d1af7cd538b8b23e621cf7ab84f11e7a923edcd
* upstream: ssh-keygen -Y find-principals fixes based on feedbackdjm@openbsd.org2020-01-251-11/+63
| | | | | | | | | | | | | | | | from Markus: use "principals" instead of principal, as allowed_signers lines may list multiple. When the signing key is a certificate, emit only principals that match the certificate principal list. NB. the command -Y name changes: "find-principal" => "find-principals" ok markus@ OpenBSD-Commit-ID: ab575946ff9a55624cd4e811bfd338bf3b1d0faf
* upstream: add a new signature operations "find-principal" to lookdjm@openbsd.org2020-01-231-0/+117
| | | | | | | up the principal associated with a signature from an allowed-signers file. Work by Sebastian Kinne; ok dtucker@ OpenBSD-Commit-ID: 6f782cc7e18e38fcfafa62af53246a1dcfe74e5d
* upstream: factor out parsing of allowed-signers linesdjm@openbsd.org2020-01-221-27/+87
| | | | OpenBSD-Commit-ID: 85ee6aeff608371826019ea85e55bfa87f79d06e
* upstream: Add new structure for signature optionsdjm@openbsd.org2019-11-251-8/+14
| | | | | | | | | | | This is populated during signature verification with additional fields that are present in and covered by the signature. At the moment, it is only used to record security key-specific options, especially the flags field. with and ok markus@ OpenBSD-Commit-ID: 338a1f0e04904008836130bedb9ece4faafd4e49
* upstream: Refactor signing - use sshkey_sign for everything,djm@openbsd.org2019-11-011-10/+11
| | | | | | | | | | | | | including the new U2F signatures. Don't use sshsk_ecdsa_sign() directly, instead make it reachable via sshkey_sign() like all other signature operations. This means that we need to add a provider argument to sshkey_sign(), so most of this change is mechanically adding that. Suggested by / ok markus@ OpenBSD-Commit-ID: d5193a03fcfa895085d91b2b83d984a9fde76c8c
* upstream: make signature format match PROTOCOdjm@openbsd.org2019-10-021-2/+2
| | | | | | | | | | =?UTF-8?q?=20as=20a=20string,=20not=20raw=20bytes.=20Spotted=20by=20Manta?= =?UTF-8?q?s=20Mikul=C4=97nas?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit OpenBSD-Commit-ID: 80fcc6d52893f80c6de2bedd65353cebfebcfa8f
* upstream: memleak on error path; found by libfuzzerdjm@openbsd.org2019-09-051-1/+1
| | | | OpenBSD-Commit-ID: 34d44cb0fb5bdb5fcbc6b02b804e71b20a7a5fc7
* upstream: expose allowed_signers options parsing code in header fordjm@openbsd.org2019-09-051-9/+9
| | | | | | | | | fuzzing rename to make more consistent with philosophically-similar auth options parsing API. OpenBSD-Commit-ID: 0c67600ef04187f98e2912ca57b60c22a8025b7c
* upstream: repair typo and editing mishapnaddy@openbsd.org2019-09-051-1/+1
| | | | OpenBSD-Commit-ID: d125ab720ca71ccf9baf83e08ddc8c12a328597e
* portability fixes for sshsigDamien Miller2019-09-031-0/+2
|
* upstream: sshsig tweaks and improvements from and suggested bydjm@openbsd.org2019-09-031-84/+96
| | | | | | | | Markus ok markus/me OpenBSD-Commit-ID: ea4f46ad5a16b27af96e08c4877423918c4253e9
* upstream: sshsig: lightweight signature and verification abilitydjm@openbsd.org2019-09-031-0/+787
for OpenSSH This adds a simple manual signature scheme to OpenSSH. Signatures can be made and verified using ssh-keygen -Y sign|verify Signatures embed the key used to make them. At verification time, this is matched via principal name against an authorized_keys-like list of allowed signers. Mostly by Sebastian Kinne w/ some tweaks by me ok markus@ OpenBSD-Commit-ID: 2ab568e7114c933346616392579d72be65a4b8fb
View Lorry Controller Status