Add soms user scenario samples please

[jpillora]

Add soms user scenario samples please

[jpillora]

Yep this is a good suggestion, will update the readme at some point :)

[hanscees]

However, if I read this : http://www.thegeekstuff.com/2013/11/reverse-ssh-tunnel/

One should be able to tunnel a shell from a lan behind a firewall to internet over 443 or 80.

First layer would be to use a reverse ssh tunnel to a remote server, that is just sitting there waiting

Using ssh -fN -R 7000:localhost:22 username@yourMachine-ipaddress
as explained in the url above

Second layer would be to tunnel the port 22 traffic over chisel using port 80 or 443

That would result in a host on internet, you can use to get a shell on a desktop/server in a network behind a firewall.

1- server on lan (machine A) connects to internet over ssh, over http, to an internet ssh host (machine B)
2- from your home (machine C) you connect to machine B. There you can connect to machine A.

Voila. But could that work?

[hanscees]

If you jpillora can confirm this could work, I can built and document it and write a blog on it.
All you have to do than is make a link.

[MatejKovacic]

I tried chisel and (client) installation is really easy. Also, the idea is awesome. However, I would like to use it on my own server. And on my server I already have HTTPS website.

As I understand, for chisel server you have to define host and port. But on my host (let's say myhost.org) at port 443 I already have a webserver running. So as I understand, I cannot run chisel on the same port as my webserver is already running. Is that true?

Anyway, I see that chisel server has an option --proxy.

My next question is then: how I can perform the proxying? Because I have an HTTPS-only website, this means all HTTP requests are redirected to HTTPS automatically.

So one option would be:

1. run chisel on port 80 with proxy set to localhost:8080.
2. run Nginx on localhost:8080 with auto redirection to 443
3. run Nginx also on 443.

In that case:

• if user come to HTTPS with web browser, he will get HTTPS website;
• if user come to HTTP with web browser, he will be redirected to HTTPS website;
• if user come to HTTP with chisel, he will get connection to chisel server.

But could there been another option?

1. run Nginx on port 80 with auto redirection to 443
2. run Nginx also on localhost:4443.
3. run chisel on 443 with proxy set to Nginx on localhost:4443

In that case:

• if user come to HTTP with web browser, he will be redirected to 443 port;
• if user come to 443 port with web browser, he will be proxyed to 4443 port and will get HTTPS website;
• if user come to 443 port with chisel, he will get connection to chisel server.

So, my question is, is that scenario possible?

An my next question is... Nginx can be used as a WebSocket proxy. In that case, Nginx "creates" a tunnel between a client and a backend server. Is it possible that backend server would be chisel? That would mean that client should connect to a specific URL, for instance https://myserver/websocket and from this location there will be tunnel established to let's say localhost:8080, where chisel would be listening.

That is possible?