From e93954138f44023f4d1d75c3e572295d8230acad Mon Sep 17 00:00:00 2001 From: Warren Young Date: Wed, 25 Feb 2015 17:41:23 +0000 Subject: [PATCH] Applied the "chgrp `id -g`" improvements suggested by Corinna for the FAQ item about SSH keys not working in 1.7.34+. --- winsup/doc/ChangeLog | 6 ++++++ winsup/doc/faq-using.xml | 15 +++++++++++++++ 2 files changed, 21 insertions(+) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 2e8e001b1..9ce8bb65b 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,9 @@ +2015-02-25 Warren Young + + * faq-using.xml (faq.using.ssh-pubkey-stops-working): More + improvements to the chgrp None hack to account for domains + and non-English versions of Windows. + 2015-02-25 Corinna Vinschen * ntsec.xml (ntsec-mapping): Match the description of the default diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index 9351bc850..372888f4c 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1141,10 +1141,25 @@ such a file reflects the change to both user and group. In effect, mode 0600 becomes mode 0660. Because we are saying we want these files to be readable only by our user, the fix for this is easy: + + $ chgrp `id -g` ~/.ssh/* + + +That resets the group on these files to your default group +which should be something like Users, +depending on your local configuration. If that doesn't work, you can +try something like this instead: + $ chgrp None ~/.ssh/* +That group always exists, but its name is different on +non-English versions of Windows. You might also want to use a +domain group instead of a local group if your site uses Windows +domains. For example, you might want to use the Domain +Users group instead. + For more information on setfacl, see