| Table of Contents |
|---|
...
SSH key configuration allows users to enter and traverse the BRB infrastructure without entering passwords at each step. The following will create an SSH keypair and authorize its use.
Local Workstation to SCU Cluster
From your local Mac or Linux workstation, enter the following within the infrastructure.terminal
| Code Block |
|---|
ssh-keygen |
Accept default options at each prompt and an SSH private and public key will be created in your ~/.ssh/ directory. Enter the following commands to authorize its use within the cluster.
| Code Block |
|---|
cd[local@my_workstation ~]$ cat ~/.ssh/ cat id_rsa.pub >> ~/.ssh/authorized_keys |
| Note |
|---|
While your public key in id_rsa.pub can be shared freely, your private key in id_rsa must be kept secret. If another person gains access to this file, they will be able to impersonate you thereby accessing all of your files. Do not ever copy or move your private key from your ~/.ssh folder or set permissions so that other users can access this file. Permissions on this file should always be "chmod 600," set my ssh-keygen, which means only accessible by the owner. Do not change permissions on the private key. |
...
Keys Within SCU Infrastructure
Repeat above steps on one of the SCU login nodes
| Code Block |
|---|
[cwid@scu-login02 ~]$ ssh-keygen |
Accept default options at each prompt and an SSH private and public key will be created in your ~/.ssh/ directory. Enter the following commands to authorize its use within the cluster.
| Code Block |
|---|
[cwid@scu-login02 ~]$ cat id_rsa.pub >> authorized_keys |
...
Access Cluster Nodes
Cluster nodes are managed through Slurm. Accessing and running jobs on login nodes or by ssh’ing directly to a node is Strictly forbidden.
In-depth SCU documentation on Slurm can be found here: Using Slurm .
...