Skip to content

SNI Injector TCP over SSL Tunnel - python alternative HTTP Injector for Windows/Linux

License

Notifications You must be signed in to change notification settings

kirula0626/SNI_Injector

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

26 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SNI Injector TCP over SSL Tunnel - python alternative HTTP Injector for Linux & Windows

What is SNI?

Server Name Indication (SNI) is an extension to the Transport Layer Security (TLS) computer networking protocol by which a client indicates which hostname it is attempting to connect to at the start of the handshaking process.This allows a server to present one of multiple possible certificates on the same IP address and TCP port number and hence allows multiple secure (HTTPS) websites (or any other service over TLS) to be served by the same IP address without requiring all those sites to use the same certificate Read more

What is SNI BUG Host

SNI bug hosts can be in various forms. They can be a packet host, a free CDN host, government portals, zero-rated websites, social media (subscription), and a variety of other sites. They also do a fantastic job of getting over your Internet service provider's firewall.

If you have a subscription to zoom.us and want to visit Zoom, your ISP's firewall will scan every time your SSL handshake to determine if the SNI is "zoom.us", and if it does, the firewall will enable you to keep that connection free fo charge. When you have a subscription to access internet, this is what happens.

What if we can modify our SNI and gain access to different sites? Yes! we can. However, SNI verification will fail, and the connection will be terminated by host. But we still can use our own TLS connection(with changed SNI) and use a proxy through it access the internet.

Server Side

  1. Open Ports :

    • Ensure that ports 22 and 443 are open on your server.
  2. Install stunnel :

    sudo apt-get install stunnel4 -y
  3. Create stunnel.conf File

    • Navigate to the /etc/stunnel directory and create the stunnel.conf file :
      sudo nano /etc/stunnel/stunnel.conf
  4. Edit stunnel.conf

    • Add the following configuration to stunnel.conf :
      client = no
      [stunnel]
      accept = 443
      connect = 127.0.0.1:22
      cert = /etc/stunnel/stunnel.pem
  5. Create SSL Certificates :

    • Generate an SSL certificate file (stunnel.pem) and place it in the /etc/stunnel directory.
      openssl genrsa -out key.pem 2048
      openssl req -new -x509 -key key.pem -out cert.pem -days 1095
      cat key.pem cert.pem >> /etc/stunnel/stunnel.pem
  6. Restart stunnel :

    /etc/init.d/stunnel4 restart

    Source : How To Set Up an SSL Tunnel Using Stunnel

Linux

Client Side

  1. Clone the repository :

    git clone https://github.com/kirula0626/sni-injector.git
  2. Add your SNI host and ssh host to settings.ini :

    [ssh]
    #Host must be your Server Public IP address
    #example host = 10.29.22.33
    host = [SERVER_PUBLIC_IP]
    
    [sni]
    #example server_name = facebook.com
    server_name = <SNI>
  3. Install the Requirements :

    • To Requirements need python and pip
      pip install -r requirements.txt
  4. Edit the ssh_tunnel.sh Script :

    • Auto login and manual login. Uncomment wanted method.
      #-Auto login with password
      #sshpass -p [SERVER_SSH_PASSWORD] ssh -C -o "ProxyCommand=nc -X CONNECT -x 127.0.0.1:9092 %h %p" [SERVER_USERNAME]@[SERVER_PUBLIC_IP] -p 443 -v -CND 1080 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
      #-Manual login
      #ssh -C -o "ProxyCommand=nc -X CONNECT -x 127.0.0.1:9092 %h %p" [SERVER_USERNAME]@[SERVER_PUBLIC_IP] -p 443 -CND 1080 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
    • For Auto login need sshpass tool :
      apt-get install sshpass
  5. Run ssh_tunnel.shscript

  6. Install Proxychains :

    apt-get install proxychains4
    • Edit proxychains conf file :
      sudo nano /etc/proxychains4.conf
    • At the end, add this line :
      socks5  127.0.0.1 1080
  7. Check Proxychains :

    proxychains4 curl ifconfig.me
    • output must be Public Server IP
  8. Use :

    1. Active proxy on Browser : Add SOCKS Host : 127.0.0.1 Port : 1080 and Select SOCKSv5

    or

    1. Open using proxychains4 :
    proxychains4 firefox

Windows

Client Side

  1. Clone the repository :

    git clone https://github.com/kirula0626/sni-injector.git
  2. Add your SNI host and ssh host to settings.ini :

    [ssh]
    #Host must be your Server Public IP address
    #example host = 10.29.22.33
    host = [SERVER_PUBLIC_IP]
    
    [sni]
    #example server_name = facebook.com
    server_name = <SNI>
  3. Install the Requirements :

    • To Requirements need python and pip
      pip install -r requirements.txt
  4. Install Nmap :

  5. Auto / Manual Method :

    1. Manual Method
      1. Run `socks5_tunnel.py' file :
        python socks5_tennel.py
      2. Run ssh :
        • Windows don't have sshpass. Manual Method using ssh. To establish connection type [SERVER_SSH_PASSWORD]
          ssh -C -o "ProxyCommand=ncat --verbose --proxy 127.0.0.1:9092 %h %p" [SERVER_USERNAME]@[SERVER_PUBLIC_IP] -p 443 -CND 1080 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
      or
    2. Automation Method :
      • Create ssh key-pair.
      1. Create client side ssh key-pair.
        ssh-keygen -t rsa
      2. Copy to rsa public key to serve's authorized_keys
        scp C:\Users\[CLIENT_USER]\.ssh\id_rsa.pub [SERVER_USERNAME]@[SERVER_PUBLIC_IP]:/home/[SERVER_USER]/.ssh/authorized_keys
      3. New user must enter [SERVER_USERNAME] and [SERVER_PUBLIC_IP] to prompt. It will save for future logins.
        ssh_tunnel.exe

6.Use :

  • Active proxy on Browser (firefox) : Add SOCKS Host : 127.0.0.1 Port : 1080 and Select SOCKSv5
    or
  • Add socks5 to Windows
  • Control Panel --> Network and Internet --> Internet Options --> Connection Tab
  • Lan Settings --> Inside Proxy Server Tik the radio box --> Advanced
  • socks : 127.0.0.1 : 1080 --> Ok

    Tip : If you not using proxy make sure to untik Inside Proxy Server radio box

Releases

No releases published

Packages

No packages published