BreadCrumbs: Public Key Authentication

Public Key Authentication

From Luke Jackson

(Difference between revisions)
Jump to: navigation, search

Ljackson (Talk | contribs)

Next diff →

Revision as of 13:25, 8 October 2006

OpenSSH is a FREE version of the SSH connectivity tools that technical users of the Internet rely on. For more information on OpenSSH check out their website OpenSSH

Contents

[edit]

Introduction

Users of telnet, rlogin, and ftp may not realize that their password is transmitted across the Internet unencrypted, but it is. OpenSSH encrypts all traffic (including passwords) to effectively eliminate eavesdropping, connection hijacking, and other attacks. Additionally, OpenSSH provides secure tunneling capabilities and several authentication methods, and supports all SSH protocol versions.

Another great feature about OpenSSH is the Public Key Authentication mechanism. With this feature enabled you are able to securely authenticate with servers with out typing in a password.

[edit]

Requirements

  • Linux/Unix OS
  • openssh
  • openssh-server
  • openssh-clients

This tutorial will assume that you already have the above installed and operating correctly.

[edit]

Generate Key Pair (Linux)

First I will walk you through creating a key pair on a Linux/Unix OS.

Connect to the server of which you would like to enable Public Key Authentication on. Insure you are in the home directory of the account you use to logon to the server. To confirm this your prompt should look something like this [root@server.ext ~]#.

Locate the command ssh-keygen: 

Usage: ssh-keygen [options]
Options:
  -b bits     Number of bits in the key to create.
  -c          Change comment in private and public key files.
  -e          Convert OpenSSH to IETF SECSH key file.
  -f filename Filename of the key file.
  -g          Use generic DNS resource record format.
  -i          Convert IETF SECSH to OpenSSH key file.
  -l          Show fingerprint of key file.
  -p          Change passphrase of private key file.
  -q          Quiet.
  -y          Read private key file and print public key.
  -t type     Specify type of key to create.
  -B          Show bubblebabble digest of key file.
  -C comment  Provide new comment.
  -N phrase   Provide new passphrase.
  -P phrase   Provide old passphrase.
  -r hostname Print DNS resource record.
  -G file     Generate candidates for DH-GEX moduli
  -T file     Screen candidates for DH-GEX moduli

In this tutorial I will use a key type of RSA you are welcome to explore the different types but for my needs RSA is more than capable.

Create your key pair by executing the following command: 

ssh-keygen -f <filename> -t rsa

You will be prompted to enter a passphrase THIS IS IMPORTANT!!! If you forget your passphrase the keypair is lost forever please choose a passphrase you will not forget! 

[root@server.ext ~]# ssh-keygen -f filename -t rsa
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase): ***********
Enter same passphrase again: ***********
Your identification has been saved in filename.
Your public key has been saved in filename.pub.
The key fingerprint is:
**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:** root@server.ext

Now that you have successfully created your key pair we can configure the server.

[edit]

Generate Key Pair (Windows)

It is also possible to do this on a Windows compatible OS using Putty.

[edit]

Configure SSHD

Open the file /etc/ssh/sshd_config and browse to the section displayed below: 

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys

Ensure that the last 3 parameters are set like above and then save your changes.

[edit]

Configure User

Return back to your home directory and check to see if you have a file named authorized_keys in sub-directory called .ssh.

If you don't no problem just create them like so: 

mkdir .ssh
cd .ssh
touch authorized_keys

Now we will add our public key to the authorized_keys file. This may seem easy but it is the most common place for error. If you miss copy one character it will not authenticate you.

To prevent any errros cat the contents of your public key (filename.pub) to the authorized_keys file. 

cat ../filename.pub > authorized_keys

Should you be in a situation where you have to copy and paste the key from one server to another insure that the key file looks identical to the original. This will save you many hours of troubleshooting as there is no log entry telling you the public key was copied incorrectly.

Retrieved from "http://wiki.ljackson.us/Public_Key_Authentication"
Personal tools