We recommend you to download "**A Windows installer for everything except PuTTYtel**" with **Pageant** (SSH authentication agent) and **PuTTYgen** (PuTTY key generator) which is available [here][a].
!!! note
After installation, you can proceed directly to private keys authentication using ["Putty"][1].
"Change Password for Existing Private Key" is optional.
"Generate a New Public/Private key pair" is intended for users without Public/Private key in the initial email containing login credentials.
...
...
@@ -101,10 +99,14 @@ You can generate an additional public/private key pair and insert public key int

* Now you can insert an additional public key into the authorized_keys file for authentication with your own private key.
You must log in using the SSH key received after registration. Then proceed to [How to add your own key][2].
## Managing Your SSH Key
To manage your SSH key for authentication to clusters, see the [SSH Key Management][3] section.
When you first create an account with IT4Innovations, you receive an SSH key with your credentials. However, you can manage your own SSH key for authentication to clusters.
## Managing Your Own Key
1. Generate your SSH key (see the [OpenSSH Keys (UNIX)][1] or [PuTTY (Windows)][2] section).
1. Go to [https://extranet.it4i.cz/ssp/index.php?action=changesshkey][a]
1. Enter your username, password and public SSH key.
First, generate a new keypair of your public and private key:
```console
local $ssh-keygen -C'username@organization.example.com'-f additional_key
```
!!! note
Enter a **strong****passphrase** for securing your private key.
You can insert an additional public key into the authorized_keys file for authentication with your own private key. Additional records in the authorized_keys file must be delimited by a new line. Users are not advised to remove the default public key from the authorized_keys file.
Example:
```console
$cat additional_key.pub >> ~/.ssh/authorized_keys
```
In this example, we add an additional public key stored in the additional_key.pub file into the authorized_keys file. Next time we log in, we will be able to use the private addtional_key key to log in.
## Managing Your SSH Key
## How to Remove Your Own Key
To manage your SSH key for authentication to clusters, see the [SSH Key Management][1] section.
Removing your key from authorized_keys can be done simply by deleting the corresponding public key which can be identified by a comment at the end of line (e.g. _username@organization.example.com_).