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

NIST vs SECP #10

Closed
mcr opened this issue May 24, 2017 · 2 comments
Closed

NIST vs SECP #10

mcr opened this issue May 24, 2017 · 2 comments

Comments

@mcr
Copy link

mcr commented May 24, 2017

 nistp256.rb             
 secp256r1.rb   

As far as I can verify, these are two names for the same group.
Ditto for the 192 and 521.
http://www.secg.org/collateral/

no longer answers, being directed to certicom's web site. I wonder if it wouldn't be better to just have one or the other in the source code base?

@DavidEGrayson
Copy link
Owner

Thanks for pointing this out. I can't think of any particular changes I would want to make to the code in light of this information which would not be breaking changes. Even just making one group be an alias for the other would be a breaking change because param_a and name of one of the groups would have to change.

@mcr
Copy link
Author

mcr commented Oct 7, 2019

Okay, reasonable.

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

No branches or pull requests

2 participants