How to Install and Uninstall stealth Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: December 24,2024

1. Install "stealth" package

Here is a brief guide to show you how to install stealth on Ubuntu 20.10 (Groovy Gorilla)

$ sudo apt update $ sudo apt install stealth

2. Uninstall "stealth" package

This guide covers the steps necessary to uninstall stealth on Ubuntu 20.10 (Groovy Gorilla):

$ sudo apt remove stealth $ sudo apt autoclean && sudo apt autoremove

3. Information about the stealth package on Ubuntu 20.10 (Groovy Gorilla)

Package: stealth
Architecture: amd64
Version: 4.02.00-3
Priority: optional
Section: universe/admin
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Frank B. Brokken
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 300
Depends: libbobcat5 (>= 5.02.00), libc6 (>= 2.14), libgcc-s1 (>= 3.0), libstdc++6 (>= 9)
Suggests: stealth-doc
Filename: pool/universe/s/stealth/stealth_4.02.00-3_amd64.deb
Size: 95444
MD5sum: 0532b8d464e823316bb1a4d0e720e515
SHA1: 67a86ce41cd1fdbf3b0223a19108b7c08f12cca9
SHA256: 447ed18f953bb7365fe7fc25943e1603328c00445d7cb50896e6cd3e3f8c88a5
SHA512: 72dd378aa11fd3cbc04fa2da709a35cbc1e2484f856eeb0796b6286f2aed702a9818e19cc51e61753e971733b750c625cd9bb6fddaccc76eb6c3cd30784a2386
Homepage: https://fbb-git.gitlab.io/stealth
Description-en: 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.
Description-md5: 5bc700bb5b7b5d6ee7d8fdc9665b6a25