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

Unable to login with my rsa key #48

Open
Arkaeriit opened this issue Dec 20, 2021 · 7 comments
Open

Unable to login with my rsa key #48

Arkaeriit opened this issue Dec 20, 2021 · 7 comments
Labels
bug Something isn't working

Comments

@Arkaeriit
Copy link

Arkaeriit commented Dec 20, 2021

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:

debug1: Authentications that can continue: publickey                                           
debug1: Next authentication method: publickey                                                  
debug1: Offering public key: /home/maki/.ssh/id_rsa RSA SHA256:uv+MKsX3MQHgDO5rlO0JenaP0oZbK87vcx+4BnOfr+4                                                                                     
debug1: send_pubkey_test: no mutual signature algorithm

On one of my other computer, the RSA key is accepted with no trouble:

debug1: Offering public key: /root/.ssh/id_rsa RSA SHA256:7F/em69/OfQsroSBri2JjxoCjsLB2qsVGGCA998vdUo                                                                                          
debug1: Server accepts key: /root/.ssh/id_rsa RSA SHA256:7F/em69/OfQsroSBri2JjxoCjsLB2qsVGGCA998vdUo                                                                                           
debug1: Authentication succeeded (publickey).

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.

@toby
Copy link
Contributor

toby commented Jan 11, 2022

Hi, thanks for reporting this. That's definitely odd. Can you try the latest version and see if you're still having the issue?

@toby toby added the bug Something isn't working label Jan 11, 2022
@Arkaeriit
Copy link
Author

Arkaeriit commented Jan 14, 2022

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.

@wychwitch
Copy link

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!

@caarlos0
Copy link
Member

caarlos0 commented Jan 21, 2022

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

@quackduck
Copy link

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.

@Andonome
Copy link

Andonome commented Apr 1, 2023

Any update on this?

It'd also be nice if the interface said to place your ssh keys, but not rsa-keys.

@caarlos0
Copy link
Member

caarlos0 commented Apr 2, 2023

golang/crypto#197 is still unmerged...

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

6 participants