Note

On Ubuntu the package “krb5-user” is needed.

The system uses Kerberos for authentication. To access files you must have a valid ticket. You can see your current tickets with:

klist


This also shows when the ticket will expire. Currently it will expire after 10 hours.

Note

You do not loose your ticket when you log out.

### Renewing a Ticket¶

As a general rule, whenever you type your password, you will also renew your tickets. To explicit renew a ticket (while having one), simply use:

kinit


If you want to run stuff during the night, be aware that your ticket may expire. In that case you can use a cron job (or maybe just a script using “sleep”), to automatically run the “kinit” command while you are away.

### Obtaining a Ticket¶

If you just log in using your password, you will get a ticket. To obtain a ticket, whlie on the SDU network (e.g., on eduroam), also use “kinit”. For NAT accounts:

kinit user@NAT.C.SDU.DK


and for non-NAT accounts:

Todo

Basically the same, but with a different domain.

Note

The capitilisation of the part after “@” matters!

Note

Currently it is not possible to get a ticket outside the SDU network, and therefore not possible to do passwordless login without typing your password once at some point.

On the jump hosts and the computer lab machines, simply do ordinary SSH. From other machines, where you have a valid ticket, use the “-K” flag to forward your ticket. E.g.:

ssh -K jlandersen@logon.sdu.dk


Warning

it seems that this actually doesn’t work at the moment.

If you use SSH-aliases in “.ssh/config” you can add ticket forwarding as default:

Todo

write it once it works, it should basically be adding “GSSAPIDelegateCredentials yes

Once you have a ticket on the target machine, then you have access to the ordinary “.ssh/authorized_keys” file, public/private key authentication will then work. That is, from outisde the SDU network, you must type your password once, and subsequent logins can be passwordless (through public/private keys).

Warning

Logging in with public/private key authentication will not renew your ticket.

## Passwordless kinit¶

You can create a keytab file to locally store credentials for use with “kinit”. The file is completely location independent, but must be recreated when your Kerberos credentials change.

Warning

A keytab file should be regarded as a secret in the same way a private key should. That is, don’t give it away, and avoid transfering it out of a machine.

A keytab file is viewed and created using “ktutil”, and we here assume you are using the MIT Kerberos implementation (see also this). ktutil works by starting it and then typing commands inside it. For example:

addent -password -p user@NAT.C.SDU.DK -k 1 -e rc4-hmac
wkt mySecrets.keytab
quit


which adds an entry for “user@NAT.C.SDU.DK” and then writes the actual keytab file to “mySecrets.keytab”. The keytab file can now be used to get a ticket without typing your password:

kinit username@NAT.C.SDU.DK -k -t mySecrets.keytab


If you have a class 3 office machine on the SDU network, you can now put this command in a cron job to make sure you always have a ticket.

The following scripts are interdependent and meant to be in the same folder. Click here to get an archive with them.

• layout: not a stand-alone script, but contains the names of all terminal room machines (updated October 13 2016, by Marco).

• foreach: general script for executing commands for each machine. You probably want to use one of the other scripts.

• getCores: make a file with computer names and number of cores in the CPUs. The file is used by the ping script.

• ping: show a map of the terminal room with information about each machine.

• doForeach: execute the given command sequentially on all machines.

• doParallelForeach: execute the given command in parallel on all machines.