libs/newlib-cygwin
libs
/
newlib-cygwin
mirror of git://sourceware.org/git/newlib-cygwin.git
4
0
Fork 0
Code Issues Projects Releases Wiki Activity

Applied the "chgrp `id -g`" improvements suggested by Corinna for the FAQ 

item about SSH keys not working in 1.7.34+.
This commit is contained in:
Warren Young 2015-02-25 17:41:23 +00:00
parent cc70635c0d
commit e93954138f
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
winsup/doc/ChangeLog
View File

@ -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

15
winsup/doc/faq-using.xml
View File

@ -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>