• 1 Post
  • 36 Comments
Joined 6 months ago
cake
Cake day: April 5th, 2024

help-circle













  • hsdkfr734r@feddit.nltome_irl@lemmy.worldme_irl
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    3 months ago

    Agreed. It really supports the rantiness of the text. Also the answer is given in the first two words. All good so far.

    Clarification: I don’t say that he has to use punctuation. That’s completely up to Phuntis. It’s just hard for me to understand the text. That is the thing I wanted to state instead of just downvoting (which explains nothing). Phuntis made clear that he doesn’t want to. That’s fine.





  • One aspect is how interesting you are as a target. What would a possible attacker gain by getting access to your services or hosts?

    The danger to get hacked is there but you are not Microsoft, amazon or PayPal. Expect login attempts and port scans from actors who map out the internets. But I doubt someone would spend much effort to break into your hosts if you do not make it easy (like scripted automatic exploits and known passwords login attempts easy) .

    DDOS protection isn’t something a tiny self hosted instance would need (at least in my experience).

    Firewall your hosts, maybe use a reverse proxy and only expose the necessary services. Use secure passwords (different for each service), add fail2ban or the like if you’re paranoid. Maybe look into MFA. Use a DMZ (yes, VLANs could be involved here). Keep your software updated so that exploits don’t work. Have backups if something breaks or gets broken.

    In my experience the biggest danger to my services is my laziness. It takes steady low level effort to keep the instances updated and running. (Yes there are automated update mechanisms - unattended upgrades i.e. -, but also downwards compatibility breaking changes in the software which will require manual interactions by me.)