888 888 .:^^^^:. 888 .:^: :^:. 88888b. .d88b. 888 888 88888b. .d88b. .d8888b .d88b. :^: :^: 888 "88b d8P Y8b `Y8bd8P' 888 "88b d88""88b 88K d8P Y8b :^: 0x :^: 888 888 88888888 X88K 888 888 888 888 "Y8888b. 88888888 :^: :^: 888 888 Y8b. .d8""8b. 888 d88P Y88..88P X88 Y8b. ':^: :^:' 888 888 "Y8888 888 888 88888P" "Y88P" 88888P' "Y8888 ':^^^^:' 888 888 888 h e x p o s e self-hosted tunnels, over plain ssh Usage: $ ssh -p 9999 -R0:localhost:5000 h.0x7359.com [+] https://<id>.h.0x7359.com [i] Anyone with that URL reaches your local :5000, over HTTPS. $ ssh -p 9999 -R0:localhost:22 tcp@h.0x7359.com [+] h.0x7359.com:<port> [i] Raw TCP: netcat, ssh, databases, anything that is not HTTP. $ ssh -p 9999 -R0:localhost:5000 qr@h.0x7359.com [i] Same as the first, plus a QR code in your terminal. $ ssh -p 9999 -R0:localhost:5000 -L4300:localhost:4300 h.0x7359.com [i] Adds a live request inspector at http://localhost:4300 ----------------------------------------------------------------------- Options: go in the username, '+'-separated: tcp+qr@h.0x7359.com Fixed subdomain: sub-blog@h.0x7359.com Access: tunnels need a token — ask the operator: TOKEN@h.0x7359.com Closing: Ctrl-C, or just close the ssh session No client: nothing to install; your ssh already does all of this