Simplify the SSH protocol introduction and link to a DO tutorial

Signed-off-by: Rémy Coutable <remy@rymai.me>
This commit is contained in:
Rémy Coutable 2017-01-31 11:28:56 +01:00
parent c9203e25d2
commit 7d0cdf6267
No known key found for this signature in database
GPG key ID: 46DF07E5CD9E96AB

View file

@ -4,10 +4,12 @@ Git is a distributed version control system, which means you can work locally
but you can also share or "push" your changes to other servers. but you can also share or "push" your changes to other servers.
Before you can push your changes to a GitLab server Before you can push your changes to a GitLab server
you need a secure communication channel for sharing information. you need a secure communication channel for sharing information.
GitLab uses Public-key or asymmetric cryptography
which encrypts a communication channel by locking it with your "private key" The SSH protocol provides this security and allows you to authenticate to the
and allows trusted parties to unlock it with your "public key". GitLab remote server without supplying your username or password each time.
If someone does not have your public key they cannot access the unencrypted message.
For a more detailed explanation of how the SSH protocol works, we advise you to
read [this nice tutorial by DigitalOcean](https://www.digitalocean.com/community/tutorials/understanding-the-ssh-encryption-and-connection-process).
## Locating an existing SSH key pair ## Locating an existing SSH key pair