chore(ci): provision an OpenSSL 3.5 image and hard-assert REST post-quantum key exchange - #1352
Open
torreypayne wants to merge 2 commits into
Open
torreypayne wants to merge 2 commits into
torreypayne wants to merge 2 commits into
Conversation
This was referenced Sep 15, 2026
torreypayne
force-pushed
the
pqc-rest-ci
branch
2 times, most recently
from
September 16, 2026 19:38
5b926f1 to
3c822da
Compare
torreypayne
added this pull request to stack #1353
September 16, 2026 20:00
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 16, 2026 20:26
3c822da to
4b5b229
Compare
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 16, 2026 20:40
4b5b229 to
ebbdeec
Compare
torreypayne
force-pushed
the
pqc-rest-ci
branch
2 times, most recently
from
September 17, 2026 17:58
168ca63 to
960ac5e
Compare
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 21, 2026 17:10
960ac5e to
404ad56
Compare
torreypayne
removed this pull request from stack #1353
September 21, 2026 17:11
torreypayne
added this pull request to stack #1356
September 21, 2026 17:12
torreypayne
force-pushed
the
pqc-rest-ci
branch
2 times, most recently
from
September 21, 2026 18:00
86f5149 to
de655fa
Compare
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 21, 2026 20:50
de655fa to
82c8f11
Compare
torreypayne
changed the title
torreypayne
marked this pull request as ready for review
September 21, 2026 20:50
torreypayne
force-pushed
the
pqc-rest-ci
branch
from
September 22, 2026 17:25
82c8f11 to
2793397
Compare
amanda-tarafa
approved these changes
Sep 24, 2026
torreypayne
force-pushed
the
pqc-rest-ci
branch
2 times, most recently
from
September 24, 2026 20:49
e0c2d22 to
78f1700
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 25, 2026 17:16
78f1700 to
fec7163
Compare
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
2 participants
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.
#1351 derives the REST expectation from the host: OpenSSL >= 3.5 must negotiate ML-KEM, older hosts must negotiate
X25519. No GitHub-hosted runner can reach the first branch.ubuntu-latest(Ubuntu 24.04) ships OpenSSL 3.0.13, and Ruby'sopensslis a binding to whateverlibsslthe host provides.So this PR adds a
pqc-restjob onruby:3.2-trixie(OpenSSL 3.5.5), where REST must negotiate ML-KEM.SHOWCASE_REQUIRE_REST_PQC=1plus a workflow guard step fail the job if the image ever drops below 3.5, instead of it silently reverting to the classical expectation. Onceubuntu-latestmoves to 26.04 (rollout from 2026-10-19) this folds back into the matrix; tracked in b/564510736.Negative controls
Both ways this job could go quietly useless were verified to fail loudly instead:
The second leaves the gRPC tests green — gRPC vendors its own BoringSSL — so the job discriminates rather than merely being fragile.
Reviewer note
ruby/setup-rubyis intentionally omitted: inside acontainer:it detectsdebian-13-x64, treats the job as self-hosted, and stops using prebuilt binaries.Companion: ruby-core-libraries#73 raises the
gapic-commongrpc floor.Design: go/client-libraries:ruby-pqc · Parent: go/cloudsdk-pqc-ruby