kodebeat / papers / security
Turning container hardening findings into the fixed file
A Dockerfile rewriter that emits the hardened file as a diff.
Where a linter emits warnings for a human to act on, this emits the corrected file as a diff: pinned base images, apt lists cleaned inside the layer that created them, a non-root USER, COPY --chown once a user is set. Every pass is idempotent, hardening a hardened file is a no-op, and that property is tested.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the Security & supply chain theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.