From 7f417a263743ae912a4810546874d2647ab41ade Mon Sep 17 00:00:00 2001 From: weinzwang Date: Sun, 24 Jul 2016 15:47:26 +0000 Subject: Added a comment: Same problem with ssh.knownHost --- .../comment_3_e057fae70854f7323dafa0d79b327dec._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/Ssh.authorizedKey_does_not_work_on_brand_new_user/comment_3_e057fae70854f7323dafa0d79b327dec._comment (limited to 'doc') diff --git a/doc/forum/Ssh.authorizedKey_does_not_work_on_brand_new_user/comment_3_e057fae70854f7323dafa0d79b327dec._comment b/doc/forum/Ssh.authorizedKey_does_not_work_on_brand_new_user/comment_3_e057fae70854f7323dafa0d79b327dec._comment new file mode 100644 index 00000000..5da15f09 --- /dev/null +++ b/doc/forum/Ssh.authorizedKey_does_not_work_on_brand_new_user/comment_3_e057fae70854f7323dafa0d79b327dec._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="weinzwang" + subject="Same problem with ssh.knownHost" + date="2016-07-24T15:47:25Z" + content=""" +Making a host key known to a brand new user `requires` the +owner of a nonexistent file to be set, if I understand the +code correctly. Removing the \"requires\"-lines from the function +modKnownHost makes the problem go away, but that's probably not +the correct solution. +"""]] -- cgit v1.2.3