@@ -150,7 +150,7 @@ You can now use it within your session without having to re-enter the passphrase
- For CHEOPS users: If you already have access to Ramses but you are using the CHEOPS key, we advise you to create your own SSH key on your local machine/laptop and then add the public key to the `~/.ssh/authorized_keys` file in your home on Ramses. Any text editor will work for this.
- How to avoid creating multiple key pairs for multiple remote machines: [SSH Agent Forwarding](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding). This feature allows an SSH Key to be taken along into another SSH session. Essentially, it lets you authenticate to other servers through an initial SSH connection.
- How to avoid creating multiple key pairs for multiple remote machines: [SSH Agent Forwarding](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding). This feature allows an SSH key to be taken along into another SSH session. Essentially, it lets you authenticate to other servers through an initial SSH connection.
### 2.3 Login nodes
Ramses has currently two login servers available:
...
...
@@ -175,7 +175,7 @@ rpabel2@ramses1:~>
Even though the message `"Autopushing..."` appears twice, only one push is executed and only one verification is needed.
#### Login to `ramses4`
On **ramses4**, you can choose different Cisco Duo authenticators, if you have configured any:
On **ramses4**, you can select different Cisco Duo authenticators, if you have configured any:
```
rpabel2@soliton:~> ssh ramses4
Duo two-factor login for rpabel2
...
...
@@ -194,8 +194,10 @@ In this example, if you choose '1', an authentication request is pushed to your
**IMPORTANT NOTE**: Be careful with scripted logins: Any login attempt with your SSH key that triggers Duo Autopush is counted by Duo. If you don't respond in your Duo-app, your account will be blocked after 10 attempts. Only an admin can then unlock it (see [FAQ section](../FAQ#access_ramses)).
#### Facilitating your login
To facilitate login, we suggest to set an alias upon initialization of your shell (`~/.bashrc`, `~/.zshrc` or similar):
To facilitate login, we suggest to set an alias in your shell's startup configuration file (`~/.bashrc`, `~/.zshrc`, or similar):
Make adjustments according to your preferences. In case you just happened to wish for enabling shorter attention spans during your ramses sessions: The default of `ServerAliveInterval` (in seconds) may cause automatic logouts after a relatively short idle time. Overriding this behaviour, as done above, can also be done globally on your host through (sudo) editing the file `/etc/ssh/ssh_config`. Then, it would simply be a line entry like `ServerAliveInterval 1000`.
