@@ -131,9 +131,7 @@ First, check if your agent is at home by typing
```
ssh-add -l # with `-l` as in "list"
```
This will list all identities currently represented by the agent. Think of "identity" as an SSH key that you want to add to the SSH authentication agent. In case, you see a message like this:
`Could not open a connection to your authentication agent.`
you need to activate the agent first:
This will list all identities currently represented by the agent. Think of "identity" as an SSH key that you want to add to the SSH authentication agent. If you see the message `Could not open a connection to your authentication agent`, you need to activate the agent first:
```
eval "$(ssh-agent -s)"
```
...
...
@@ -150,7 +148,7 @@ You can now use it within your session without having to re-enter the passphrase
#### 2.2.4 Additional SSH information
- For the Windows System: [Key-based authentication in OpenSSH for Windows](https://learn.microsoft.com/en-gb/windows-server/administration/openssh/openssh_keymanagement)
- 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 your `.ssh/authorized_keys` file in your home on Ramses. Any text editor will work for this.
- 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.
...
...
@@ -160,7 +158,7 @@ Ramses has currently two login servers available:
`ramses4.itcc.uni-koeln.de`
#### Login to `ramses1`
When logging in to **ramses1**, the public key you sent us is authenticated with your host's private key (1st factor, you will be asked for the SSH passphrase, unless you have ssh-agent configured as described above). If successful, a verification request is automatically pushed to the Duo-app on your device where you need to confirm the login (2nd factor).
When logging in to **ramses1**, the public key you sent us is authenticated with your host's private key (1st factor, you will be asked for the SSH passphrase, unless you have the SSH agent configured as described above). If successful, a verification request is automatically pushed to the Duo-app on your device where you need to confirm the login (2nd factor).
On your terminal you should see something like this:
