From LWP-Wiki
Jump to: navigation, search


There are two requirements for remote access via ssh.

  1. the public part of your ssh key is stored in ~/.ssh/authorized_keys
  2. the file /etc/security/access.conf contains a line for your username
    + : p123456 : ALL

Howto add yourself to /etc/security/access.conf

If the command id tells you that you are a member of the localadmin group then you can edit the file with your favorite text editor. Otherwise you need to contact us at

How to get and manage your ssh keys

You can generate an ssh key pair with the command:

$ ssh-keygen

See the manual for more options. Make sure to passphrase protect your private key. The command will tell you where it created the keys. Now copy the public part of the key into your ~/.ssh/authorized_keys file. Assuming you choose to use the ssh-keygen -t dsa command and used the defaults do:

$ cat ~/.ssh/ >> ~/.ssh/authorized_keys
$ chmod 600 ~/.ssh/authorized_keys

Now all that is left to do is to use a thumbdrive or encrypted email or some other method to get the private key (~/.ssh/id_dsa) into your other computer. If the other computer uses Linux or OSX then store the file in ~/.ssh/ and it will be picked up automatically when you use the ssh command to connect. If you use Windows and PUTTY command for ssh you can import the key through the PUTTYGen key manager. Note you can also generate the key pair on your other computer and import the public part of the key into your LWP. It is then safe to use unencrypted e-mail.


  • I still get asked for a password?
    Yes this happens after a reboot of your LWP and you have not logged in at least once. It can also happen if you have not used your computer for a week. Just try again and you will see that this time it will let you in using your ssh key only.
  • So how does this work?
    When you login you get a Kerberos ticket which gives you access to a number of services (like reading your home directory) without prompting you for a password every time. The Kerberos ticket is valid for one day initially, but will be extended automatically for up to one week. It will also reinitialize when you type your password (eg. to unlock your screen). If you reboot your computer or purposefully destroy your Kerberos ticket, you do not have access to your home directory anymore and so the ssh command cannot find your public key in the authorized_keys file. It will ask for a password, but unfortunately it will not try to look again for the public key. So access will be denied. However if you try again (anytime in the next week) things will work.
  • Can I get access from anywhere?
    Yes, but you yourself can restrict access further by changing the value ALL in /etc/security/access.conf eg. to the ip-address of your home computer.