Skip to content

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

Merged
merged 4 commits into from
Jul 21, 2024

Conversation

cedricMicrovision
Copy link

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.

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.
@cedricMicrovision
Copy link
Author

Hi,
While I continue to use this certificates branch, I faced a similar problem with RSA keys : "ssh-rsa" algorithm name is used instead of "rsa-sha2-256" or "rsa-sha2-512".
Using a regular expression to remove the "cert" part from the name seems to solve the problem for both Ed25519 & RSA keys.
What do you think ?

@Rob-Hague
Copy link
Owner

Thanks for taking a look! I'll get myself reacquainted with this branch and get back to you over the weekend

@Rob-Hague
Copy link
Owner

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

@Rob-Hague Rob-Hague self-requested a review as a code owner July 21, 2024 23:18
@Rob-Hague Rob-Hague merged commit 25042da into Rob-Hague:certificates Jul 21, 2024
@Rob-Hague
Copy link
Owner

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

@kakins
Copy link

kakins commented Sep 1, 2024

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.

@Rob-Hague
Copy link
Owner

No worries, the branch is basically complete now I'm just slowly adding polish then I'll submit upstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants