Two releases on the same day, twenty minutes apart: v1.0.1 then v1.0.2. Both do the same job — harden pi-secured-setup itself. This is a short post to explain what changed and why it matters, because a security tool that ships its own vulnerabilities loses all credibility.
If you’re new to the project, the introductory article covers the basics: Guards, Scanners, the audit trail.
v1.0.1 — the quality pass
Three threads: