summaryrefslogtreecommitdiff
path: root/doc/ssh
diff options
context:
space:
mode:
authorRémy Coutable <remy@rymai.me>2017-01-31 11:28:56 +0100
committerRémy Coutable <remy@rymai.me>2017-01-31 11:28:56 +0100
commit7d0cdf62673303e9164c2a98ca9387d8f26c2233 (patch)
tree0d28ead767727c50f383fdab7ed80869d08e09f0 /doc/ssh
parentc9203e25d214487b2b7ccc0e85af32e418a84bcb (diff)
downloadgitlab-ce-7d0cdf62673303e9164c2a98ca9387d8f26c2233.tar.gz
Simplify the SSH protocol introduction and link to a DO tutorialsimplify-ssh-doc
Signed-off-by: Rémy Coutable <remy@rymai.me>
Diffstat (limited to 'doc/ssh')
-rw-r--r--doc/ssh/README.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/ssh/README.md b/doc/ssh/README.md
index 9803937fcf9..9e391d647a8 100644
--- a/doc/ssh/README.md
+++ b/doc/ssh/README.md
@@ -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.
Before you can push your changes to a GitLab server
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"
-and allows trusted parties to unlock it with your "public key".
-If someone does not have your public key they cannot access the unencrypted message.
+
+The SSH protocol provides this security and allows you to authenticate to the
+GitLab remote server without supplying your username or password each time.
+
+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