Server doesn't accept RSA SHA-2 keys. #77
Labels
bug
Something isn't working
Comments
|
This is mentioned in the Readme, you should use the command Alternatively, you can log to the port 443 which doesn't require a public key. |
I already have a public key though. Am I missing something? |
|
Found a hacker news post which I think is relevant. It just doesn't like RSA. https://news.ycombinator.com/item?id=30690988 |
|
Yeah this is a known issue with some crypto libs: see golang/crypto#197, gliderlabs/ssh#145 & charmbracelet/soft-serve#48 |
|
This problem hasn't been solved, reopening. |
quackduck
changed the title
|
Not sure if this is a related error, but I've also been unable to log on to the server, although only recently, as of the beginning of this week. My error is |
|
Did you get the same error as @thepixelmonk before this week? I wonder if simply changing the server’s ssh key would fix this. |
|
@quackduck I got no errors before this week. |
|
changing the server key will have all old user clients complaining about a possible man in the middle attack lol I could try and set up another instance with a new host key... |
|
@quackduck If no one can reproduce the issue, it's probably not worth it, I don't want to cause all those issues just because I maybe have something on my end. |
|
No this is a legitimate issue a lot of people face: I have to tell them to use port 443. We're mostly waiting on the libs here to add support: #77 (comment) |
|
For the record, I fixed it by restarting. The RSA SHA-2 issue is unrelated. |
|
Hey @thepixelmonk could you run |
|
|
For comparison, this is mine: |
|
After updating openssh I get the same issue: |
|
We could solve this by using a third-party fork of https://github.com/replicatedhq/kots/pull/2613/files |
|
Okay here's a tracking issue for this problem: golang/go#49952 |
|
I updated some dependencies and the verbose messages have now changed. It appears it goes a bit further this time: Diff: 29,31c29,66
< debug1: kex: algorithm: [email protected]
< debug1: kex: host key algorithm: (no match)
< Unable to negotiate with 150.136.142.44 port 22: no matching host key type found. Their offer: ssh-rsa
---
> debug1: kex: algorithm: curve25519-sha256
> debug1: kex: host key algorithm: rsa-sha2-512
> debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
> debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
> debug1: SSH2_MSG_KEX_ECDH_REPLY received
> debug1: Server host key: ssh-rsa SHA256:0NFbqn9ACSQBVVjvqcVsGl0vtVUq9n//nJgEwB25UFk
> debug1: load_hostkeys: fopen /Users/ishan/.ssh/known_hosts2: No such file or directory
> debug1: load_hostkeys: fopen /opt/homebrew/etc/ssh/ssh_known_hosts: No such file or directory
> debug1: load_hostkeys: fopen /opt/homebrew/etc/ssh/ssh_known_hosts2: No such file or directory
> debug1: Host 'devzat.hackclub.com' is known and matches the RSA host key.
> debug1: Found key in /Users/ishan/.ssh/known_hosts:1
> debug1: rekey out after 134217728 blocks
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SSH2_MSG_NEWKEYS received
> debug1: rekey in after 134217728 blocks
> debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities
> debug1: Will attempt key: /Users/ishan/.ssh/id_rsa RSA SHA256:/30Vhs3sufvZ/NTJVIUiSTwpFyvDEh10bIOyiZO9cj4
> debug1: Will attempt key: /Users/ishan/.ssh/id_ecdsa
> debug1: Will attempt key: /Users/ishan/.ssh/id_ecdsa_sk
> debug1: Will attempt key: /Users/ishan/.ssh/id_ed25519
> debug1: Will attempt key: /Users/ishan/.ssh/id_ed25519_sk
> debug1: Will attempt key: /Users/ishan/.ssh/id_xmss
> debug1: Will attempt key: /Users/ishan/.ssh/id_dsa
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentications that can continue: publickey
> debug1: Next authentication method: publickey
> debug1: Offering public key: /Users/ishan/.ssh/id_rsa RSA SHA256:/30Vhs3sufvZ/NTJVIUiSTwpFyvDEh10bIOyiZO9cj4
> debug1: send_pubkey_test: no mutual signature algorithm
> debug1: Trying private key: /Users/ishan/.ssh/id_ecdsa
> debug1: Trying private key: /Users/ishan/.ssh/id_ecdsa_sk
> debug1: Trying private key: /Users/ishan/.ssh/id_ed25519
> debug1: Trying private key: /Users/ishan/.ssh/id_ed25519_sk
> debug1: Trying private key: /Users/ishan/.ssh/id_xmss
> debug1: Trying private key: /Users/ishan/.ssh/id_dsa
> debug1: No more authentication methods to try.
> [email protected]: Permission denied (publickey).This looks like a result of golang/crypto@3147a52 |
|
Fixed in 486eb4e by switching to a fork of https://github.com/golang/crypto: https://github.com/cli/crypto 🎉 |
|
Okay nvm that was a bit premature; I tested the fix wrong. |
|
OKAY ACTUALLY FIXED NOW IN 93dfd63 🎉 |
|
Yay! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm getting a permission denied error even though I have a public key generated. Any ideas?
The text was updated successfully, but these errors were encountered: