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.

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 day ago

    This is like browsing /c/selfhosted as everyone portforwards every experimental piece of garbage across their router…

    • MonkeMischief@lemmy.today
      link
      fedilink
      arrow-up
      2
      ·
      17 hours ago

      portforwards every experimental piece of garbage across their router…

      Man some of those “It’s so E-Z bro” YouTubers are WAY too cavalier about doing this.

    • smiletolerantly@awful.systems
      link
      fedilink
      arrow-up
      9
      ·
      1 day ago

      Meh. Each service in its isolated VM and subnet. Plus just generally a good firewall setup. Currently hosting ~10 services plubicly, never had any issue.

      • ikidd@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 day ago

        Well, if you actually do that, bully for you, that’s how that should be done if you have to expose services.

        Everyone else there is probably DMZing their desktop from what I can tell.

    • InputZero@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 day ago

      Yeah the only thing forwarded past my router is my VPN. Assuming I did my job decently, without a valid private key it should be pretty difficult to compromise.