feat: add libssl3t64 runtime for OpenSSL-linked binaries#1
Merged
Conversation
Previously pulled in transitively via Python 3.12 / ca-certificates on debian:trixie-slim. Making it explicit so downstream projects that run OpenSSL-linked binaries (e.g. SolidSyslog E3 TLS transport) don't depend on the transitive graph holding stable across base-image updates. Note: package is libssl3t64 (t64 = Debian 13's time64 transition), not libssl3 — the latter doesn't exist in trixie. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2 tasks
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.
Summary
Explicitly declare `libssl3t64` as a runtime dependency. It's already pulled in transitively by Python 3.12 / ca-certificates on `debian:trixie-slim`, but making it explicit removes the ambiguity for downstream projects that run OpenSSL-linked example binaries — e.g. SolidSyslog E3 (TLS transport).
Companion to CppUTestDocker#1 and CppUTestDockerClang#1, which added `libssl-dev` to the compiler images. Development there; runtime here.
Why `libssl3t64` not `libssl3`?
Debian 13 / trixie's time-64 transition renamed the package. `apt-cache policy libssl3` shows no candidate; `libssl3t64` is the right name. Same shared library (`libssl.so.3`).
Test plan
🤖 Generated with Claude Code