Ubuntu
stealth package

stealth 2.02.01-3 source package in Ubuntu

Changelog

stealth (2.02.01-3) unstable; urgency=low

  * Build-Depend on g++ >= 4:4.6.0, better support for c++0x.
    (fixes ftbfs with older compilers on some architectures)
 -- Ubuntu Archive Auto-Sync <email address hidden>   Tue,  28 Jun 2011 10:03:02 +0000

Upload details

Uploaded by:
Ubuntu Archive Auto-Sync
Uploaded to:
Oneiric
Original maintainer:
Frank B. Brokken
Architectures:
any
Section:
admin
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Precise release universe admin

Downloads

File Size SHA-256 Checksum
stealth_2.02.01.orig.tar.gz 97.4 KiB ea4cd9ea2d213a7fa2eb4714477091fff46acaf6e787734f6729b03ed18283e2
stealth_2.02.01-3.debian.tar.gz 8.8 KiB f81550e82fed71c745e4b492bd54726dd05d02d723c108588356b03eff38c213
stealth_2.02.01-3.dsc 2.0 KiB d3aa06309e87cd839dfb879c0b9434bdbb00c182821ce10d008c80269db7ef9c

Available diffs

View changes file

Binary packages built by this source

stealth: No summary available for stealth in ubuntu quantal.

No description available for stealth in ubuntu quantal.

stealth-doc: stealthy File Integrity Checker

 STEALTH program performs File Integrity Checks on (remote) clients. It
 differs from other File Integrity Checkers by not requiring baseline
 integrity data to be kept on either write-only media or in the client's file
 system. In fact, client's will contain hardly any indication at all that they
 are being monitored, thus improving the stealthiness of the integrity scans.
 .
 STEALTH uses standard available software to perform file integrity checks
 (like find(1) and md5sum(1)). Using individualized policy files, it is highly
 adaptable to the specific requirements of its clients.
 .
 In production environments STEALTH should be run from an isolated computer
 (called the `STEALTH monitor'). In optimal configurations the STEALTH
 monitor should be a computer not accepting incoming connections. The account
 used to connect to its clients does not have to be `root': usually
 read-access to the client's file system is enough to perform a full integrity
 check. Instead of using `root' a more restrictive administrative or
 ordinary account might offer all requirements for the desired integrity
 check.
 .
 STEALTH itself must communicate with the computers it should monitor. It is
 essential that this communication is secure, and STEALTH configurations will
 therefore normally specify SSH as the command-shell to use to connect to its
 clients. STEALTH may be configured so as to use but one SSH connection per
 client, even if integrity scans are to be performed repeatedly. Apart from
 this, the STEALTH monitor might be allowed to send e-mail to remote clients
 system's maintainers.
 .
 STEALTH-runs itself may start randomly within specified intervals. The
 resulting unpredicability of STEALTH-runs further increases STEALTH's
 stealthiness.
 .
 STEALTH's acronym is expanded to `Ssh-based Trust Enforcement Acquired
 through a Locally Trusted Host': the client's trust is enforced, the locally
 trusted host is the STEALTH monitor.
 .
 This package provides the supplemental documentation for Stealth.