5 ms·
Docker is cool and all. Kids these days don’t know anything about Tmux and port 433. Exposing localhost to the internet and getting your internet monitored by
by biggerChris 4y ago
Docker is cool and all.
Kids these days don’t know anything about Tmux and port 433. Exposing localhost to the internet and getting your internet monitored by your ISP and getting letters in the mail; for hosting movies and Storage services.
Lol.
- aidos 4y agoWhat’s port 433? You mean 443?
- dijksterhuis 4y ago433 for those who didn't know (like me) https://en.wikipedia.org/wiki/Network_News_Transfer_Protocol https://en.wikipedia.org/wiki/Network_News_Transfer_Protocol > The Network News Transfer Protocol (NNTP) is an application protocol used for transporting Usenet news articles (netnews) between news servers, and for reading/posting articles by the end user client applications. > Well-known TCP port 433 (NNSP) may be used when doing a bulk transfer of articles from one server to another.
- jjtheblunt 4y agoon many unix variants, /etc/services lists the ports and normal uses
- biggerChris 4y agoYes. I meant port 443.
- siftrics 4y agoIf it's going over port 443, how would your ISP know you're hosting movies? The way ISPs catch you is by seeing that you're connecting to IPs that are known to host content illegally. There's now way for your ISP to know what's going _out_ of your port 443 without breaking TLS.
- jjice 4y agoThe post said 433, not 443. I read it as the HTTPS port as well at first.
- qbasic_forever 4y agoYour ISP doesn't care about what you're connecting to and accessing, at least not until they get a court order demanding that info. They care a LOT about what you're serving to other people from their network though as there might be some legal issues directed back at them.
- pixl97 4y agoYour ISP may care about what your connecting to very much, and are prepared to sell it to the highest bidder. https://arstechnica.com/information-technology/2015/03/atts-plan-to-watch-your-web-browsing-and-what-you-can-do-about-it/3/ https://arstechnica.com/information-technology/2015/03/atts-...
- pkrumins 4y agoLove your comment! Come work for me!
- koprulusector 4y agoWhat does tmux have to do with anything?
- Macha 4y agoA common deployment strategy for small scale services, especially around the 2005-2015 era, was to just copy files to your VPS, ssh in and start it up with nohup or in a screen/tmux session so it stayed running when you closed your ssh session. screen/tmux were especially helpful for stuff like irssi or minecraft servers which had a server side console you might want to return to. This was a step up for novice sysadmins/developers from "FTP to the webroot" without having to learn real deployment tools, how to write init scripts, etc. Of course it wasn't good enough for anything business critical, but I'm sure it happened there too. Also, if you then wanted to access that service from your college network, who may have gone out of their way to block gaming, a common workaround was to host it on port 443. By 2010-2015, colleges were using DPI sophisticated enough to see that "that's not http traffic" on port 80, but tended to treat 443 as "that's encrypted, must be a black box". That's how I ran mine in ~2013.
- edfletcher_t137 4y agoBack in the day we used screen because tmux didn't exist yet.
- sureglymop 4y agoAm kid, do know