• 6 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle







  • lungdart@lemmy.catoSelfhosted@lemmy.worldAnother good reason not to open port 22
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    1
    ·
    11 months ago

    Moving the port doesn’t reduce attack surface. It’s the same amount of surface.

    Tailscale is a bit controversial because it requires a 3rd party to validate connections, a 3rd party that is a large target for threat actors, and is reliant on profitability to stay online.

    I would recommend a client VPN like wireguard, or SSH being validated using signed keys against a certificate authority your control, with fail2ban.


  • lungdart@lemmy.catoSelfhosted@lemmy.worldHave I been DoS'd?
    link
    fedilink
    English
    arrow-up
    25
    ·
    11 months ago

    Sounds like you were out of resources. That is the goal of a DoS attack, but you’d need connection logs to detect if that was the case.

    DDoS attacks are very tricky to defend. (Source: I work in DDoS defence). There’s two sections to defense, detection and mitigation.

    Detection is very easy, just look at packets. A very common DDoS attack uses UDP services to amplify your request to a bigger response, but then spoof your src ip to the target. So large amounts of traffic is likely an attack, out of band udp traffic is likely an attack. And large amount of inband traffic could be an attack.

    Mitigation is trickier. You need something that can handle a massive amount of packet inspection and black holing. That’s done serious hardware. A script kiddie can buy a 20Gbe/1mpps attack with their moms credit card very easily.

    Your defence options are a little limited. If your cloud provider has WAF, use it. You may be able to get rules that block common botnets. Cloudflare is another decent option, they’ll man in the middle your services, and run detection and mitigation on all traffic. They also have a decent WAF.

    Best of luck!



  • Your host sets it’s own DNS servers, if the router isn’t on the list, they don’t get pinged. Now they could try to man in the middle you, so you could try DNS over TLS, but it’s probably not your issue.

    You’re DNS server settings likely never took hold. Like if you use a DHCP client, then override your DNS settings, that won’t take effect until you request a new DHCP connection.

    Some Linux distros will have local DNS servers that you always point to which are a pain to update as well. Not sure about Windows and MAC.

    good luck man!