Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to OpenSSH w/ OpenSSL-1.1.1d: Unknown key type rsa-sha2-512 #17

Closed
mgorny opened this issue Sep 19, 2019 · 5 comments
Closed
Labels
bug Something isn't working

Comments

@mgorny
Copy link

mgorny commented Sep 19, 2019

Bug description

Upon attempting to connect to my home computer, I get the following error:

Key exchange was not finished, connection is closed.
The server hostkey was not accepted by the verifier callback.
Unknown key type rsa-sha2-512

Steps to reproduce

I have just added the host and choose the connect. I'm sorry but the machine's on local network without public IP address or full-time connectivity.

Expected behavior

I expected it to connect just fine ;-).

Android device

  • Device: Motorola MotoG6
  • OS: Android 9 PPSS29.55-37-4-3
  • TermBot Version: 1.9.5-77-08fcc7c-termbot

Server information

  • OS: Gentoo Linux
  • SSH Software and Version: OpenSSH_8.0p1-sctp-1.2, OpenSSL 1.1.1d 10 Sep 2019
  • Pubkeys used (if applicable): apparently it uses RSA server key, it didn't get to client key

Additional context

Downgrading OpenSSL to 1.1.1c resolves the problem.

@mgorny mgorny added the bug Something isn't working label Sep 19, 2019
@mgorny mgorny changed the title Connecting to OpenSSH-8.0: Unknown key type rsa-sha2-512 Connecting to OpenSSH w/ OpenSSL-1.1.1d: Unknown key type rsa-sha2-512 Sep 19, 2019
@mgorny
Copy link
Author

mgorny commented Sep 19, 2019

Reported on Gentoo end, in case it was bug in OpenSSL: https://bugs.gentoo.org/694984

@antonpiatek
Copy link

I get the same issue - using instructions from https://bugs.gentoo.org/694984 to block 4x rsa2 algorithms allows it to work HostKeyAlgorithms -rsa-sha2-256-cert-v01@openssh.com,rsa-sha2-256,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-512 but as mentioned in the gentoo bug it should not be required for the server not to advertise a supported algorithm, the client should simply ignore ones it does not want to use

@hagau
Copy link

hagau commented Jan 27, 2020

This is fixed in connectbot/sshlib@e6a49c5. Unfortunately, that commit has not made it into a release of sshlib yet.

@nmz787
Copy link

nmz787 commented Apr 5, 2020

I switched to termbot and it works out of the box.

@dschuermann
Copy link
Member

AFAIK this should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants