|UNVEIL(2)||System Calls Manual||UNVEIL(2)|
char *path, const char
unveilremoves visibility of the entire filesystem from all other filesystem-related system calls (such as open(2), chmod(2) and rename(2)), except for the specified path and permissions.
unveil system call remains capable of
traversing to any path in the filesystem, so
additional calls can set permissions at other points in the filesystem
After establishing a collection of path and
permissions rules, future calls to
unveil can be disabled by passing two
NULL arguments. Alternatively,
pledge(2) may be used to remove the
The permissions argument points to a string consisting of the following characters:
A path that is a directory will enable all
filesystem access underneath path using
permissions if and only if no more specific matching
unveil() exists at a lower level. Directories are
remembered at the time of a call to
means that a directory that is removed and recreated after a call to
unveil() will appear to not exist.
Non-directory paths are remembered by name within their containing
directory, and so may be created, removed, or re-created after a call to
unveil() and still appear to exist.
Attempts to access paths not allowed by
unveil will result in an error of
EACCES when the permissions
argument does not match the attempted operation.
ENOENT is returned for paths for which no
unveil permissions qualify.
unveil() use can be tricky because
programs misbehave badly when their files unexpectedly disappear. In many
cases it is easier to unveil the directories in which an application makes
use of files.
unveilwas called after locking.
unveil() system call first appeared in OpenBSD 6.4.
unveilrestrictions required by realpath(3). Future changes intend to repair this problem.
|March 24, 2019||OpenBSD-current|