-
Notifications
You must be signed in to change notification settings - Fork 1
Fix signature algorithm name #1
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
Conversation
Using KeyHostAlgorithm.Name as a SignatureKeyData.AlgorithmName would result in a "ssh-ed25519-cert-v01@openssh.com" algorithm name while the "ssh-ed25519" one is expected.
Hi, |
Thanks for taking a look! I'll get myself reacquainted with this branch and get back to you over the weekend |
So I had a look, I think it's something we should treat in CertificateHostAlgorithm. I want to write a couple of integration tests to make sure it is actually functional. I'll be a few more days with that |
I wrote a couple of integration tests for the authentication, moved this code to CertificateHostAlgorithm and confirmed the tests pass with this change. Thanks! Perhaps you could try it out and report back? Still TODO: integration tests for server certificates Also fyi @kakins |
Sorry, I had noble intentions here but life and other unrelated priorities quickly overtook me. Would like to come back this at some point when I can. |
No worries, the branch is basically complete now I'm just slowly adding polish then I'll submit upstream |
Using KeyHostAlgorithm.Name as a SignatureKeyData.AlgorithmName would result in a "ssh-ed25519-cert-v01@openssh.com" algorithm name while the "ssh-ed25519" one is expected.