nadnerB's CloudatCost Project Journal
- 
 So, today I'd like to set up SSH but I'll check on the fail2ban that I did yesterday. 
 Ā
 Logged in as my non-root user account
 fail2ban-client status sshd... looks like it requires use of sudo to check
 Apparently my non-root account requires listing in a 'sudoers file'... righto.
 Ā
 One goes the lab coat as I step into the research mode...
- 
 I think I'll do this by group permissions instead of individual permissions. 
 New group createdgroupadd <group name>
 User addedusermod <user> -G <groupname>
 Check members of the groupgrep ^<group name> /etc/group- success  
 
- success 
- 
 Righto, so it looks like the Sudoers file, that I need to edit, is read only. 
 However, I have found what looks like a good set of instructions here: https://www.digitalocean.com/community/tutorials/how-to-edit-the-sudoers-file-on-ubuntu-and-centos
 EDIT: This initial setup guide has a slightly different (I think) way of doing it (step 4) https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-12-04
- 
 Hmmm, perhaps editing the Sudoers file is not a good idea... 
 Should I edit the file and add my username or just usesu?
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.
- 
 @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.I log in as root directly to all my servers. 
- 
 @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.You don't edit the file You'd gpasswd -a nadnerb wheelwhere nadnerb is the username you wish to give sudo privileges too.
- 
 @thanksajdotcom said: @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.I log in as root directly to all my servers. I personally would disable root access over SSH after the initial setup. 
- 
 @thanksajdotcom said: @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.I log in as root directly to all my servers. Thanks for your input but I won't be doing this  
- 
 @thecreativeone91 said: @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.You don't edit the file You'd gpasswd -a nadnerb wheelwhere nadnerb is the username you wish to give sudo privileges too.Fantastic! Thanks!  
- 
 @thecreativeone91 said: @thanksajdotcom said: @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.I log in as root directly to all my servers. I personally would disable root access over SSH after the initial setup. On the secret To-Do list 
- 
 @nadnerB said: @thecreativeone91 said: @nadnerB said: Hmmm, perhaps this is not a good idea... 
 Comments @JaredBusch, @thecreativeone91, @scottalanmiller or @thanksajdotcom ?
 EDIT: I'll hold off on deploying this for now.You don't edit the file You'd gpasswd -a nadnerb wheelwhere nadnerb is the username you wish to give sudo privileges too.Fantastic! Thanks!  No Problem. It's just a group you add it to, as the group has sudo premissions (sudoers file) . 
- 
 
- 
 @nadnerB said: Righto, so it looks like the Sudoers file, that I need to edit, is read only. Just means you have to tell the editor that you "mean it" when you save. In vi that means :w! instead of :w 
- 
 Righto, I've blocked root access via SSH and renamed the server to something more useful (for ron... later on) 
- 
 Hmmm, attempting to install htop is proving to be more difficult than yum -y install htop.
 I can't seem to connect to any of the mirrors.
 *http://mirror.netflash.net/centos/7.0.1406/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not *resolve host: mirror.netflash.net; Unknown error"
 Trying other mirror.
- 
 Often that means that DNS isn't set up. Can you lookup addresses in general? 
- 
 You might need to set dns in resolv.conf 
- 
 If the DNS issue doesn't resolve it you may have to refresh your YUM cache. I think a yum -clean all or yum -clean headers will do that. 
- 
 Excellent suggestions!  I'll check that out when I get home I'll check that out when I get home 
- 
 Found the location of resolv.conf and how to edit here: http://ask.xmodulo.com/configure-static-dns-centos-fedora.html 
 htop now installed. I quite like it 


