RFR: 8331682: Slow networks/Impatient clients can potentially send unencrypted TLSv1.3 alerts that won't parse on the server [v22]
Xue-Lei Andrew Fan
xuelei at openjdk.org
Thu Oct 24 07:12:10 UTC 2024
On Mon, 21 Oct 2024 20:18:24 GMT, Artur Barashev <abarashev at openjdk.org> wrote:
>> Check for unexpected plaintext alert message during TLSv1.3 handshake. This can happen if client doesn't receive ServerHello due to network timeout and tries to close the connection by sending an alert message.
>
> Artur Barashev has updated the pull request incrementally with one additional commit since the last revision:
>
> Update Copyright
src/java.base/share/classes/sun/security/ssl/SSLCipher.java line 1878:
> 1876: }
> 1877:
> 1878: throw new BadPaddingException(msg);
Is BadPaddingException still good enough for alert messages? Is the exception message description accurate for both client and server cases?
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/21043#discussion_r1814392719
More information about the security-dev
mailing list