tani/hyper-tunnel

HTTPS tunnel over WSS

hyper-tunnel

hyper-tunnel is HTTPS tunnel over WSS

Introduction

In the meetup and other situations, we have to expose our localhost to host demo-application avoid Firewall for other participants. Generally, this is worst way. Tunneling over HTTP have risks by MITM. For this reason, almost services provide tunnels over End-to-End SSL/TLS in paid plan. This project is a simple toolkit to make HTTP tunneling over End-to-End SSL/TLS by WSS (WebSocketSecure). hyper-tunnel works on the following route.

web browser <--HTTPS--> hyper-tunnel server
                              |
~~~~~~~~~~~~~~Firewall~~~~~~ WSS ~~~~~~~
                              |
  localhost <-HTTP(S)-> hyper-tunnel client

How to use

$ npm install -g tani/hyper-tunnel
$ htunnel server --authorization USERNAME:PASSWORD --port 4000
$ htunnel client --authorization USERNAME:PASSWORD --localhost localhost:8000 --remotehost localhost:4000

Now you can access localhost:4000 with browsers, and hyper-tunnel access localhost:4000. `

Related Services

• localtunnel
• ngrok
• pagekite

Copyright & License

Copryright (c) 2018 TANIGUCHI Masaya All Rights Reserved.

hyper-tunnel licensed under the GPLv3 or later.

hyper-tunnel's Issues

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (:automerge)

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency typescript to v5.4.5
• Update dependency commander to v12

Detected dependencies

dockerfile

Dockerfile

github-actions

.github/workflows/node.js.yml

• actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b
• actions/setup-node v4

npm

package.json

• circular-json ^0.5.9
• commander ^6.1.0
• ws ^8.0.0
• @types/circular-json 0.4.0
• @types/commander 2.12.2
• @types/ws 8.5.10
• tslint 6.1.3
• tslint-config-prettier 1.18.0
• typescript 5.0.4

---

• Check this box to trigger a request for Renovate to run again on this repository

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.