KAUST Supercomputing Laboratory Newsletter 10th August

Maintenance Session Tuesday 20th September

The next scheduled maintenance on Shaheen will be Tuesday 20th September from 08:00 until 17:00. There will no access to the system during this period.

Two Factor Authentication

To enhance the security of the Shaheen service, we will be introducing two factor authentication to the login process after the maintenance session of 20th September. This will apply to all Shaheen users, without exception. The first factor will be the method that you are used to - either Active Directory password or SSH keys (we strongly recommend the use of encrypted SSH keys rather than password). The second factor will be a one-time password, i.e. a password that will only be valid for one login session. We will announce further details about the process soon.

RCAC Meeting

The project submission deadline for the next RCAC meeting is 31st August 2016. Please note that the RCAC meetings are held once per month. Projects received on or before this deadline will be included in the agenda for the next RCAC meeting, scheduled to be held in September 2016. The detailed procedure and the forms are available here:


Neser Last Day of Operation

Please note this system will be decommissioned on 30th November 2016.

After this date all data in /project and /home will be deleted. Please ensure that you have transferred any data you wish to retain.

Running Application Code on the login nodes

The login nodes (CDLs) are not designed or designated to run application code, they are meant to be used exclusively for file management, editing and compiling. Please do not run other code on the login nodes as this impacts performance and adversely affects other users. If code is found to be running on the CDLs, KSL staff may kill these programs without warning and continued abuse may lead to account suspension.

Tip of the Week: SSH public-private key authentication

SSH keys establish a unique communications path between a user's workstation and the server that s/he is logging into. The public-private key pair is generated on the user's workstation, and the private key exists only there. The public key should be copied to the $HOME/.ssh/authorized_keys file on the server(s) that you are logging into. This will allow password-less SSH authentication from client to server; however we strongly recommend that you protect your private key using a passphrase, which should be different from your Active Directory password. The private key must then be "unlocked" using the passphrase each time that you make a SSH connection. If you are logging in frequently, you may also wish to investigate the use of an ssh agent to avoid continually having to enter your passphrase.

Follow us on Twitter

Follow all the latest news on HPC within the Supercomputing Lab and at KAUST, on Twitter @KAUST_HPC.

Previous Announcements


Previous Tips