security: verified socat mitigation recipes + monthly base-image digest refresh - #20
Merged
Merged
Conversation
…mage digest refresh workflow
libre-7
added a commit
that referenced
this pull request
Aug 24, 2026
security: verified socat mitigation recipes + monthly base-image digest refresh
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.
S1 — socat exposure mitigation (README)
Adds a Securing the socat port section next to the socat bridge docs with two live-verified recipes against the v1.0.1 image:
-p 127.0.0.1:5226:5226) — verified WS handshake 101 via loopback, connection refused from LAN IP; plus optionalDOCKER-USERiptables allowlist and Tailscaleserveforward for tailnet-only exposure.S5 — base-image digest rotation (.github/workflows/base-refresh.yml)
Monthly scheduled workflow (plus workflow_dispatch): resolves current
ubuntu:24.04digest via skopeo, compares to Dockerfile line-1 pin, opens an automated PR when it moved. Keeps the digest pin; automates re-pinning.Both verified from the test VM (192.168.1.127); containers/images cleaned up afterwards.