-
Notifications
You must be signed in to change notification settings - Fork 204
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
Add P-384 #186
Add P-384 #186
Conversation
This is fine by me, but we're now out of space in Thoughts from anyone else? @OR13 just out of interest, do you have a current use-case for a P-384 public key? |
yes, the main problem is that web crypto / hardware backed kms often don't support secp256k1, ed25519 or bls12381... so what do you do if you are required to work with say ... a customer who requires you use NIST curves for somethings ? I would like to be able to generate a non extractable software isolated key in a browser, and represent it using https://github.com/w3c-ccg/did-method-key I have used I chose P-384 because of its use by both the US and NZ governments. |
@rvagg yes, its probably better to register all the NIST Curves nicely in their own block... I was wondering how we were going to go higher than |
if someone can recommend the block to register for NIST curves, I will close this PR and open open one which registers them. |
Anything above the single byte range is wide open, I see two slots that might be nice (this is mostly a subjective call given the space available!). After |
0x1200 - P-256 ^ would this be correct?... |
Closing this PR in favor of #190 |
AFAIK, this will be the first NIST Curve added here... so its pretty valuable for legacy systems.