Needed a simple way to tunnel SSH connection over HTTPS recently.

It should be trivial, but internets somehow mostly care about sharing SSH and HTTPS on the same port. Or do $ANY over SSH.

I wanted to completely hide the fact that I use SSH protocol. AFAIU it's easy to detect by looking at the headers.

Tunneling is supposed to be trivial but has a few caveats. Here is my attempt:

https://trofi.github.io/posts/295-ssh-over-https.html

#socat #howto #ssh #https

Update: I *finally* located the post that to me best summarizes the philosophy in question: https://queue.acm.org/blogposting.cfm?id=673 (this is the ACM repost, appropriately enough). Cc @bcantrill @ahl

#GDB #gdbserver #DTrace #Unix #socat #ssh #Eclipse #Linux

Interesting: socat can listen on two ports (1). First, it listens on the first provided port (2), where you can connect to (3). Then it listens on the second provided port (4), where you also can connect to (5). You can then send data between these clients, e.g.from the first client (6) to the second client (7) or vice versa.

The same works via TLS, UDP, IPv6, Unix Sockets, etc.

This can be useful if you want to connect two clients which can't talk to each other directly via another external accessible system.

#socat #networking #pentesting

What the Shell? - I have just completed this room! Check it out: https://tryhackme.com/room/introtoshells #tryhackme #shells #netcat #socat #metasploit #msfvenom #windows #linux #fundamentals #MuirlandOracle #Introductory #introtoshells via @RealTryHackMe

quicktip #8: A simple tcp relay with socat.

#linux #netcat #socat #proxy

quicktip #8: a simple tcp relay with socat.

#linux #network #socket #socat #netcat

#debian #socat #readline #говно @rf @ua
‰ socat /tmp/printer readline
2022/11/26 21:07:12 socat[4961] E unknown device/address "readline"
дебиан это унижение
дистрибутив для опущенцев

Been looking for a way to expose home-hosted services to the internet, and found a solution that's both geeky and fun :

1. turn your service into an #onion (https://community.torproject.org/onion-services/setup/). It's actually very quick and easy if you follow the instructions.
2. use a cheap vps to reverse-proxy requests coming from the clearnet to #tor through #socat

Is there any good reason not to do this ?

Been looking for a way to expose home-hosted services to the internet, and found a solution that's both geeky and fun :

1. turn your service into an #onion (https://community.torproject.org/onion-services/setup/). It's actually very quick and easy if you follow the instructions.
2. use a cheap vps to reverse-proxy requests coming from the clearnet to #tor through #socat

Is there any good reason not to do this ?

Hab heute mein kleines Flaschenhals #VPN #wireguard #Problem gelöst. Durch meine wilde Konstruktion den DS-Lite-Stack zu überwinden, habe ich auf einem #vServer ein #socat laufen, dass mir sämtliche UDP-Pakete auf einem bestimmten #IPv4 Port an meinen Raspi mit #IPv6 sendet. Funktioniert auch so weit. Problem: socat läuft im Userspace und performt daher unter aller sau. Erschwerend kommt hinzu, dass die Wireguard-Android-App IPv4 bevorzugt. Ich halte das für nicht so super. 🧵

Local to remote port forwarding with socat https://github.polettix.it/ETOOBUSY/2022/03/22/socat-local-to-remote-port/ #socat #networking #linux

I spent a good deal of yesterday implementing a way to copy from tmux sessions in a remote connection to my local clipboard ( #copyq, actually ). The receiving process was hanging from lack of what I thought was a EOT or some other mysterious force. I beat my head against multitudinous flat surfaces before trying #socat instead of #netcat to send the text... and there we go.

Just found out that #socat and #netcat are awesome powerful tools.