Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
778d2045
Commit
778d2045
authored
Sep 04, 2018
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update doc/ssh/README.md
parent
de45ba49
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
9 deletions
+11
-9
doc/ssh/README.md
doc/ssh/README.md
+11
-9
No files found.
doc/ssh/README.md
View file @
778d2045
...
@@ -151,15 +151,6 @@ Host gitlab.company.com
...
@@ -151,15 +151,6 @@ Host gitlab.company.com
RSAAuthentication yes
RSAAuthentication yes
IdentityFile ~/.ssh/config/private-key-filename
IdentityFile ~/.ssh/config/private-key-filename
```
```
If you want to use different keys depending on the repository you are working
on, you can issue the following command while inside your repository:
```
git config core.sshCommand "ssh -o IdentitiesOnly=yes -i ~/.ssh/private-key-filename-for-this-repository -F /dev/null"
```
Please note that such a configuration will not use the SSH Agent and requires
at least Git 2.10.
Due to the wide variety of SSH clients and their very large number of
Due to the wide variety of SSH clients and their very large number of
configuration options, further explanation of these topics is beyond the scope
configuration options, further explanation of these topics is beyond the scope
...
@@ -169,6 +160,17 @@ Public SSH keys need to be unique, as they will bind to your account.
...
@@ -169,6 +160,17 @@ Public SSH keys need to be unique, as they will bind to your account.
Your SSH key is the only identifier you'll have when pushing code via SSH.
Your SSH key is the only identifier you'll have when pushing code via SSH.
That's why it needs to uniquely map to a single user.
That's why it needs to uniquely map to a single user.
## Per-repository SSH keys
If you want to use different keys depending on the repository you are working
on, you can issue the following command while inside your repository:
```
sh
git config core.sshCommand
"ssh -o IdentitiesOnly=yes -i ~/.ssh/private-key-filename-for-this-repository -F /dev/null"
```
This will not use the SSH Agent and requires at least Git 2.10.
## Deploy keys
## Deploy keys
### Per-repository deploy keys
### Per-repository deploy keys
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment