2a6f4bfe17
- rebase to 1.0.4 - added rpm_sha256_only option - added trust.d directory - allow file names with whitespace in trust files - use full paths in trust files Resolves: rhbz#2032408 - fix libc.so getting identified as application/x-executable Resolves: rhbz#2015307 - fix selinux DSP module definition in spec file Resolves: rhbz#2014449
17 lines
1.2 KiB
Diff
17 lines
1.2 KiB
Diff
diff --color -ru a/doc/fapolicyd.trust.5 b/doc/fapolicyd.trust.5
|
|
--- a/doc/fapolicyd.trust.5 2021-11-12 20:21:54.000000000 +0100
|
|
+++ b/doc/fapolicyd.trust.5 2021-12-07 13:28:18.358213561 +0100
|
|
@@ -7,6 +7,12 @@
|
|
contains list of trusted files/binaries for the application whitelisting daemon. You may add comments to the file by starting the line with a '#' character.
|
|
Each line has to contain three columns and space is a valid separator. The first column contains full path to the file, the second is size of the file in bytes
|
|
and the third is valid sha256 hash.
|
|
+.sp
|
|
+The directory \fI/etc/fapolicyd/trust\&.d\fR can be used to store multiple trust files\&.
|
|
+This way a privileged user can split the trust database into multiple files and manage them separately through \fBfapolicyd\-cli\fR\&.
|
|
+Functionally, the fapolicy daemon will behave the same way as if the whole trust database has been defined inside \fBfapolicyd\&.trust\fR file\&.
|
|
+Syntax and semantics of trust files inside \fBtrust\&.d\fR directory are the same as for \fBfapolicyd\&.trust\fR file (described above)\&.
|
|
+Trust files can either be created manually inside \fBtrust\&.d\fR directory or via \fBfapolicyd\-cli\fR\& (the latter option is recommended).
|
|
|
|
.SH EXAMPLE
|
|
.PP
|