You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (Jira)" <ji...@apache.org> on 2022/03/29 16:12:00 UTC
[jira] [Updated] (KAFKA-13779) System test verifying key updates with TLS 1.3
[ https://issues.apache.org/jira/browse/KAFKA-13779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-13779:
--------------------------------
Description:
KAFKA-13418 identified a gap in our TLS 1.3 implementation. The fix for that included a unit test that forced a key update, which is a start. It would be good to also verify that the system behaves correctly when a key update is triggered automatically and it's more practical to achieve that via a system test [as explained in the PR|https://github.com/apache/kafka/pull/11966].
The system test can be a simple produce/consume workload with TLS 1.3 and Java 11 (or newer) and it must set the security property `jdk.tls.keyLimits` to a number smaller than the bytes encrypted by each client in the test.
was:
KAFKA-13418 identified a gap in our TLS 1.3 implementation. The fix for that included a unit test that forced a key update, which is a start. It would be good to verify that the system behaves correctly when a key update is triggered automatically and it's more practical to achieve that via a system test [as explained in the PR|https://github.com/apache/kafka/pull/11966].
The system test can be a simple produce/consume workload with TLS 1.3 and Java 11 (or newer) and it must set the security property `jdk.tls.keyLimits` to a number smaller than the bytes encrypted by each client in the test.
> System test verifying key updates with TLS 1.3
> ----------------------------------------------
>
> Key: KAFKA-13779
> URL: https://issues.apache.org/jira/browse/KAFKA-13779
> Project: Kafka
> Issue Type: Test
> Reporter: Ismael Juma
> Priority: Major
>
> KAFKA-13418 identified a gap in our TLS 1.3 implementation. The fix for that included a unit test that forced a key update, which is a start. It would be good to also verify that the system behaves correctly when a key update is triggered automatically and it's more practical to achieve that via a system test [as explained in the PR|https://github.com/apache/kafka/pull/11966].
> The system test can be a simple produce/consume workload with TLS 1.3 and Java 11 (or newer) and it must set the security property `jdk.tls.keyLimits` to a number smaller than the bytes encrypted by each client in the test.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)