Age | Commit message (Collapse) | Author |
|
|
|
ok markus@
|
|
|
|
default ports. bz3367 ok dtucker@
|
|
more: ask the token whether a particular key belongs to it in cases
where the token support on-token user- verification (e.g. biometrics)
rather than just assuming that it will accept it.
Will reduce spurious "Confirm user presence" notifications for key
handles that relate to FIDO keys that are not currently inserted in at
least some cases.
Motivated by bz3366; by Pedro Martelletto
|
|
|
|
|
|
unable to kill such a session. bz3360; ok dtucker@
|
|
"internal error"
|
|
at present, so don't say otherwise in SYNOPSIS; spotted jmc@
|
|
|
|
|
|
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@
|
|
|
|
|
|
for RSA keys). Avoids fatal errors for PKCS#11 libraries that return
empty keyid, e.g. Microchip ATECC608B "cryptoauthlib"; bz#3364
|
|
ca certs but not with simple key lifetimes within the allowed
signers file.
Since it returns the first keys principal it finds this could
result in a principal with an expired key even though a valid
one is just below.
patch from Fabian Stelzer; feedback/ok djm markus
|
|
|
|
|
|
ok deraadt millert
|
|
as half-close on the output side; ok deraadt millert
|
|
interferes with the new poll()-based listen loop; spotted and
debugged by anton@+deraadt@
|
|
with djm
|
|
|
|
ok djm
|
|
to make things easier.
back and forth and ok; djm
|
|
Discussed with mestre
|
|
|
|
select() code was using exceptfds incorrectly..
ok millert
|
|
Streamlined NTRU Prime post-quantum KEX to the default KEXAlgorithms
list (after the ECDH methods but before the prime-group DH ones).
ok markus@
|
|
feedback/ok markus@
|
|
user that doesn't exist; better matches what the shell does
ok deraadt@
|
|
PR#283, ok markus@
|
|
no code change
|
|
|
|
on the device itself, including biometric keys.
Query the token during key creation to determine whether it supports
on-token UV and, if so, clear the SSH_SK_USER_VERIFICATION_REQD flag
in the key so that ssh(1) doesn't automatically prompty for PIN later.
When making signatures with the key, query the token's capabilities
again and check whether the token is able (right now) to perform user-
verification without a PIN. If it is then the PIN prompt is bypassed
and user verification delegated to the token. If not (e.g. the token
is biometric capable, but no biometric are enrolled), then fall back
to user verification via the usual PIN prompt.
Work by Pedro Martelletto; ok myself and markus@
NB. cranks SSH_SK_VERSION_MAJOR
|
|
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
|
|
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which might lead future people
to copy this broken idiom, and perhaps even believe this parameter has some
meaning or implication or application. Delete them all.
This comes out of a conversation where tb@ noticed that a strange (but
intentional) pledge behaviour is to always knock-out high-bits from
mode_t on a number of system calls as a safety factor, and his bewilderment
that this appeared to be happening against valid modes (at least visually),
but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef.
ok millert
|
|
no addresses. ALso, remove an unneeded NULL check in addr_ntop.
From khaleesicodes via github PR#281, ok deraadt@
|
|
via github PR#280.
|
|
|
|
protocol for copying. Let's get back to testing the SFTP protocol.
|
|
can be used in a Match block. Patch from eehakkin via github PR#277.
|
|
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@
|
|
ok dtucker@
|
|
were processed. Useful to see whether a file or command actually has
keys present
|
|
Fixes error in portable where GCC>=11 takes notice of the bounds.
ok deraadt@
|
|
|
|
|