How to Install and Uninstall stealth Package on Kali Linux

Last updated: May 20,2024

1. Install "stealth" package

Please follow the step by step instructions below to install stealth on Kali Linux


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                stealth
            
                    
    
    Copied

2. Uninstall "stealth" package

Learn how to uninstall stealth on Kali Linux:


    
        
            $
        

        
            
                sudo apt remove
            
                        
                stealth
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the stealth package on Kali Linux

Package: stealth
Version: 4.03.03-1
Installed-Size: 310
Maintainer: Frank B. Brokken
Architecture: amd64
Depends: libbobcat6 (>= 6.02.02), libc6 (>= 2.34), libgcc-s1 (>= 3.0), libstdc++6 (>= 11)
Suggests: stealth-doc
Size: 110600
SHA256: 32e96d6c08f962d1fde891616ee8ac92c8cab5d3f8122d168dc365974d96de08
SHA1: f9e582de535b0b07018729b8a6c5e5c4b63f2de8
MD5sum: f9daca37cd691e49526e2308d55fe438
Description: 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:
Homepage: https://fbb-git.gitlab.io/stealth
Tag: admin::logging, admin::monitoring, implemented-in::c++,
interface::commandline, interface::daemon, role::program,
security::integrity, use::checking, use::monitor
Section: admin
Priority: optional
Filename: pool/main/s/stealth/stealth_4.03.03-1_amd64.deb