Viktor Szakats

~~Would it be feasible to upgrade to modern (SHA2) algo instead?~~

Would this also make sense for the `sshd_config` inside `Dockerfile`? We use Debian bullseye there, with OpenSSH 8.4, but the next release will have 9.2 or newer: https://packages.debian.org/bullseye/openssh-server https://packages.debian.org/testing/openssh-server ```diff...

As @willco007 said, if this is resolved by renaming a few internal symbols, I think we're ready to accept a PR for this.

This [commit](https://github.com/libssh2/libssh2/commit/03092292597ac601c3f9f0c267ecb145dda75e4e) landed "OpenSSH Key format reading support", released in libssh2 v1.9.0. We also have an OpenSSH RSA [key](https://github.com/libssh2/libssh2/blob/f2de2fda4e0cc314465ed00e59a541627f5d3ca4/tests/key_rsa_openssh) in our default test suite. According `ssh-keygen` man page, that format...

This PR addresses this issue: #789

This seems like an issue with autotools itself. Trying another build method (CMake, Makefile.mk) or using an updated autotools are possible solutions. Similar ones: #709 https://github.com/curl/curl/issues/10902

Thanks everyone and in particular @MichaelBuckley for the PR. It has now been merged in bc4e619e76071393e466c29220fc4ef5764c2820.

This seems like an issue with autotools itself. Trying another build method (CMake, Makefile.mk) or using an updated autotools are possible solutions. Similar ones: #641 https://github.com/curl/curl/issues/10902

This PR seems to contain past patches and no new commits. Looks accidental.

@hamletg Can you rebase this one for a fresh CI run? Some checksrc errors might need to be fixed after that.