Skip to main content
Information Security

Return to Answer

replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

mriconmricon brought up two excellent points for not using root login in a multi-user system. I just want to add a counter-point for using root login. If I need to rsync config files to the server, I can do it in one step using root login instead of uploading to the home directory of a user, then do su or sudo to rsync again into the /etc folder. Of course, I am the only administrator on the server and auditing is not an issue here.

There is no hard and fast rule for not permitting root login. It is part of a defense in depth measure. For that purpose, you can implement IP filtering or port knocking on your firewall. These, together with a strong password or key authentication should put you in good stead.

mricon brought up two excellent points for not using root login in a multi-user system. I just want to add a counter-point for using root login. If I need to rsync config files to the server, I can do it in one step using root login instead of uploading to the home directory of a user, then do su or sudo to rsync again into the /etc folder. Of course, I am the only administrator on the server and auditing is not an issue here.

There is no hard and fast rule for not permitting root login. It is part of a defense in depth measure. For that purpose, you can implement IP filtering or port knocking on your firewall. These, together with a strong password or key authentication should put you in good stead.

mricon brought up two excellent points for not using root login in a multi-user system. I just want to add a counter-point for using root login. If I need to rsync config files to the server, I can do it in one step using root login instead of uploading to the home directory of a user, then do su or sudo to rsync again into the /etc folder. Of course, I am the only administrator on the server and auditing is not an issue here.

There is no hard and fast rule for not permitting root login. It is part of a defense in depth measure. For that purpose, you can implement IP filtering or port knocking on your firewall. These, together with a strong password or key authentication should put you in good stead.

Source Link
Question Overflow
Question Overflow
  • 5.3k
  • 6
  • 29
  • 49

mricon brought up two excellent points for not using root login in a multi-user system. I just want to add a counter-point for using root login. If I need to rsync config files to the server, I can do it in one step using root login instead of uploading to the home directory of a user, then do su or sudo to rsync again into the /etc folder. Of course, I am the only administrator on the server and auditing is not an issue here.

There is no hard and fast rule for not permitting root login. It is part of a defense in depth measure. For that purpose, you can implement IP filtering or port knocking on your firewall. These, together with a strong password or key authentication should put you in good stead.