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.

  • Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    23
    ·
    edit-2
    24 days ago

    And this is why every time a developer asks me for shell access to any of the deployment servers, I flat out deny the request.

    Good on you for learning from your mistakes, but a perfect example for why I only let sysadmins into the systems.

      • corsicanguppy@lemmy.ca
        link
        fedilink
        English
        arrow-up
        3
        ·
        24 days ago

        Please examine where devops allowed non-system people to be the last word on altering systems. This is a risk that needs block-letter indemnification or correction.

        It’s not that devops made ya lazy. I’ve been doing devops since before they coined the term, and it’s a constant effort to remind people that it doesn’t magically make things safe, but keeping it safe is still the way.

        • Tablaste@linux.communityOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          23 days ago

          Ah not to discount devops, I mean that in a good way.

          Devops made me lazy in that for the past decade, I focus on just everything inside the code base.

          I literally push code into a magic black box that then triggers a rube goldberg of events. Servers get instanced. Configs just get magically set up. It’s beautiful. Just years of smart people who make it so easy that I never have to think about it.

          Since I can’t pay my devops team to come to my house, I get to figure it all out!