β² 858 βΌ I didn't know you were supposed to disable root user... (linux.community) submitted 2 years ago by Tablaste@linux.community to c/linuxmemes@lemmy.world 170 comments fedilink hide all child comments 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.
[β] satans_methpipe@lemmy.world 17 points 2 years ago* (2 children) On a new linux install or image I will always: Make new users(s) Setup new user to sudo Change ssh port Change new user to authenticate ssh via key+password Disable root ssh login permalink fedilink source hideshow 4 child comments replies: [β] njordomir@lemmy.world 10 points 2 years ago That's more or less the advice I've gotten as well. I've also read good things about fail2ban which tries to ban sources of repeated authentication failures to prevent brute force password attempts. I've used it, but the only person who has managed to get banned is myself! I did get back in after the delay, but I'm happy to know it works. permalink fedilink source parent [β] stebator@lemmy.world 7 points 2 years ago Setup new user to sudo I hope it is not a passwordless sudo, it is basically the same as root. permalink fedilink source parent
[β] njordomir@lemmy.world 10 points 2 years ago That's more or less the advice I've gotten as well. I've also read good things about fail2ban which tries to ban sources of repeated authentication failures to prevent brute force password attempts. I've used it, but the only person who has managed to get banned is myself! I did get back in after the delay, but I'm happy to know it works. permalink fedilink source parent
[β] stebator@lemmy.world 7 points 2 years ago Setup new user to sudo I hope it is not a passwordless sudo, it is basically the same as root. permalink fedilink source parent