Repository navigation
feat(supply-chain): implement predictable releases, automated scanning, SBOM provenance, and hardened runtime (Milestone 7) - #25
Merged
Conversation
…g, SBOM provenance, and hardened runtime (Milestone 7)
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
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.
Problem
Prior to this PR, release versioning, vulnerability scanning, provenance/SBOM generation, and runtime hardening guidelines were undocumented and unverified. Users lacked guidance for running
torproxywith read-only filesystems or dropped Linux capabilities in hardened production environments, and CI lacked automated vulnerability scanning.Resolves #24
Solution
Implemented Milestone 7 tasks without breaking changes:
1.2.0inpyproject.tomland addedorg.opencontainers.image.version="1.2.0"label in Dockerfile. Documented SemVer guarantees, upgrade paths, and instant rollback procedures indocs/releases.md.pr-gate.yml), and documented the vulnerability management policy, SLA, and false-positive handling inSECURITY.md.mode=max) inpublish-dockerhub.yml. CreatedDOCKERHUB.mdand configured automated description sync.docs/hardening.mdand a production-readyexamples/hardened-production/configuration demonstratingread_only: true,cap_drop: [ALL],no-new-privileges: true, and scratchtmpfsmounts. Added automated tests intest_examples.pyand a smoke check in CI.Compatibility
Tests
ruff check .passed cleanly with 0 errors.docker/start.sh,docker/healthcheck.sh, andtests/integration/verify_container.shpassed with 0 warnings.tests/unit/test_examples.pyvalidates 4 examples (17 tests) including hardened production.Security and Privacy
torproxy).SECURITY.md.cap_drop: [ALL]andread_only: truewithout affecting Tor or Privoxy function.Documentation
docs/releases.md,docs/hardening.md,DOCKERHUB.md, andexamples/hardened-production/README.md.README.mdandSECURITY.md.Remaining Limitations