-
Notifications
You must be signed in to change notification settings - Fork 141
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
Unable to login with my rsa key #48
Comments
Hi, thanks for reporting this. That's definitely odd. Can you try the latest version and see if you're still having the issue? |
I tried on the last version (0.1.3) and I have the same results, unable to use the RSA key because there is no mutual signature algorithm. |
Can confirm I'm having this issue too! Same error and everything. I detailed it in my issue thread here, I can provide any info that's needed! |
seems to be gliderlabs/ssh#145 which in turn is a issue with x/crypto/ssh, which is fixed golang/go#37278 seems like gliderlabs/ssh needs a dep update gliderlabs/ssh#165 -> gliderlabs/ssh#166 EDIT: there are still x/crypto/ssh changes pending merge golang/crypto#197 |
Switching from x/crypto to rmohr/crypto would add both client and server support and fix this issue. The problem I see is that we would then be using a slightly out of date fork not officially maintained by the Go project. |
Any update on this? It'd also be nice if the interface said to |
golang/crypto#197 is still unmerged... |
I configured my soft-serve server to only accept public key authentication. I am currently on the commit e8b5146.
For some strange reason, on one of my computer, the RSA key is not accepted by the server. When I run
ssh -v
I got the following output:On one of my other computer, the RSA key is accepted with no trouble:
This is not a very problematic issue as I could solve it by using an ed25519 key instead of the ssh one but this is still very intriguing.
I do not know if that matter but the computer with the faulty behavior is running openSUSE Tumbleweed.
The text was updated successfully, but these errors were encountered: