-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Implement TLS v1.3, including X25519 and Ed25519, especially within X509 certs. #345
Comments
Work on Ed25519 is under way and TLS 1.3 is beginning shortly. |
There is something regarding Ed25519 in open-keychain#2. |
Yes, and I've just now submitted a pull-request with code based on the above but reworked for more seamless integration with bcgit:master. |
? |
There's existing X25519 math code under core/src/main/java/org/bouncycastle/math/ec/rfc7748 I understand that there's a possible path to/from Ed25519/X25519 keys but that's beyond my skills. |
Closing as TLS 1.3 is in place now. We do not yet enable it for the "TLS" SSLContext though; you currently need to use "TLSv1.3" explicitly, or else enable it on the individual sockets/engines, or use jdk.tls.client.protocols/jdk.tls.server.protocols system properties. Relative to TLS 1.2, it is currently missing session resumption. Relative to the full TLS 1.3 spec it is missing several of the new features, e.g. early data, half-close. Specific issues can be raised for these, although they are not likely to be on our roadmap for this year. |
Now that TLS v1.3 has been approved by the IETF can it be implemented into BC please?
Note that section 9.1 "Mandatory-to-Implement Cipher Suites" states that "A TLS-compliant application [...] SHOULD support key exchange with X25519 [RFC7748]."
You have some X25519-related code already and I can submit a pull request for most of the Ed25519/X509 aspect however I am new to the BC codebase so it would need serious reviewing.
The text was updated successfully, but these errors were encountered: