From 3c7b0075f74fb6f8fbedeac266ddea00351977fd Mon Sep 17 00:00:00 2001 From: Vincas Dargis Date: Mon, 18 Mar 2019 20:17:01 +0200 Subject: [PATCH] docs(apparmor): Fix custom install prefix example AppArmor profile attachement example is wrong because it does not use { } "alternations" to make comma define alternative executable path. Update example to make it actually work in custom install prefix case. --- security/apparmor/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/security/apparmor/README.md b/security/apparmor/README.md index 966270a41..d3ca4b35d 100644 --- a/security/apparmor/README.md +++ b/security/apparmor/README.md @@ -113,7 +113,7 @@ sudo apparmor_parser -r /etc/apparmor.d/usr.bin.qtox For custom installations, when `qTox` executable is not `/usr/bin/qtox` or `/usr/local/bin/qtox`: 1. create `/etc/apparmor.d/tunables/usr.bin.qtox.d/local`, adding `@{qtox_prefix} += /path/to/your/custom/install/prefix` line. -2. modify `/etc/apparmor.d/usr.bin.qtox` profile attachement path: `profile qtox /usr{,local}/bin/qtox,/path/to/your/qtox_executable {` +2. modify `/etc/apparmor.d/usr.bin.qtox` profile attachement path: `profile qtox /{usr{,local}/bin/qtox,path/to/your/qtox_executable} {` Restart AppArmor and [check](#checking-if-qtox-is-actually-confined) if `qTox` process under custom path is actually confined.