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
[–] 13 points 2 years ago (1 child)

There's no real advantage to disable the root user, and I really don't recommend it. You can disable SSH root login, and as long as you ensure root has a secure password that's different than your own account your system is just as safe with the added advantage of having the root account incase something happens.

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

    That wouldn't be defense in depth. You want to limit anything that's not necessary as it can become a source of attack. There is no reason root should be enabled.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 7 points 2 years ago

    I don't understand. You will still need to do administrative tasks once in a while so it isn't really unnecessary, and if root can't be logged in, that will mean you will have to use sudo instead, which could be an attack vector just as su.

  • source
  • parent
  • [–] 4 points 2 years ago

    Why do like, houses have doors man. You gotta eliminate all points of egress for security, maaaan. /s

    There's no particular reason to disable root, and with a hardened system, it's not even a problem you need to worry about...

  • source
  • parent