* bump platform toolset to v143
* add updated proj files for testing
* add _CRT_DECLARE_NONSTDC_NAMES=0 to projects with posix functions
* revert onecore changes
* fix typo
* use latest sdk in build script
* update build toolset in config proj
* update build script to use latest toolsets
* update paths.targets
* update to win11 sdk in paths.targets
* make build script more robust with VSwhere
* change validity check from count check to null-check
* remove static keyword from auth_debug declaration
* change to ifndef for diff checking
* update string compare
* change msbuild tool search from manual check instead of using vswhere
* update wixproj to work with wix install on new build image
* update 2022 build image and zlib version
multiplexed sessions to ignore SIGINT under some circumstances. Reported by /
feedback naddy@, ok dtucker@
OpenBSD-Commit-ID: 4d5c6c894664f50149153fd4764f21f43e7d7e5a
connections. If the multiplex socket exists but the connection times out,
ssh will fall back to a direct connection the same way it would if the socket
did not exist at all. ok djm@
OpenBSD-Commit-ID: 2fbe1a36d4a24b98531b2d298a6557c8285dc1b4
When sshd is built with an OpenSSL that does not self-seed, it would
fail in the preauth privsep process while handling a new connection.
Sanity checked by djm@
a specific point. e.g. "make LTESTS_FROM=t-sftp" will only run the sftp.sh
test and subsequent ones. ok dtucker@
OpenBSD-Regress-ID: 07f653de731def074b29293db946042706fcead3
AuthorizedKeysCommand accept the %D (routing domain) and a new %C (connection
address/port 4-tuple) as expansion sequences; ok markus
OpenBSD-Commit-ID: ee9a48bf1a74c4ace71b69de69cfdaa2a7388565
Previously sk-dummy.so used libc's (or compat's) SHA256 since it may be
built without OpenSSL. In many cases, however, including both libc's
and OpenSSL's headers together caused conflicting definitions.
We tried working around this (on OpenSSL <1.1 you could define
OPENSSL_NO_SHA, NetBSD had USE_LIBC_SHA2, various #define hacks) with
varying levels of success. Since OpenSSL >=1.1 removed OPENSSL_NO_SHA
and including most OpenSSL headers would bring sha.h in, even if it
wasn't used directly this was a constant hassle.
Admit defeat and use OpenSSL's SHA256 unless we aren't using OpenSSL at
all. ok djm@
multiplexed cases (inc. ControlPersist). bz3589 bz3589 Based on patches by
Peter Chubb; ok dtucker@
OpenBSD-Commit-ID: a7a2976a54b93e6767dc846b85647e6ec26969ac
Tess Gauthier
Sam Hocevar
s911415
tgauth@bu.edu
Darren Tucker
djm@openbsd.org
Damien Miller
dtucker@openbsd.org
jmc@openbsd.org
naddy@openbsd.org