Repository navigation
Post-quantum cryptography blog post (part 1: named groups) - #305
Open
MarkNSweep wants to merge 1 commit into
Open
MarkNSweep wants to merge 1 commit into
MarkNSweep wants to merge 1 commit into
Conversation
This is the first post in the Kroxylicious post-quantum series, covering the named-groups control delivered in the 0.26 release. It explains why post-quantum matters now through 'harvest now, decrypt later', introduces TLS named groups and the hybrid X25519MLKEM768 group, and walks through controlling the groups negotiated on both sides of the proxy. The downstream walkthrough covers a client to Kroxylicious, and the upstream walkthrough covers Kroxylicious to Kafka, each showing the configuration and the negotiated outcome across Java 21 and Java 25. The diagrams are kept as mermaid sources in Jekyll comment blocks with rendered SVGs committed alongside. Screenshots and the walkthrough recordings accompany each scenario. Assisted-by: Claude Opus 4.8 <[email protected]> Signed-off-by: Adam Pilkington <[email protected]>
1 task
k-wall
reviewed
Nov 19, 2026
k-wall
reviewed
Nov 19, 2026
| The upstream walkthrough, Kroxylicious to Kafka used a two-terminal layout. The left terminal shows the Kroxylicious configuration. The right terminal shows the named group negotiated with the upstream Kafka, obtained by turning on TLS tracing for Kroxylicious with `-Djavax.net.debug=SSL` and filtering for the negotiated group. A producer sending a single message drove the upstream connection. | ||
|
|
||
| <video controls muted playsinline width="720" preload="metadata"> | ||
| <source src="/assets/blog/videos/pqc-series/kroxy-upstream-pqc.mp4" type="video/mp4"> |
Member
There was a problem hiding this comment.
Could we put the videos on the Kroxylicious youtube channel? You can link back to the blog post from the youtube content page too.
Member
|
@MarkNSweep I've only read rthe text, but nice job, I think this looks great! I'll review the video content tomorrow. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Post-quantum Kafka, part 1: controlling TLS named groups
Adds the first post in the Kroxylicious post-quantum series. It covers the named-groups control delivered in the 0.26 release: how to constrain the TLS named groups negotiated downstream (a client to Kroxylicious) and upstream (Kroxylicious to Kafka), and how a post-quantum key exchange with X25519MLKEM768 depends on the JDK at each end of the connection.
The post introduces post-quantum cryptography and 'harvest now, decrypt later', explains named groups and their place in the TLS 1.3 handshake, then works through each scenario with the Kroxylicious configuration and the negotiated outcome on Java 21 and Java 25. It relates to the 0.26 PQC delivery tracked in kroxylicious/kroxylicious#5186.
The diagrams are mermaid sources in Jekyll comment blocks with committed SVGs, and screenshots and the walkthrough recordings accompany the scenarios.
🤖 Generated with Claude Code