• nbailey@lemmy.ca
    link
    fedilink
    English
    arrow-up
    28
    ·
    2 months ago

    Anybody who’s ever exposed any service to the internet knows this as the “background radiation” of the net. My boxes get thousands of random connection attempts per day. The best practice for years has been to use keypairs and/or VPNs. Friends don’t let friends expose RDP to the web.

    • lost_faith@lemmy.ca
      link
      fedilink
      English
      arrow-up
      12
      ·
      2 months ago

      I had a little linux server years ago and after a setup forgot to change my SSH port. One day I noticed my network was slow and after poking around realized that I had someone knocking at my port trying pass after pass with like 15 - 30 sec between attempts, watched this person for 2 days laughing at the 8-10 char passwords they were using, my password was a sentence. I then shifted the port to the 30k range and all was silent on my ports, always remember to change default ports, fun times

    • WolfLink@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      I had a website exposed to the net and would constantly get http requests for things like “wordpress_admin.js”

    • Darkassassin07@lemmy.ca
      link
      fedilink
      English
      arrow-up
      14
      ·
      2 months ago

      There’s a few ways to do it; but if they block based on username it can lockout legitimate users too.

      This is what fail2ban is for. Too many failed auths from an IP and that whole IP is blacklisted for a day or two. This can still catchout vpn users, but it’s still less disruptive.

      • HubertManne@kbin.social
        link
        fedilink
        arrow-up
        8
        ·
        2 months ago

        Many blocked for an hour or even just 10 mins. at the time it was enough to get the attack scripts to change targets.

      • SemiAuto@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 months ago

        I went a bit overboard I think with my fail2ban configuration. If you fail 2 times to login in any admin interfaces (ssh, web, etc), you get banned for around 4880 days… I have too many banned IPs already… :/

    • discozombie@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      Indeed but in this particular case they’re using a large number of IPs, over 3000 on the last list I saw.

      • HubertManne@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        yeah and im thinking from an early 2000 perspective to where not being able to login for an hour was not necessarily a big deal. Whereas now so much of our life is online its not really as laid back a proposition.

  • Socsa@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    12
    ·
    2 months ago

    This has happened to every SSH host on the internet for at least 20 years. Key based authentication is important folks.