Rails%203%20In%20Action

Creating a user for the app
At this stage, you’ll be prompted for a password, which is the complex one you set up
a little earlier. Enter it here and the file will be copied over to the server.
Add this key to the ~/.ssh/authorized_keys file on the server by using this:
cat ~/.ssh/[your_name]_key.pub >> ~/.ssh/authorized_keys
This command will append the key to ~/.ssh/authorized_keys if that file already exists,
or create the file and then fill it with the content if it doesn’t. Either way, you’re going
to have a ~/.ssh/authorized_keys file, which means that you’ll be able to SSH to this
server without using your complex password. If you disconnect from the server and
then reconnect, you shouldn’t be prompted for your password. This means that the
authentication is working.
Finally, change the permissions on this ~/.ssh/authorized_keys file so that only the
user it belongs to can read it:
chmod 600 ~/.ssh/authorized_keys
With that set, change into the application’s user account by running sudo su
ticketeeapp.com and run the same steps, beginning with mkdir ~/.ssh and ending
with disconnecting and reconnecting without password prompt. Remember to
change user in the scp command to be the ticketeeapp.com user this time around.
If both of these accounts are working without password authentication, then you
may as well turn it off!
14.3.2 Disabling password authentication
You’ve just implemented key-based authentication on your system for both the
accounts you have, thus removing the need for any kind of password authentication.
To secure your server against possible password attacks, it’s a good idea to turn off
password authentication altogether.
To do this, open /etc/ssh/sshd_config using sudo nano /etc/ssh/sshd_config 18
and add PasswordAuthentication no where it would otherwise say #Password-
Authentication yes (the # symbol indicates a commented line, just like Ruby). You
can find this line by pressing Ctrl+W, typing in PasswordAuth, and pressing Enter.
This configures your SSH server to not accept password authentication.
Towards the top of this file there’s a line that says PermitRootLogin yes. Change
this line to read PermitRootLogin no instead, so that it blocks all SSH connections for
the root user, increasing the security further.
NOTE There is also /etc/ssh/ssh_config, which is a little confusing... two
files with nearly identical names. The file you just edited is the file for the
SSH server (or daemon, hence the d at the end), while the ssh_config file is
for the SSH client. Make sure you’re editing the right one.
Last, quit nano by pressing Ctrl+X and then Y to confirm that you do want to quit and
save. Next, you need to restart the SSH daemon by using this command:
18 nano is the basic editor that comes with Ubuntu.
393