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
x/crypto/ssh: can't establish ssh connection using signed key #54027
Comments
Hi @FiloSottile , here is an issue I filed per your request. Thanks! |
cc @FiloSottile @golang/security |
Folks, do you have any news on this by any chance? |
Any help with resolving this issue will be very much appreciated. |
@kt97679 Can you run ssh-agent with -d option and test running your program again?
and copy-paste the output once the program exit. |
@shuLhan please find output below. Please let me know if there is anything else I can do to help with debugging.
|
Tried today, still see failure:
Can I provide more details to help with the fix of this issue? |
Issue is still there:
It seems that this is a regression. I have old binary that works with signed keys ok and here is dependency:
|
issue is reproducible with golang.org/x/crypto v0.5.0
|
Hi folks, I found list of versions here: https://deps.dev/go/golang.org%2Fx%2Fcrypto/v0.0.0-20151201002508-7b85b097bf75/versions and was able to identify versions where issue was introduced:
I really hope this will help with fixing this issue. Thank you. |
From what I see issue is related to this change: golang/crypto@5d542ad#diff-bb5baf29632fd3d0305064ad6e6dc4b9849778a8cd1513f08cf9e866c61210acL775-L783 |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?ubuntu 18.04 amd64
go env
OutputWhat did you do?
What did you expect to see?
Connection is established using signed key.
What did you see instead?
Connection is not established with an error message:
Additional information
I have 2 keys in the agent and I can connect ok via ssh command to 127.0.0.1 (accepts only unsigned keys) and 10.19.197.10 (accepts only signed keys):
Versions of the ssh components are in the output above.
The text was updated successfully, but these errors were encountered: