RFC
RFC (Remote Filesystem Checker) is a set of scripts that aims to help system administrators run a filesystem checker (like tripwire, aide, etc.) from a "master-node" to several "slave-nodes" using ssh, scp, sudo, and few other common shell commands.
| Tags | Security Filesystems Monitoring Systems Administration |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX |
| Implementation | Unix Shell |
Recent releases
- 17 Nov 2005 14:55
Changes: A new function that replaces the "seq" command, which is not available on all systems. A fix for a small bug that caused a "cp: missing destination file" error. A fix for an error that caused RFC to suggest a bad "sudo" setup. A new function to check whether a node is alive without the "nmap" requirement. "/lib" is included in all default configuration files for the filesystem checkers (afick, aide, and integrit). AFICK has been updated to version 2.8-2. The documentation reflects the latest changes.
- 29 Aug 2004 08:46
Changes: In this release, afick has been updated to version 2.3-1, there is an explicit requirement for "wc". Most importantly, you can finally choose an arbitrary port for SSH/SCP connections, and this port can be different for each host that RFC will check.
- 10 May 2004 11:07
Changes: AFICK is updated to version 2.1-0, but the most important thing is that this release has a better email report that will only show hosts where differences are found. This way, the report will be very short even for people running RFC on many hosts.
- 04 Mar 2004 03:09
Changes: The program now really honours $PROC (which specifies the number of parallel process to run) on fast systems. A string checking problem was corrected. Processes can now be killed if they take too long to run.
- 27 Feb 2004 13:49
Changes: This release may not run in interactive mode. It can perform a mass check/update for all nodes, set up some options from the command line, and send an alert to a different email address. It does not require an "rfc" user to run on master/slaves, so anyone but root can run it, and you can chose a different user on each remote node. It can check a single node, does not use multiple SSH connections to remove files, and clears files on the remote host. The documentation has been updated and some small bugs have been fixed.
