Dear,
in Java 11 (JEP 329) ChaCha20 and Poly1305 cryptographic algorithms had been
implemented. However, the cipher suite TLS_CHACHA20_POLY1305_SHA256 wasn't
added to the Java standard cipher suites. As far as I can see, support for this
cipher suite is neither part of Java 12.
Out of interes
Great! Thank you Bradford and Jamil.
-- Ralph
On 3/26 0:14:24 AM, Bradford Wetmore wrote:
>Please see the SunJSSE provider documentation for JDK 12.
>
>https://docs.oracle.com/en/java/javase/12/security/oracle-providers.html#GUID-7093246A-31A3-4304-AC5F-5FB6400405E2
>
>Brad
>
>
>On 3/25/20
Dear all,
in Java 13 the new System properties
jdk.tls.client.enableSessionTicketExtension and
jdk.tls.server.enableSessionTicketExtension were introduced. In TLS 1.2 and
prior these properties support stateful session resumption according to RFC
5077.
In TLS 1.3, however, there is no Se
Hi Tony,
thank you for the clarification.
Btw: If I'm not mistaken, the new System properties for stateless session
resumption are not included in the documentation
https://docs.oracle.com/en/java/javase/13/security/java-secure-socket-extension-jsse-reference-guide.html#GUID-93DEEE16-0B70-40E5-
Hi all,
I very much appreciate @SalusaSecondus' idea for providing a key logger.
For, when working with networks, it's quite natural to analyze message flow
with help of wireshark. In TLS 1.3 this isn't possible without a key log
because most parts of the handshake messages are encrypted. So,
Concerning the question:
>Also the note about TLS 1.3 in the same section isn't entirely clear
to me. What does it mean when the docs say "the contents of stateless
>tickets, in particular, the contents of a NewSessionTicket message,
>depend on the value of jdk.tls.server.enableSessionTicketExten
Hi Daniel,
I agree that the doc is a bit misleading. Maybe, the TLS 1.2 part can be put
into the note:
--
jdk.tls.server.enableSessionTicketExtension: Enables a server to use stateless
session
tickets. A value of true (default value) enables the use of stateless session
