stealth 2.11.03-2 source package in Ubuntu


stealth (2.11.03-2) unstable; urgency=low

  * Add patch for FTBFS with bobcat 3.17.00.  (Closes: #729302)
    - Thank you to Andreas Moog.
  * Bump Standards-Version to 3.9.5 (no changes).

 -- tony mancill <email address hidden>  Mon, 11 Nov 2013 19:41:47 -0800

Upload details

Uploaded by:
Frank B. Brokken
Uploaded to:
Original maintainer:
Frank B. Brokken
any all
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Trusty release universe admin


File Size SHA-256 Checksum
stealth_2.11.03-2.dsc 2.1 KiB 0de25f8141c05aa2eb90a8ad401c39aab1a77ec6158d073f6e88804a9e282fe4
stealth_2.11.03.orig.tar.gz 92.2 KiB 56592a9ad1c1c3d4a92721ef7dd44307daa14185c7c3c8b036a22b9723c7a9ad
stealth_2.11.03-2.debian.tar.gz 9.3 KiB 8e71bfda6a8e59330f367f82990a8df9d191676e12d8123f3058d891a037359d

No changes file available.

Binary packages built by this source

stealth: No summary available for stealth in ubuntu utopic.

No description available for stealth in ubuntu utopic.

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
 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
 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.