-
Notifications
You must be signed in to change notification settings - Fork 10
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
Document the requirements for the ssh keys #11
Comments
I’m not so sure either. rsa keys used to work, but at some point that stopped working. I’m not sure if it was a change in OpenSSH (i.e. on the client side) or in the Personally I just switched to ed25519 and called it a day. Sounds like some more detective work is necessary, but we could just recommend ed25519 for now |
Yeah for me this is (now that I know about it) not big of a deal aswell, I just think the error is not that easy to spot. Especially if you do not run ssh in verbose mode you just get "Permission denied (publickey)". Newcomers (like me yesterday) might rather question if the overall gokrazy deployment they created is right than check for the ssh output. IMO a little notice in the readme should suffice! |
For sure. We can add a note for now until someone wants to look deeper into whether rsa can be made working again and how. Do you want to send a PR with the note? :) |
See issue gokrazy#11 for further discussion
See issue #11 for further discussion
So apparently it was a change in OpenSSH and
https://github.com/rmohr/crypto is apparently a fork that implements authentication via RSA keys, for the time being I wouldnt switch but rather just wait until its fixed in mainline! 😊 |
Thanks for investigating! Yeah, waiting like x/crypto fixes it sounds good to me :) |
@stapelberg, I think this can be closed now. The x/crypto changes seem to work. I just tested and was able to use an RSA key to log in to my Gokrazy VM on EC2:
Notable lines from above:
|
Apparently RSA Keys do not work with breakglass:
ssh
output (click to expand)I am not sure whether this is expected and just needs documentation or if its is a bug ...
The text was updated successfully, but these errors were encountered: