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

@@ -1,3 +1,9 @@
+2015-02-25  Warren Young  <warren@etr-usa.com>
+
+	* 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  <corinna@vinschen.de>
 
 	* ntsec.xml (ntsec-mapping): Match the description of the default

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:</para>
 
+<screen>
+  $ chgrp `id -g` ~/.ssh/*
+</screen>
+
+<para>That resets the group on these files to your default group
+which should be something like <computeroutput>Users</computeroutput>,
+depending on your local configuration. If that doesn't work, you can
+try something like this instead:</para>
+
 <screen>
   $ chgrp None ~/.ssh/*
 </screen>
 
+<para>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 <computeroutput>Domain
+Users</computeroutput> group instead.</para>
+
 <para>For more information on <command>setfacl</command>, see
 <ulink url="https://cygwin.com/cygwin-ug-net/using-utils.html#setfacl"/></para>
 </answer></qandaentry>