-
Notifications
You must be signed in to change notification settings - Fork 45
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 curve customization #713
Comments
This sounds like a straightforward parameter addition to the schema, and feeding that info through zss.c and zowe-common-c/c/tls.c. However the enumeration of valid values needs to be researched starting from https://datatracker.ietf.org/doc/rfc4492/ and it's related and superseding RFC's. |
I believe the full list of curve strings is here https://neuromancer.sk/std/x962/ Short story: much like our TLS cipher implementation, we should utilize the name strings, and then create the string-to-number map. You can even query what node supports, to see their syntax: |
zowe.network.server.tls.curves is an array a user can set in zowe.yaml to customize crypto curves.
But, zss doesnt do anything with that array currently.
GSK handles curve customization much like cipher customization, which we already do here
zss/c/zss.c
Line 1192 in f44ce8a
That is, curves are specified as a string of 4 digit numbers back to back without any spaces or symbols inbetween.
Its very unfriendly to a human, so a convention of mapping from names to numbers is needed.
However, all of zowe needs to conform to the names. I dont know which name strings are available.
Node claims to use ASN.1 strings like "prime256v1"
So,
The text was updated successfully, but these errors were encountered: