selinux/policycoreutils/setfiles
Jonathan Lebon 5f844b6991 setfiles: clarify documented path resolution behaviour
One thing that confused me when investigating
https://github.com/SELinuxProject/selinux/issues/248 (i.e.
https://github.com/coreos/fedora-coreos-tracker/issues/512) was that the
manual page for `setfiles` seemed to imply that paths were fully
resolved. This was consistent with the issues above where `setfiles` was
failing because the target of the symbolic link didn't exist.

But in fact, the wording around symbolic links in
`setfiles`/`restorecon` refers actually to whether the parent
directories are canonicalized via `realpath(3)` before labeling.

Clarify the man pages to explain this.

Signed-off-by: Jonathan Lebon <jlebon@redhat.com>
Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
2020-06-25 13:29:08 -04:00
..
ru Add man pages translation by Olesya Gerasimenko 2019-01-28 12:03:57 +01:00
.gitignore
Makefile Allow installing translated man pages 2019-01-28 12:03:57 +01:00
restore.c setfiles: Add -E option to treat conflicting specifications as errors. 2020-04-14 18:22:25 +02:00
restore.h setfiles: Add -E option to treat conflicting specifications as errors. 2020-04-14 18:22:25 +02:00
restorecon_xattr.8 setfiles: Update utilities for the new digest scheme 2019-07-27 10:39:24 +02:00
restorecon_xattr.c setfiles: Update utilities for the new digest scheme 2019-07-27 10:39:24 +02:00
restorecon.8 setfiles: clarify documented path resolution behaviour 2020-06-25 13:29:08 -04:00
setfiles.8 setfiles: clarify documented path resolution behaviour 2020-06-25 13:29:08 -04:00
setfiles.c Add restorecon -x option to not cross FS boundaries 2020-06-18 19:30:35 +02:00