akitaonrails/ai-jail v1.18.1

on GitHub

Security fix

• A literal mask or deny_paths entry that does not exist when the sandbox
  is built is skipped, which drops a confidentiality control. That warning
  used the ordinary warning channel, so --exec quiet mode suppressed it
  entirely — exactly the automated mode where nobody would notice the rule
  had lapsed. Both mask and deny skips now use the security warning channel,
  which bypasses --exec quiet, and say plainly that the rule was not
  applied:

  ⚠ Deny: /path/.env does not exist; rule not applied
  

  Masks and denies still only cover paths that exist at launch. Create the
  file beforehand (an empty .env is enough) when you need the rule
  enforced. Thanks to @maarcotulio for raising this (#95).

Release integrity

• Release tags are now signed and cryptographically verified in CI against a
  pinned key in .github/release-keyring/. Previous releases, including
  v1.18.0, were unsigned and logged an explicit "tag signature NOT
  cryptographically verified" warning.
• The release-signing and release-publish environments are restricted to
  v* tag runs, and GitHub Actions are limited to an allowlist of
  GitHub-owned actions plus dtolnay/rust-toolchain.

Packaging

• AUR PKGBUILD and PKGBUILD-bin updated for the 1.18.x series.

Checksums (SHA256)

f7a4c17578f91ee76a42718e8ee204bc45284543f5fbb7d6e1d6066fb46e2d0c  ai-jail-linux-x86_64.tar.gz
a8fea88f8f3ef3964bd56ccc0556ec9b0bfb9ffe49babb569e486d19ca2b12e8  ai-jail-macos-aarch64.tar.gz

Install

brew tap akitaonrails/tap && brew install ai-jail
yay -S ai-jail-bin
cargo install --locked ai-jail