Skip to content

Envoy: allow BoringSSL to enable ML-KEM by default.#45119

Open
divVerent wants to merge 1 commit into
envoyproxy:mainfrom
divVerent:divVerent/mlkemprepare
Open

Envoy: allow BoringSSL to enable ML-KEM by default.#45119
divVerent wants to merge 1 commit into
envoyproxy:mainfrom
divVerent:divVerent/mlkemprepare

Conversation

@divVerent
Copy link
Copy Markdown

This required adjusting QUIC tests to deal with the ClientHello no longer fitting in a single packet.

Commit Message: Allow BoringSSL to enable ML-KEM by default.
Additional Description: This required adjusting QUIC tests to deal with the ClientHello no longer fitting in a single packet.
Risk Level: low
Testing: unit test fix only; tested manually with patched BoringSSL

@repokitteh-read-only
Copy link
Copy Markdown

Hi @divVerent, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #45119 was opened by divVerent.

see: more, trace.

@divVerent divVerent had a problem deploying to external-contributors May 18, 2026 12:55 — with GitHub Actions Error
@repokitteh-read-only
Copy link
Copy Markdown

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #45119 was opened by divVerent.

see: more, trace.

This required adjusting QUIC tests to deal with the ClientHello no
longer fitting in a single packet.

Signed-off-by: Rudolf Polzer <rpolzer@google.com>
@divVerent divVerent force-pushed the divVerent/mlkemprepare branch from 4186e27 to 191454a Compare May 18, 2026 12:56
@divVerent divVerent requested a deployment to external-contributors May 18, 2026 12:56 — with GitHub Actions Waiting
@divVerent divVerent marked this pull request as ready for review May 19, 2026 05:53
@divVerent
Copy link
Copy Markdown
Author

Hi - can anyone start the testing workflows? I ported this change from a pending cl/ but did not manage to get Envoy to build on my own device yet, so I haven't tested the change in this repository yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant