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

Support alternate casing "Ed25519" (lowercase "d") #406

Closed
wants to merge 2 commits into from

Conversation

johnnyshields
Copy link

@johnnyshields johnnyshields commented Feb 5, 2021

Currently the system requires "ED25519". However, RFC#8037 refers to it clearly as "Ed25519" (lowercase "d"), and this casing is used in various other JWT libs such as Go, Erlang, and Haskell.

@johnnyshields johnnyshields changed the title Support alternate casing "Ed25519" Support alternate casing "Ed25519" (lowercase "d") Feb 5, 2021
@johnnyshields
Copy link
Author

@anakinj please take a look

@anakinj
Copy link
Member

anakinj commented Feb 5, 2021

This looks great. Think that the tests are failing because they are expecting Ed25519_private and Ed25519_private to exist in the hash on

'ED25519_private' => RbNaCl::Signatures::Ed25519::SigningKey.new('abcdefghijklmnopqrstuvwxyzABCDEF'),

@johnnyshields
Copy link
Author

Specs fixed

@anakinj
Copy link
Member

anakinj commented Feb 9, 2021

I'll close this one. #405 gives the case insensitivity and we need a proper fix for #334

@anakinj anakinj closed this Feb 9, 2021
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.

2 participants