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

Proposal: API additions for determining curve support #19877

Closed
vcsjones opened this issue Jan 11, 2017 · 2 comments
Closed

Proposal: API additions for determining curve support #19877

vcsjones opened this issue Jan 11, 2017 · 2 comments
Labels
api-suggestion Early API idea and discussion, it is NOT ready for implementation area-System.Security
Milestone

Comments

@vcsjones
Copy link
Member

Right now in netstandard1.6 we have ECCurve for using named or arbitrary ECC curves. This is very useful for certain type of applications where the curve is a configurable option (for example, a German company that insists on using brainpool curves for certain operations).

What we don't have right now is an easy way to list all of the supported named curves for a particular platform. Keeping with the brainpool example, Windows 10 supports most (if not all) of the named brainpool curves, however Windows 8.1 and below do not in CNG. Also, depending on how far #17597 goes, macOS CommonCrypto / Security Transforms do not support curves other than the standard NIST prime curves and some of djb's curves.

I'm not entirely sure all platforms support arbitrary curves, either (for example, Twisted Edwards curves).

I would then propose an API that lets us determine the capabilities of the current platform.

@vcsjones
Copy link
Member Author

/cc @bartonjs

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 23, 2020
@bartonjs bartonjs modified the milestones: 5.0.0, Future Jul 7, 2020
@bartonjs bartonjs removed the untriaged New issue has not been triaged by the area owner label Jul 7, 2020
@vcsjones
Copy link
Member Author

vcsjones commented Feb 3, 2021

I'm no longer invested in this proposal, and given the lack of discussion on it, I am going to close this out.

@vcsjones vcsjones closed this as completed Feb 3, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Mar 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api-suggestion Early API idea and discussion, it is NOT ready for implementation area-System.Security
Projects
None yet
Development

No branches or pull requests

4 participants