Secure Ubuntu server for non-root user using only SSH keys

August 3, 2013 26.8k views
lindahl22
By:
lindahl22
I would like to have a secure Ubuntu server. I believe the best way to accomplish this is to only use SSH keys and disable use of the root user account. Accomplishing this is not made easy. The tutorials either show you how to use SSH keys on root or how to use a second account with a password, not a combination of the two. I have tried to do both and failed. The following is what I have attempted to do to accomplish this task. Create Ubuntu droplet with SSH keys in DO panel. Login to root using SSH key and create secondary user. Paste the SSH key into the secondary users' ~/.ssh/authorized_keys file. Either disable root login or require SSH keys: PermitRootLogin No || without-password
Log In to Comment
14 Answers
rileycrane May 6, 2015

I realize this is a bit late, but I had the same problem and managed to solve it. Here are the set of commands that you need to run as root on a new digital ocean droplet (assuming you have already setup root to have ssh access). This will setup mynewuser with passwordless sudo rights and the ability to ssh into the machine without a password (using only your ssh-key)
adduser --system --group mynewuser
mkdir /home/mynewuser/.ssh
chmod 0700 /home/mynewuser/.ssh/
cp -Rfv /root/.ssh /home/mynewuser/
chown -Rfv mynewuser.mynewuser /home/mynewuser/.ssh
chown -R mynewuser:mynewuser /home/mynewuser/
gpasswd -a mynewuser sudo
echo "mynewuser ALL=(ALL) NOPASSWD: ALL" | (EDITOR="tee -a" visudo)
service ssh restart
usermod -s /bin/bash mynewuser

Now you should be able to ssh into your new droplet with
ssh mynewuser@your-new-digitalocean-droplet-ip-address

Reply
  • spython01 June 1, 2017

    Thank you for posting this. These instructions helped me out with a similar issue. May I ask what is the purpose of the following two lines?

    chown -Rfv mynewuser.mynewuser /home/mynewuser/.ssh
chown -R mynewuser:mynewuser /home/mynewuser/
    • lelanomusrex December 4, 2017

      You may have found this in your own research already, but my understanding is these two lines change the ownership of the directories /home/mynewuser/.ssh and /home/mynewuser so that they are owned by the USER mynewuser and the GROUP mynewuser which were created in the first line of these instructions

  • seanconnell20 May 10, 2019

    Thank you 😊

pablo August 3, 2013
Scroll down to the Disable Username/Password Logins section of this article: How to Create SSH Keys with PuTTY to Connect to a VPS.
How To Create SSH Keys With PuTTY to Connect to a VPS
by Pablo Carranza
This tutorial runs through creating SSH keys with PuTTY to connect to your virtual server.
Reply
lindahl22 August 3, 2013
So with PasswordAuthentication and UsePAM set to no, there would be no concerns with having no password for the root user or the secondary user?
Reply
kamaln7 MOD August 3, 2013
Correct. :]
Reply
lindahl22 August 3, 2013
I think I did something wrong. It seems like SSH keys are not working. Also, it appears that I can't login via the VNC console on DO because I setup the server with SSH keys, not a password. It also asked for my password for the secondary user, I didn't expect this. Is this only becuase it needed it to run sudo?

This is what I am getting on the secondary account:

new-host-2:~ mymac$ ssh -p PORT USERNAME@IPADDRESS
The authenticity of host '[IPADDRESS]:PORT ([IPADDRESS]:PORT)' can't be established.
RSA key fingerprint is FINGERPRINTKEY.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[IPADDRESS]:PORT' (RSA) to the list of known hosts.
Permission denied (publickey).
new-host-2:~ user$ sudo apt-get install fail2ban
Password:
sudo: apt-get: command not found


This is what I am getting when I try to login as root:
new-host-2:~ mymac$ ssh -p NUM root@IP
Permission denied (publickey).
Reply
kamaln7 MOD August 3, 2013
Did you add you ssh key to /home/user/.ssh/authorized_keys?
Reply
lindahl22 August 3, 2013
Nope. But the error even occurs when I try logging in as root.
Reply
lindahl22 August 3, 2013
So right now I can't access my droplet. The root user won't let me in (which did before), the second user doesn't have the authorized_keys set. I used the DO VNC console to login as my second user but I cannot login as root. Changing PermitRootLogin to yes didn't fix logging in as root (on desktop or VNC) as it gives me "Permission denied (publickey)." which was not an issue when I first logged in with my keys. It would be great to get a tutorial that actually explained these settings instead of just telling us what to type.
Reply
kamaln7 MOD August 3, 2013
Log in as root via the console (sshd's settings shouldn't affect the console), and revert sshd_config to allow password login so you can add your public ssh keys. If you do not know the root password, you can reset it by clicking the Reset Root Password button in the Access tab.
Reply
lindahl22 August 3, 2013
Okay. I can login as root now. It was because it wasn't an AllowedUser. My bad. I'll copy the key to my authorized_keys and I should be good. Hopefully.
Reply
lindahl22 August 3, 2013
Would this be the correct command to copy the key from root the secondaryuser (when logged in as root)? Or do I not need home?

root@droplet-01:~# cp i ~/.ssh/authorized_keys /home/secondaryuser/.ssh/authorized_keys
cp: target `/home/secondaryuser/.ssh/authorized_keys' is not a directory
Reply
kamaln7 MOD August 3, 2013
The easiest way would be running this command locally:

ssh-copy-id user@host
Reply
smurf September 6, 2014

I am having a similar problem. My key works when login in for root but not for non-root users.

Reply
  • shahbazkhan1003 May 14, 2017

    I have the same problem I can login using root but when I try to login with different users it just won't work.

    So I have a user called myuser and inside its home directory which /home/myuser.ssh I have kept the authorized keys.

    But I just won't work.

    Help :(

sigurdurbjarnason March 31, 2017

For anyone out there scratching their heads over this still.... I had this problem..

the only issue for me was that the authorized_keys had to be chmod to 644 in the users .ssh folder

hope it helps

Siggi

Reply
Have another answer? Share your knowledge.