Live data from Hacker News

Show HN: Tunnelling TCP through a file

github.com

31–40 of 42 posts

Re: Show HN: Tunnelling TCP through a file

#34
post #18

Feature request: TCP over Facebook Messenger, TCP over Whatsapp For use on flights where they give you "messenger only" internet access. Feature request: TCP over JPEG cat pictures on HTTP port 80 It would likely do a better job at circumventing the China firewall than existing VPNs that can be flagged as VPN protocols.

> For use on flights where they give you "messenger only" internet access.

They still rate limit these flows to a very low speed.

Re: Show HN: Tunnelling TCP through a file

#35
post #8

Earlier quoted context omitted.

It looks like one file per direction, and this is a point to point connection. It looks like each side just reads to the end of the file and then tries to read more to see if any new data is available.

Yes exactly. One file in each direction made arbitration easier. In the future I will implement a single file to handle both directions.

[deleted]

Re: Show HN: Tunnelling TCP through a file

#36

That’s cool. A question that immediately comes to my mind is this: how is this different than using the Windows SMB native support for named pipes over the IPC$ share? From your example it would seem the users on both sides of the share would require the same AAA for your implementation as would be required to use IPC$ via SMB. If that is indeed the case, (I am not a Windows pr SMB expert, so perhaps you will tell me…

I wish unix domain sockets worked over NFS. It would be such a nice way to assign user-level permissions on networked services. ssh /services/gw etc. Maybe even file:/// -urls for the web browser, though the cross domain logic would need updates.

It would presume trusting the permission system over NFS, though.

Re: Show HN: Tunnelling TCP through a file

#39
post #17

reminds me how the other day I circumvented disabled SSH port forwarding by using https://github.com/nwtgck/yamux-cli + ncat already on the machine to do something like: yamux -l lport | ssh server -- .sh good thing I needed HTTP access or else i had to find that socks5 server that's actually working again.

I've been trying to read up on TCP/UDP multiplexing and I'm having a hard time understanding what the use cases are, or advantages over just using regular connections, sockets, and application logic.

Do you have a good resource recommendation to learn this more?

Post reply on HN