Skip to content

v2.0.1

Choose a tag to compare

@github-actions github-actions released this 02 Nov 18:42
· 4 commits to main since this release
v2.0.1
bae9fd3

Straza 2.0.1 is a security and bug-fix release for 2.0.0. It changes no wire format and no database schema, so you upgrade the binary or the package and nothing else.

Security

  • Interpreter rules now apply to straza exec. A rule such as interpreters: {deny: ["python*"]} held on a harness hook but not on straza exec, which is also the path of a hookless sandbox's wrappers.
  • The standalone database is readable by its owner only. strazad created it with mode 0644, and the standalone guide made its data directory 0755, so any local user could read the audit records and password hashes in it. strazad now creates it 0600 and narrows an existing one when it starts.

Fixed

  • A call that a classify rule allows runs again. In 2.0.0 every such call was denied, while its audit record said allow.
  • An API token request with expires_in sent as text answers that it must be a whole number of seconds, where it answered "name is required".

Before you upgrade

  • The Linux, macOS and Windows packages restart straza service. If you run straza service from the archive, restart it after the upgrade, because the classify and exec fixes run in it.
  • After the upgrade, an exec call that an interpreter rule denies or sends to the classifier is denied or classified, as on a hook. Check your interpreter rules before you roll it out to a hookless sandbox or a CI job that runs through straza exec.
  • On a standalone host, strazad narrows straza.db and its -wal and -shm files to 0600 at its first start and logs each file it changes. A backup job that read the database as another user needs to read it as the user that runs strazad.

Which file do I need

Each archive (.tar.gz, .zip) holds all three programs: strazad, the server, also for a standalone install on one host; strazactl, the admin CLI; and straza, the client. Each package holds only the client and installs its background service: .deb or .rpm on Linux, .msi on Windows, .pkg on macOS. On Docker or Kubernetes, run the server from ghcr.io/strazahq/straza:2.0.1 or the Helm chart.

Install and verify

Verify your download with Download a release and verify it: checksums.txt is signed with cosign, and every file below, the packages included, has its line in it. The image is ghcr.io/strazahq/straza:2.0.1, and the Helm chart is 2.0.1.

The changelog lists every change of this release.