Simon Tatham d663356634 Work around key algorithm naming change in OpenSSH <= 7.7. ...

When you send a "publickey" USERAUTH_REQUEST containing a certified
RSA key, and you want to use a SHA-2 based RSA algorithm, modern
OpenSSH expects you to send the algorithm string as
rsa-sha2-NNN-cert-v01@openssh.com. But 7.7 and earlier didn't
recognise those names, and expected the algorithm string in the
userauth request packet to be ssh-rsa-cert-v01@... and would then
follow it with an rsa-sha2-NNN signature.

OpenSSH itself has a bug workaround for its own older versions. Follow
suit.

2023-05-05 00:05:28 +01:00

..

agentf.c

…

bpp1.c

…

bpp2.c

…

bpp-bare.c

…

bpp.h

…

ca-config.c

…

censor1.c

…

censor2.c

…

channel.h

…

CMakeLists.txt

…

common.c

…

connection1-client.c

…

connection1-server.c

…

connection1.c

…

connection1.h

…

connection2-client.c

…

connection2-server.c

…

connection2.c

…

connection2.h

…

crc-attack-detector.c

…

gss.h

…

gssc.c

…

gssc.h

…

kex2-client.c

…

kex2-server.c

…

login1-server.c

…

login1.c

…

mainchan.c

…

nogss.c

…

nosharing.c

…

pgssapi.c

…

pgssapi.h

…

portfwd.c

…

ppl.h

…

scpserver.c

…

server.c

…

server.h

…

sesschan.c

…

sftp.c

…

sftp.h

…

sftpcommon.c

…

sftpserver.c

…

sharing.c

…

signal-list.h

…

ssh.c

…

transient-hostkey-cache.c

…

transport2.c

…

transport2.h

…

ttymode-list.h

…

userauth2-client.c

Work around key algorithm naming change in OpenSSH <= 7.7.

2023-05-05 00:05:28 +01:00

userauth2-server.c

…

verstring.c

Work around key algorithm naming change in OpenSSH <= 7.7.

2023-05-05 00:05:28 +01:00

x11fwd.c

…

zlib.c

…