Next: Reporting issues, Previous: Developing, Up: Top [Contents]
You can use configuration files ${sysconfdir}/libsecrm.progban and ${sysconfdir}/libsecrm.fileban to specify which programs should LibSecRm not mess with and which files shouldn’t be wiped (partial names are enough in both files). Put each entry on its own line.
${sysconfdir} is /usr/local/etc unless set otherwise during configure.
If additional banning files haven’t been disabled (How to compile?), they can
be located in users’ home directories (e.g. /home/user1/.libsecrm.progban,
/home/user1/.libsecrm.fileban).
You can also put the file in any location and set the environment variables
LIBSECRM_PROGBANFILE
and LIBSECRM_FILEBANFILE
to point at that file, e.g.
‘export LIBSECRM_PROGBANFILE=/opt/config/libsecrm.progban’
‘export LIBSECRM_FILEBANFILE=/opt/config/libsecrm.fileban’
The /proc filesystem must be mounted in order for program banning to work right now. It is also used for checking if a file to be wiped is already opened.
You can set the environment variable LIBSECRM_ITERATIONS
to change
the number of wiping passes/iterations at run-time:
‘export LIBSECRM_ITERATIONS=5’
This affects only the programs started after setting the variable.