How to Install and Uninstall sniproxy Package on Ubuntu 21.10 (Impish Indri)

Last updated: May 17,2024

1. Install "sniproxy" package

Please follow the guidance below to install sniproxy on Ubuntu 21.10 (Impish Indri)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                sniproxy
            
                    
    
    Copied

2. Uninstall "sniproxy" package

Here is a brief guide to show you how to uninstall sniproxy on Ubuntu 21.10 (Impish Indri):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                sniproxy
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the sniproxy package on Ubuntu 21.10 (Impish Indri)

Package: sniproxy
Architecture: amd64
Version: 0.6.0-2
Priority: optional
Section: universe/web
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Jan Dittberner
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 126
Depends: lsb-base, init-system-helpers (>= 1.51), libc6 (>= 2.14), libev4 (>= 1:4.04), libpcre3, libudns0 (>= 0.4)
Recommends: logrotate
Filename: pool/universe/s/sniproxy/sniproxy_0.6.0-2_amd64.deb
Size: 39828
MD5sum: 9bac997148012ef05f9f435142cc6617
SHA1: d9f6a9531a9a3f7538a3c205e5e6dc7aad337536
SHA256: 00f8eabb8c58933df743dc2acea1120bb25d1d290efa722a9c6f23540c821032
SHA512: 6ee6ebb372b13c588f06880df91a7550b5faec55b268faee99fbec799e15bb7feeb6e20cf7d7ac3cd9fce2e4314548dc1ce58fd260d7ca4457d0d8e2a92c9eb7
Homepage: https://github.com/dlundquist/sniproxy
Description-en: Transparent TLS and HTTP layer 4 proxy with SNI support
Proxies incoming HTTP and TLS connections based on the hostname contained in
the initial request of the TCP session. This enables HTTPS name-based virtual
hosting to separate backend servers without installing the private key on the
proxy machine.
Description-md5: 4124f85582aa6704d623bae64e3ff35f