chore(ci): hard-assert REST post-quantum key exchange on an OpenSSL 3.5 image - #1352
Draft
torreypayne wants to merge 1 commit into
Draft
torreypayne wants to merge 1 commit into
torreypayne wants to merge 1 commit into
Conversation
This was referenced Sep 15, 2026
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 16, 2026 19:16
b0b9724 to
5b926f1
Compare
….5 image The existing matrix runs on ubuntu-latest, whose system OpenSSL is 3.0.13. ML-KEM only exists from OpenSSL 3.5, so the REST transport there negotiates classical X25519 and the conformance assertion stays tolerant. gRPC is unaffected, since it carries its own BoringSSL inside the grpc gem. Add a job that re-runs the same showcase suite inside ruby:3.2-trixie, which provides OpenSSL 3.5.5, with SHOWCASE_REQUIRE_REST_PQC set. That promotes the tolerant assertion into a hard X25519MLKEM768 requirement and is what actually proves REST post-quantum key exchange works. The job asserts the image's OpenSSL is at least 3.5 before running the suite. Without that check, a future retag of the base image onto an older OpenSSL would silently drop back to the tolerant path and reintroduce exactly the false-green this job exists to prevent. ruby/setup-ruby is deliberately omitted: inside a container it detects debian-13-x64, treats the job as self-hosted, and will not use prebuilt binaries. The image's own Ruby is already linked against the OpenSSL we want. Once ubuntu-latest advances to Ubuntu 26.04, which ships OpenSSL 3.5.5, this job collapses into a single environment variable on the matrix above.
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 16, 2026 19:38
5b926f1 to
3c822da
Compare
torreypayne
added this pull request to stack #1353
September 16, 2026 20:00
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
1 participant
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.
Adds a
pqc-restCI job that hard-asserts REST post-quantum key exchange (X25519MLKEM768) on an image that actually provides OpenSSL >= 3.5.Layer 2 of the two-layer REST strategy: Layer 1 (#1351) asserts against a tolerant
{X25519MLKEM768, X25519}allowlist on every host; this job removes the tolerance, runningruby:3.2-trixie(OpenSSL 3.5.5) withSHOWCASE_REQUIRE_REST_PQC=1.Why a container rather than the stock runner
Ruby's
opensslis a default gem binding to whateverlibsslthe host provides. ML-KEM needs OpenSSL >= 3.5;ubuntu-latestships 3.0.13. No gemspec constraint, PPA, or backport fixes that, andruby/setup-rubylinks the runner's systemlibssl, so it cannot help either. Ruby is the only Cloud SDK language with this problem — Java ships Conscrypt, C++ vendors BoringSSL, Node bundles OpenSSL.ubuntu-26.04(3.5.5) was rejected as public preview with no GA date.Reviewer notes
ruby/setup-rubyis intentionally omitted. Inside acontainer:it detectsdebian-13-x64, classifies the job as self-hosted, and stops using prebuilts. The container's own Ruby is what we want anyway.Green, zero skips, on OpenSSL 3.0.18 / 3.5.5 / 3.6.3.
zizmoradds no new finding class.Sits on #1330 (fork-hosted, so GitHub excludes it from the stack) · Companion: ruby-core-libraries#73 raises the
gapic-commongrpc floor.Design: go/client-libraries:ruby-pqc · Parent: go/cloudsdk-pqc-ruby