itycodes
/
convince
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify that executable has to be a full path

Browse Source
master
Drew DeVault 8 years ago
parent c61746a15b
commit 0c8dc0e6df
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File

6
sway/sway-security.7.txt
Unescape View File

@ -104,11 +104,13 @@ access:
**permit** <executable> <features...>:: **permit** <executable> <features...>::
Permits <executable> to use <features> (each feature seperated by a space). Permits <executable> to use <features> (each feature seperated by a space).
<executable> may be * to affect the default policy. <executable> may be * to affect the default policy, or the full path to the
executable file.
**reject** <executable> <features...>:: **reject** <executable> <features...>::
Disallows <executable> from using <features> (each feature seperated by a space). Disallows <executable> from using <features> (each feature seperated by a space).
<executable> may be * to affect the default policy. <executable> may be * to affect the default policy, or the full path to the
executable file.
Note that policy enforcement requires procfs to be mounted at /proc and the sway Note that policy enforcement requires procfs to be mounted at /proc and the sway
process to be able to access _/proc/[pid]/exe_ (see **procfs(5)** for details on process to be able to access _/proc/[pid]/exe_ (see **procfs(5)** for details on

Write Preview
Loading…
Cancel
Save