stealth 4.01.04-1 source package in Ubuntu

Changelog

stealth (4.01.04-1) unstable; urgency=medium

  * New upstream release streamlines the installation procedure

  * Adapted debian/rules so that the user guide and comparable documentation
    is installed in stealth-doc*.deb 

 -- Frank B. Brokken <email address hidden>  Thu, 24 Dec 2015 13:04:39 +0100

Upload details

Uploaded by:
Frank B. Brokken
Uploaded to:
Sid
Original maintainer:
Frank B. Brokken
Architectures:
any all
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe admin

Downloads

File Size SHA-256 Checksum
stealth_4.01.04-1.dsc 2.1 KiB fb996daa4e5dd095daed0e758f378fa442575d1622238d377db69ef98a3f6f48
stealth_4.01.04.orig.tar.gz 190.5 KiB 342720c7a3ecfcab8b8c7311dd65ca682fb77e4effe30db557f29b898a4f8976
stealth_4.01.04-1.debian.tar.xz 9.0 KiB 66c249579bf2289a61833df1cc3af374789d58249a432c9198b1b138b9661b00

Available diffs

No changes file available.

Binary packages built by this source

stealth: stealthy File Integrity Checker

 The 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, clients will hardly contain any indication suggesting 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 sha1sum(1)). Using individualized policy files, it is
 highly adaptable to the specific characteristics 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 necessary requirements for the desired
 integrity check.
 .
 STEALTH itself must communicate with the computers it should monitor. It is
 essential that this communication is secure. STEALTH configurations
 therefore normally specify SSH as the command-shell to use for connecting to
 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 is commonly allowed to send e-mail to remote
 client systems' 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.

stealth-dbgsym: debug symbols for package stealth

 The 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, clients will hardly contain any indication suggesting 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 sha1sum(1)). Using individualized policy files, it is
 highly adaptable to the specific characteristics 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 necessary requirements for the desired
 integrity check.
 .
 STEALTH itself must communicate with the computers it should monitor. It is
 essential that this communication is secure. STEALTH configurations
 therefore normally specify SSH as the command-shell to use for connecting to
 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 is commonly allowed to send e-mail to remote
 client systems' 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.

stealth-doc: stealthy File Integrity Checker documentation

 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.