diff options
| author |  eeerky <eeerky@web> | 2015-01-13 19:26:51 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-01-13 19:26:51 +0000 |
| commit | 86d8a795507f913e11e79e71cef2f0f1f41556a4 (patch) | |
| tree | 9e648157d439bdfffe47c7fe3418fe1d98177618 /doc | |
| parent | 188e9865054a8478851969c10c1a0841d6f2d95d (diff) | |
removed
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tips/Synology_NAS_and_git_annex/comment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/doc/tips/Synology_NAS_and_git_annex/comment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment b/doc/tips/Synology_NAS_and_git_annex/comment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment deleted file mode 100644 index 2c68f7e2e..000000000 --- a/doc/tips/Synology_NAS_and_git_annex/comment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="eeerky" - subject="shared keys?" - date="2015-01-13T15:24:25Z" - content=""" -I'm not sure if I'm misreading this walkthrough, but does prefixing your key in authorize_keys file mean that the specific key pair can only be used in conjunction with git annex? - -In other words, if I wish to have one key pair between my laptop and server, could I use that one key pair for both git-annex and simple shell access? - -What I'm seeing now is that the path to my **git-annex-shell** script is correct, but my server goes into high cpu and doesn't let me login when I try sshing into it. -"""]] |