openssh - openssh

	Commit message (Collapse)	Author	Age	Files	Lines
*	upstream: Replace all calls to signal(2) with a wrapper around	dtucker@openbsd.org	2020-01-23	1	-4/+5
\| \| \| \| \| \| \| \|	sigaction(2). This wrapper blocks all other signals during the handler preventing races between handlers, and sets SA_RESTART which should reduce the potential for short read/write operations. OpenBSD-Commit-ID: 5e047663fd77a40d7b07bdabe68529df51fd2519
*	upstream: check access(ssh-sk-helper, X_OK) to provide friendly	djm@openbsd.org	2020-01-21	1	-1/+9
\| \| \| \| \| \|	error message for misconfigured helper paths OpenBSD-Commit-ID: 061bcc262155d12e726305c91394ac0aaf1f8341
*	upstream: pass the log-on-stderr flag and log level through to	djm@openbsd.org	2020-01-21	1	-17/+23
\| \| \| \| \| \|	ssh-sk-helper, making debugging a bit easier. ok markus@ OpenBSD-Commit-ID: 2e7aea6bf5770d3f38b7c7bba891069256c5a49a
*	upstream: Extends the SK API to accept a set of key/value options	djm@openbsd.org	2020-01-06	1	-5/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	for all operations. These are intended to future-proof the API a little by making it easier to specify additional fields for without having to change the API version for each. At present, only two options are defined: one to explicitly specify the device for an operation (rather than accepting the middleware's autoselection) and another to specify the FIDO2 username that may be used when generating a resident key. These new options may be invoked at key generation time via ssh-keygen -O This also implements a suggestion from Markus to avoid "int" in favour of uint32_t for the algorithm argument in the API, to make implementation of ssh-sk-client/helper a little easier. feedback, fixes and ok markus@ OpenBSD-Commit-ID: 973ce11704609022ab36abbdeb6bc23c8001eabc
*	upstream: SK API and sk-helper error/PIN passing	djm@openbsd.org	2019-12-30	1	-10/+37
\| \| \| \| \| \| \| \| \| \| \| \| \|	Allow passing a PIN via the SK API (API major crank) and let the ssh-sk-helper API follow. Also enhance the ssh-sk-helper API to support passing back an error code instead of a complete reply. Will be used to signal "wrong PIN", etc. feedback and ok markus@ OpenBSD-Commit-ID: a1bd6b0a2421646919a0c139b8183ad76d28fb71
*	upstream: implement loading of resident keys in ssh-sk-helper	djm@openbsd.org	2019-12-30	1	-1/+71
\| \| \| \| \| \|	feedback and ok markus@ OpenBSD-Commit-ID: b273c23769ea182c55c4a7b8f9cbd9181722011a
*	remove a bunch of ENABLE_SK #ifdefs	Damien Miller	2019-12-13	1	-0/+8
\| \| \| \| \| \| \| \| \| \| \|	The ssh-sk-helper client API gives us a nice place to disable security key support when it is wasn't enabled at compile time, so we don't need to check everywere. Also, verification of security key signatures can remain enabled all the time - it has no additional dependencies. So sshd can accept security key pubkeys in authorized_keys, etc regardless of the host's support for dlopen, etc.
*	ssh-sk-client.c needs includes.h	Damien Miller	2019-12-13	1	-0/+2
\|
*	upstream: actually commit the ssh-sk-helper client code; ok markus	djm@openbsd.org	2019-12-13	1	-0/+323
	OpenBSD-Commit-ID: fd2ea776a5bbbf4d452989d3c3054cf25a5e0589