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.

you are viewing a single comment's thread
view the rest of the comments
[–] 48 points 2 years ago (1 child)

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.

  • source
  • hideshow 2 child comments
  • [–] 31 points 2 years ago (2 children)

    I search commits for "removed env file" to hopefully catch people who don't know how git works.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 15 points 2 years ago* (2 children)

    --verbose please?

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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 14 points 2 years ago (1 child)

    yeah, I just tried it there, people actually did it.

  • source
  • parent
  • hideshow 2 child comments