exposer

Expose your services without public ip!

TL;DR

Exposer allows to expose your local/hidden services in the internet. The only requirement is to have internet connection, and from your host the host that you are exposing must be available.

So for example - you have your device/soft that is exposing port 80, but you have no public ip on this device/can't share cause of hard router configuration, etc.

With exposer you can forward your traffic over tunnel between server and client. So any request to remote port will be forwarded to listening client. Simple, right? Of course this is not my solution - this is builded in SSH.

This is based on pure ssh, i think that it resolving lot of problem and i've decided to make this open source.

Somebody noticed me, that there is similiar service - https://ngrok.com/

Server usage

Server is just containerized sshd server with enabled port forwarding. On your server you can make the container with command:

docker run -p 8080:22 -p 80:9999 --restart=always --name exposerserver -e PASSWORD=supersecretpassword -d razikus/exposerserver:1.0

This will expose your exposerserver on ssh port 8080 and port 80 from inside port 9999 with password supersecretpassword. Your server should be public if you want to public expose ports. Any client can connect now.

Client usage

Let's assume, that server ip was 53.53.53.53

docker run --network=host -e PASSWORD=supersecretpassword -e SERVER=exposer@53.53.53.53 -e SSHPORT=8080 -e REMOTEPORT="\*:9999" -e FROM=localhost -e FROMPORT=8081 --restart=always -d razikus/exposerclient:1.0

This will try to expose service localhost:8081 from your network to public server 53.53.53.53 on port 9999. But 9999 was exposed to 80 in server container so the real exposure will be 53.53.53.53:80. Of course you can adjust it on what you want.

More cases in client examples.

How this works?

Client have internet connection, so this is enough to make 2-way connection - any request will be forwarded by tunnel.

Example usage - "SSH TeamViewer"

Maybe not exactly, but it's absolutely doable with gotty. Of course - this is not really secure, but you can always forward it to your own service, not exposer.eu

docker run -p 80:8080 -e username=admin -e password=supersecretpassword -e gottyentry=/bin/ash -v /:/mounted -d --name gotty razikus/gotty:2.0.0-alpha.3

This will create gotty instance (terminal over http), volume your root / to /mounted (so you can access it from web)

Next go to http://exposer.eu/superssh/80/localhost You will get docker command to expose your localhost:80

In my case that was

docker run --name tunneler -e KEY="akFhSXJtU2FxcEpPYW9tZ0dZUnA7Kjo5OTk5O2xvY2FsaG9zdDs4MDtleHBvc2VyQHRlc3QyLmV4cG9zZXIuZXU7MzI4OTk=" --network=host --rm -d razikus/exposerclient:1.0

Execute it, and... That's it. My service was exposed to superssh.exposer.eu, then log with admin supersecretpassword

Tadaam

exposer.eu usage

Ups not working anymore

ARM support

From now also supporting ARM (builded on RaspberryPi 3).

Instead of razikus/exposerclient:1.0 use razikus/exposerclient:1.0-arm.

Instead of razikus/exposerserver:1.0 use razikus/exposeserver:1.0-arm.

Who is using this?

For example me, my company and my devices Skryba-1 (time and attendance registrator). So every client can just provide the key that i'm selling, and device will be exposed in the internet.