assistant: Ensure that .ssh/config and .ssh/authorized_keys are not group or world writable when writing to those files, as that can make ssh refuse to use them, if it allows another user to write to them.

1 files changed, 9 insertions, 0 deletions

diff --git a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn b/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn
index 47c44bea3..9b2e89ca2 100644
--- a/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn
+++ b/doc/bugs/file_permissions_on___126____47__.ssh__47__config___40__windows__41__.mdwn
@@ -9,3 +9,12 @@ Windows 7, git-annex version 5.20131230-g192d991
 
 ### Please provide any additional information below.
 I have no daemon.log, and the console log isn't particularly detailed today; it had just created an ssh key and shown it's fingerprint.
+
+> Ok, I guess this is ssh refusing to use a file that has a group
+> write bit set (when the owner is not the only member of its group),
+> or perhaps that has the world write bit set.
+>
+> I have made the assistant unset those modes when creating and modifying
+> ssh config files. Hopefully that is enough for Windows too.. I can't
+> really test it there, but am calling this provisionally [[done]].
+> --[[Joey]]