Background: 15 years of experience in software and apparently spoiled because it was already set up correctly.

Been practicing doing my own servers, published a test site and 24 hours later, root was compromised.

Rolled back to the backup before I made it public and now I have a security checklist.

    • Tablaste@linux.communityOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      3 months ago

      I published it to the internet and the next day, I couldn’t ssh into the server anymore with my user account and something was off.

      Tried root + password, also failed.

      Immediately facepalmed because the password was the generic 8 characters and there was no fail2ban to stop guessing.

      • lud@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Don’t use passwords for ssh. Use keys and disable password authentication.

        • Voroxpete@sh.itjust.works
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          3 months ago

          More importantly, don’t open up SSH to public access. Use a VPN connection to the server. This is really easy to do with Netbird, Tailscale, etc. You should only ever be able to connect to SSH privately, never over the public net.

          • troed@fedia.io
            link
            fedilink
            arrow-up
            1
            ·
            3 months ago

            It’s perfectly safe to run SSH on port 22 towards the open Internet with public key authentication only.