git-setup.md

@@ -15,12 +15,14 @@ Each former CVS module on the second level of the hierarchy is now 'project' in
 
 
 # 3 Authentication And Cloning Projects
-Each project page displays a clone URL under the project name. Two methods are supported: SSH and HTTPS, which have different clone URLs. The HTTPS method only uses your username and password. The SSH method is more convenient but requires some up-front setup: you need to generate an SSH key pair, and paste the public key into your profile page at: https://webis16.medien.uni-weimar.de/gitlab/profile/keys. If you don't have an SSH-key pair, you can generate one by running
+Each project page displays a clone URL under the project name. Two methods are supported: SSH and HTTPS, which have different clone URLs. The HTTPS method only uses your username and password. The SSH method is more convenient, but requires some up-front setup. You need to generate an SSH key pair, and make the public key known to GitLab. If you don't have an SSH-key pair, you can generate one by running
 
 ```
 ssh-keygen -t rsa -b 4096
 ```
 
+and following the instructions. Although not required, it is recommended to set a password for encrypting your private key.
+
 Once your SSH key has been generated, copy the contents of `~/.ssh/id_rsa.pub` (or whatever file you chose to store your public key in) into the *Key* field at https://webis16.medien.uni-weimar.de/gitlab/profile/keys and click *Add Key*. This will add the public key to your GitLab account, so you can use you the corresponding private key to pull from and push to GitLab via SSH. Make sure to keep the private key part in `~/.ssh/id_rsa` secret at all times! If your private key gets compromised, delete the public key from GItLab and create a new key pair to prevent others from gaining unauthorized access to our Git repositories.
 
 If you are using the `webis` command (see next section), then `webis git init` will automatically create an SSH key pair for you if you don't have one.