0.10.1

A fix for integrity checks, and a README you can read in five minutes

• Fix: integrity accept no longer races the background check. Squidbrake checks its own hooks, rules and installed files every minute. If that check ran at the moment you ran squidbrake integrity accept, it could write the old "changed" state back after your accept. With integrity: fail_closed on, risky actions then stayed blocked until the next check. The check and the accept now never run at the same time (#89). Only installs with integrity: fail_closed were affected; the default alert only showed the change again.
• A shorter README (#88): what Squidbrake is, a four-step quick start (install, observe, squidbrake report --week, enforce), what it controls, proof, deployment, security model and limits, and privacy.
• The details move to docs/, unchanged:
  • install
  • rules and checks
  • integrations
  • operations
  • FAQ

Upgrading from 0.9.x? Read the 0.10.0 notes first: three defaults changed.

Install this version (0.10.1)

Windows (PowerShell):

$env:SQUIDBRAKE_VERSION="0.10.1"; irm https://pilots.squidbrake.com/install.ps1 | iex

macOS / Linux:

curl -fsSL https://pilots.squidbrake.com/install.sh | SQUIDBRAKE_VERSION=0.10.1 sh

With pip: pip install squidbrake==0.10.1. Docker: docker pull ghcr.io/batrapulkit/squidbrake:0.10.1

Running the line again without SQUIDBRAKE_VERSION goes back to the newest. Every version:
https://github.com/batrapulkit/squidbrake/releases