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.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 days ago

    Lol you can actually demo a github compromise in real time to an audience.

    Make a repo with an API key, publish it, and literally just watch as it takes only a few minutes before a script logs in.

      • raspberriesareyummy@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        14 days ago

        –verbose please?

        edit: never mind, found it. So there’s dumbasses storing sensitive data (keys!) inside their git folder and unable to configure .gitignore…

          • lunachocken@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            8 days ago

            I always start with .gitignore and adding the .env then making it.

            Anywho, there’s git filter-repo which is quite nice and retconned some of my repos for some minor things out of existence :P