• People can use weak passwords which are easy to hack
• A remote machine may have a key logger on it
• Someone may be performing a man-in-the-middle type attack

Hence if you wish to access a shell account or scp files remotely you should consider using either public/private keys setup or to setup One Time Keys.

Setting Up One Time Keys

Log in to the box (AS SECURELY AS POSSIBLE)

Logging in securely is important as you’ll be asked for a pass phrase. If this is compromised you’re in trouble.

Enable OTP

Run:

 opiepasswd -c

This will enable one time keys, asking you for the pass phrase as a seed for the cipher.

Once run one time keys are enabled.

The output of the command (something like):

 ID closebs OTP key is 499 wc8001
 THY HOOK TRY FREY DED DEDE

tells you a lot.

• The 499 is the number of the current One Time Password.
• The wc80001 is a key to go with your pass phrase if you want to generate the 499 login password.
• The THY HOOK… is the password for key 499

Finding out the next N passwords

To discover the next N One Time Passwords for printing use:

 opiekey -n NUM SEQ KEY

where:

• NUM is the amount of passwords to generate
• SEQ is the sequence number of the password to start with
• KEY is the key given for the cipher

Ie:

 opiekey -n 10 499 wc80001

This will display 10 keys, starting with key 499 and using the key wc80001. This can be useful as you can then print out the keys, and put them in your wallet/purse. WHAT I hear you say?

The reality is most passwords are broken by remote hackers. Whilst printing a list of one time passwords may seem insecure, the likely hood of someone going through your purse/wallet to find the printed out keys is very low. If you are concerned about it, simple put a simple transposition in each key that only you will know about.

Disabling OTP access

Help my keys have been compromised!

Get someone to run:

 opiepasswd -d

in your account.

Changing your OTP Pass Phrase

Simply run:

 opiepasswd

This will ask you for the next OTP in order to allow you to change your key (incase your remote) Once changed all your all your existing keys will now become invalid.

Using One Time Passwords

Any time you try to ssh to the WCL, you will be presented with:

 otp-md5 497 psfasdf ext
 Password:

This indicates you are required to provide password 497. The seed is given so you can generate the required password using it and your pass phrase if required.

Depending on the server setup, you can also enter your regular password at this point.

There is no way of telling if the server will accept your regular password or not unless you know it’s configuration.

Your Away, don’t have any passwords or pub/private keys but have access to a secure machine

As long as you can guarentee the machine you are on is secure, then chances are you can generate yourself the next password in the sequence in order to be able to access the remote box.

On the box your on run:

   opiekey  SEQUENCENUM SEED

You can get SEQUENCENUM & SEED just by sshing to the box and not logging in. You’ll need your pass phrase though.

SSH provides an encrypted tunnel for use with interactive and non interactive terminal sessions. It provides authentication via a number of methods including password, public/private key pairs and challenge keys.

SSH also provides authentication forwarding between machines. This feature allows a user to be able to log on to a machine without the need of typing a password. This is an extreemly strong feature as it means you can provide access to an account or even to execute a command without the need to provide someone with a password.

In order to setup public/private key authentication forwarding both the client and the server must have knowledge of the relevant keys. You must also consider the version of SSH software that the server/client is running as different versions use different files. Generating SSH Keys

The first step is to generate an SSH private/public key pair. For this I assume you are using some version of OpenSSH. There is currently three types of ssh key pairs that can be generated. They are rsa1, rsa and dsa. Of these dsa is the most secure and is the one used by ssh2. To generate the key perform the following:

  ssh-keygen -t rsa1
  ssh-keygen -t rsa
  ssh-keygen -t dsa

The public/private keys will be installed in the following places

Automated Authentication

With the keys generated it is now possible to setup automatic key authentication. This means when you log in to a machine you don’t need to enter your password. The authentication happens by the server encrypting some data with your public key then challenging the client to decript it. For this to happen, the client must have the private key matching the public key.

The procedure to set this up varies up which server you attempting to access. The procedure is basically as follows:

  scp [publickey] user@host:~
  ssh user@host
  cat [publickey] >> [filename]

The above is the basic procedure. However the publickey and filename vary depending on the server/client you are using. A valid example for OpenSSH using dsa keys is:

  scp ~/.ssh/id_dsa.pub user@host:~
  ssh user@host
  cat id_dsa.pub >> ~/.ssh/authorized_keys2

The table below shows which file to copy where:

Note 1: In order to generate an SECSH compliant key the following OpenSSH Command can be used:

  ssh-keygen -e -f [KEY].pub > [KEY]_SECSH.pub