https://github.com/torxed/ftunnel

stunnel but written in Python
https://github.com/torxed/ftunnel

Last synced: about 2 months ago
JSON representation

stunnel but written in Python

• Host: GitHub
• URL: https://github.com/torxed/ftunnel
• Owner: Torxed
• License: gpl-3.0
• Created: 2019-05-21T17:32:25.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2019-05-23T13:41:42.000Z (almost 6 years ago)
• Last Synced: 2025-01-25T17:23:05.482Z (4 months ago)
• Language: Python
• Homepage:
• Size: 75.2 KB
• Stars: 1
• Watchers: 2
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# ftunnel

stunnel but written in Python..

# HOWTO

Where you're coming from:

    python ftunnel.py --source=:1337 --destination=hvornum.se:443 --http=destination

Where you're going:

    python ftunnel.py --source=:443 --destination=127.0.0.1:22 --http=source

Then simply point for instance OpenVPN towards `127.0.0.1:1337`.

This will create a transparent/passive tunnel, masking the traffic coming in on `--source` as a HTTP `POST` request while it's being transmitted between two ftunnel sessions. And the destination will extract the original traffic before sending it to it's `--destination`.

![overview](screenshot.png)

# Parameters

    --http=

      Tells ftunnel if the [incoming] data should be [unwrapped]

      or if [destination] traffic should be [wrapped] before sending.

    

    --source=[IP]<:PORT>

      Which port (and/or IP) to listen on.

    

    --destination=

      Where to relay the data passively. I say passively because the original

      data is never touched.

      

    --pem=[./*.pem|/etc/ftunnel/*.pem]

      Supply a custom key & cert pair (pem format for now)

      TODO: Just generate one in runtime if one ain't supplied.

    

    --verbose

    --verbosity=3

      Manages the level of logging and if printing output to terminal

      should be enabled or not (default off).

# TODO:

 * Get it working with OpenSSH

 * Get it working with webservers behind the destination

There's something dodgy with session-based sockets.

OpenVPN for instance works fine, just not if the sockets expects

to be closed every now and then.