• 4 Posts
  • 268 Comments
Joined 1 year ago
cake
Cake day: April 27th, 2024

help-circle




  • Good news! I am doing something! I’m an active part of a vehemently anti-fascist party in my country! And I’m proud to say that we’ve been passing actually progressive legislation and being the stop-block against a slide right.

    How about yourself? Have you actually done anything besides shitposting?

    If you’d fight in the revolution, but not fight in the revolution and cast a vote, I seriously question your commitment to the fighting-in-the-revolution part.



  • Whenever I read a comment such as yours, I get the distinct impression that you actually relish the thought of causing suffering.

    You self-glorify through the thought of “Well I did not support this system! If everyone was like me, this would all be solved!” - it’s so easy, right? All those people experiencing additional suffering because you are too lazy to cast a vote sure are grateful to you for sticking to your principals, heroically practicing non-participation in a system built on suffering by… furthering that suffering. Hey, wait a minute!

    I don’t even know why I am writing all this out. Chances are you are either a troll, a bot, or simply so deeply misguided that nothing I say could possibly reach you.

    At some level though, you must know that making it easier for fascists to seize power actively hurts what you claim to stand for. You could always move the needle a little by voting, and still do whatever you believe needs doing beyond that; those are not mutually exclusive.








  • TBH, it sounds like you have nothing to worry about then! Open ports aren’t really an issue in-and-on itself, they are problematic because the software listening on them might be vulnerable, and the (standard-) ports can provide knowledge about the nature pf the application, making it easier to target specific software with an exploit.

    Since a bot has no way of finding out what services you are running, they could only attack caddy - which I’d put down as a negligible danger.


  • My ISP blocks incoming data to common ports unless you get a business account.

    Oof, sorry, that sucks. I think you could still go the route I described though: For your domain example.com and example service myservice, listen on port :12345 and drop everything that isn’t requesting myservice.example.com:12345. Then forward the matching requests to your service’s actual port, e.g. 23456, which is closed to the internet.

    Edit: and just to clarify, for service otherservice, you do not need to open a second port; stick with the one, but in addition to myservice.example.com:12345, also accept requests for otherservice.example.com:12345, but proxy that to the (again, closed-to-the-internet) port :34567.

    The advantage here is that bots cannot guess from your ports what software you are running, and since caddy (or any of the mature reverse proxies) can be expected to be reasonably secure, I would not worry about bots being able to exploit the reverse proxy’s port. Bots also no longer have a direct line of communication to your services. In short, the routine of “let’s scan ports; ah, port x is open indicating use of service y; try automated exploit z” gets prevented.


  • I am scratching my head here: why open up ports at all? It it just to avoid having to pay for a domain? The usual way to go about this is to only proxy 443 traffic to the intended host/vm/port based on the (sub) domain, and just drop everything else, including requests on 443 that do not match your subdomains.

    Granted, there are some services actually requiring open ports, but the majority don’t (and you mention a webserver, where we’re definitely back to: why open anything beyond 443?).