From cf247cf6cc8468c88e702223652bcca92cc90160 Mon Sep 17 00:00:00 2001 From: eeerky Date: Tue, 13 Jan 2015 15:24:25 +0000 Subject: [PATCH] Added a comment: shared keys? --- ...omment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/tips/Synology_NAS_and_git_annex/comment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment 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 new file mode 100644 index 0000000000..2c68f7e2eb --- /dev/null +++ b/doc/tips/Synology_NAS_and_git_annex/comment_4_d8e4b08ceedece8a45d4146ff5d3a995._comment @@ -0,0 +1,11 @@ +[[!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. +"""]]