What changed, and why it matters
This commit updates a documentation file (README) that describes how to manually create a permissive AppArmor profile for the Guix build environment. It changes the AppArmor ABI version referenced and broadens the file paths covered by the profile. It is a build/operational documentation change, not a code change to Feather Wallet itself, and it does not fix or introduce a software vulnerability.
No security action required. Review as normal documentation update if auditing build instructions.
Security signals we found
No security-relevant code changes
Documentation-only change to build environment setup instructions
AppArmor profile remains explicitly permissive (unconfined)
Evidence from the diff
The diff modifies contrib/guix/README.md. It changes the suggested AppArmor profile from ABI 4.0 to ABI 3.0 and expands the executable path pattern from /usr/bin/guix to multiple Guix-related store paths. The profile remains flags=(unconfined) and userns, meaning it is intentionally permissive. This is documentation for users setting up a Guix build environment; it does not alter Feather Wallet source code, wallet logic, cryptography, networking, or build scripts.
Changed components
contrib/guix/README.mdInspect captured patch +2 / −3
### contrib/guix/README.md
@@ -62,10 +62,9 @@ To work around this issue, you need to create a permissive AppArmor profile for
```bash
$ apt install apparmor-utils
$ cat <<EOL >> /etc/apparmor.d/guix
-abi <abi/4.0>,
+abi <abi/3.0>,
include <tunables/global>
-
-profile guix /usr/bin/guix flags=(unconfined) {
+profile guix /gnu/store/{*-guix-command,*/bin/guix-daemon,*/bin/guix,*/bin/guile} flags=(unconfined) {
userns,
include if exists <local/guix>
}Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.