Ubuntu
stealth package

stealth 4.03.03-1 source package in Ubuntu

Changelog

stealth (4.03.03-1) unstable; urgency=medium

  [ Frank B. Brokken ]
  * New upstream version 4.03.03-1
  * debian/rules sources C++ version from 'c++std' file
  * Removed 'debian/patches/hyperref-ftbfs.patch': the unusable
    '\usepackage[...]{hyperref} was removed upstream

  [ tony mancill ]
  * Remove debian/NEWS file; it referred to a release from 2008

 -- tony mancill <email address hidden>  Mon, 14 Nov 2022 21:11:08 -0800

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
Oracular release universe admin
Noble release universe admin
Mantic release universe admin
Lunar release universe admin

Downloads

File Size SHA-256 Checksum
stealth_4.03.03-1.dsc 2.2 KiB 7af0e8b2ea95c48597ff3b5051a1620ea54c5b1b5c5192a6a2561e13ed2beff5
stealth_4.03.03.orig.tar.gz 192.3 KiB 199381bdaf6efa23f7b29b6b12ebb3d19def97d3a51b33986272c78c46ac8538
stealth_4.03.03-1.debian.tar.xz 10.2 KiB 0b0bcdc65bca0553ebb4a719442803d12dafa5042ad1638c84467eb6a4a0674f

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