stealth by Frank B. Brokken (f.b.brokken@rug.nl)
stealth V2.11.04
SSH-based Trust Enhancement Acquired through a Locally Trusted Host
Copyright (c) GPL 2005-2014
Usage 1:
stealth options policy
Where:
options: (long options between parentheses) select from:
-c: (--parse-config-file) process the config file,
no further action, report the results to std output.
-d: (--debug) write debug messages to std error
-e: (--echo-commands) echo commands to std error when they
are processed (implied by -d)
-h (--help): show this usage info
-i <interval>[m]: (--random-interval) start the scan between now and
a random interval of interval seconds, or minutes if an `m' is
appended to the specified interval.
Requires --repeat and --keep-alive.
-n: (--no-child-processes) no child processes are
executed: child actions are faked to be OK.
-o: (--only-stdout) scan report is written to stdout. No mail is sent.
-q: (--quiet) suppress progress messages to stderr.
-r <nr>: (--run-command) only run command <nr> (natural number).
-s <skipfiles>: (--skip-files) skip the integrity checks of
files having their absolute path names listed in the file
'skipfiles'
-v: (--version): display version information (and exit).
--keep-alive pidfile: keep running as a daemon, wake up at interrupts.
--max-size <size>[BKMG]: files retrieved by GET may at most
have <size> bytes (B), Kbytes (K), Mbytes (M), Gbytes (G)
default: 10M, default spec. unit: B
--repeat <seconds>: keep running as a daemon, wake up at
interrupts. or after <seconds> seconds.
Requires --keep-alive.
--usage: provide this help (and exit)
--help: provide this help (and exit)
policy: path to the policyfile
Usage 2:
stealth {--reload,--rerun,--resume,--suppress,--terminate} pidfile
Where:
--reload: reload a stealth process's configuration files
--rerun: restart a stealth integrity scan
--resume: resume stealth following --suppress
--suppress: suppress stealth activities
--terminate: terminate stealth
pidfile: file containing the pid of the stealth process to rerun or
terminate.
Note that with the second type of usage the policy file is not required:
here only the pidfile must be specified.