New FAQ entry about permissions since Cygwin 1.7.34

New FAQ entry about permissions since Cygwin 1.7.34

[Ken Brown]

There have been several recent threads on the cygwin list stemming from 
the permissions change in 1.7.34.  I've pointed people to the FAQ about 
ssh public key authentication, which is not the first place where 
someone with this problem is likely to look.  The following patch 
attempts to remedy this:

---
  winsup/doc/ChangeLog     |  4 ++++
  winsup/doc/faq-using.xml | 42 ++++++++++++++++++++++++++++++++++++++++++
  2 files changed, 46 insertions(+)

diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index 35935be..7e85a76 100644
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,3 +1,7 @@
+2015-10-06  Ken Brown  <kbrown@cornell.edu>
+
+       * faq-using.xml (faq.using.same-with-permissions): New entry.
+
  2015-09-07  Brian Inglis  <Brian.Inglis@SystematicSw.ab.ca>

         * faq-using.xml (faq.using.man): Replace makewhatis with mandb.
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index 7656880..0564504 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -1183,6 +1183,48 @@ Users</computeroutput> group instead.</para>

  </answer></qandaentry>

+<qandaentry id="faq.using.same-with-permissions">
+<question><para>Why do my files have extra permissions after updating 
to Cygwin 1.7.34?</para></question>
+<answer>
+
+<para>The problem is exactly the same as with the key files of SSH.  See
+<xref linkend="faq.using.ssh-pubkey-stops-working"/>.</para>
+
+<para>The solution is the same:</para>
+
+<screen>
+  $ ls -l *
+  -rw-rwxr--+ 1 user group 42 Nov 12  2010 file1
+  -rw-rwxr--+ 1 user group 42 Nov 12  2010 file2
+  $ setfacl -b *
+  $ ls -l *
+  -rw-r--r--  1 user group 42 Nov 12  2010 file1
+  -rw-r--r--  1 user group 42 Nov 12  2010 file2
+</screen>
+
+<para>You may find that newly-created files also have unexpected
+permissions:</para>
+
+<screen>
+  $ touch foo
+  $ ls -l foo
+  -rw-rwxr--+ 1 user group 42 Nov 12  2010 foo
+</screen>
+
+<para>This probably means that the directory in which you're creating
+the files has unwanted default ACL entries that are inherited by
+newly-created files and subdirectories.  The solution is again the
+same:</para>
+
+<screen>
+  $ setfacl -b .
+  $ touch bar
+  $ ls -l bar
+  -rw-r--r--  1 user group 42 Nov 12  2010 bar
+</screen>
+
+</answer></qandaentry>
+
  <qandaentry id="faq.using.tcl-tk">
  <question><para>Why do my Tk programs not work anymore?</para></question>
  <answer>
--
2.5.3

Ken

Re: New FAQ entry about permissions since Cygwin 1.7.34

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]

Hi Ken,

On Oct  6 16:41, Ken Brown wrote:
> There have been several recent threads on the cygwin list stemming from the
> permissions change in 1.7.34.  I've pointed people to the FAQ about ssh
> public key authentication, which is not the first place where someone with
> this problem is likely to look.  The following patch attempts to remedy
> this:

Unfortunately it doesn't apply cleanly.  There are weird differences in
whitespaces and a patch-breaking line wrap.  Can you check and resend,
please?


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: New FAQ entry about permissions since Cygwin 1.7.34

[Ken Brown]

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

On 10/20/2015 3:25 PM, Corinna Vinschen wrote:
> Hi Ken,
>
> On Oct  6 16:41, Ken Brown wrote:
>> There have been several recent threads on the cygwin list stemming from the
>> permissions change in 1.7.34.  I've pointed people to the FAQ about ssh
>> public key authentication, which is not the first place where someone with
>> this problem is likely to look.  The following patch attempts to remedy
>> this:
>
> Unfortunately it doesn't apply cleanly.  There are weird differences in
> whitespaces and a patch-breaking line wrap.  Can you check and resend,
> please?

Sorry, my mailer must have messed it up.  Here it is as an attachment.

Ken


[-- Attachment #2: 0001-winsup-doc-faq-using.xml-faq.using.same-with-permiss.patch --]
[-- Type: text/plain, Size: 2344 bytes --]

From d073a456341cb58d92ce75c2b5b46e1d2a54ec09 Mon Sep 17 00:00:00 2001
From: Ken Brown <kbrown@cornell.edu>
Date: Tue, 6 Oct 2015 16:31:05 -0400
Subject: [PATCH] * winsup/doc/faq-using.xml (faq.using.same-with-permissions):
 New entry.

---
 winsup/doc/ChangeLog     |  4 ++++
 winsup/doc/faq-using.xml | 42 ++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 46 insertions(+)

diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index 35935be..7e85a76 100644
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,3 +1,7 @@
+2015-10-06  Ken Brown  <kbrown@cornell.edu>
+
+	* faq-using.xml (faq.using.same-with-permissions): New entry.
+
 2015-09-07  Brian Inglis  <Brian.Inglis@SystematicSw.ab.ca>
 
 	* faq-using.xml (faq.using.man): Replace makewhatis with mandb.
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index 7656880..4cfc822 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -1183,6 +1183,48 @@ Users</computeroutput> group instead.</para>
 
 </answer></qandaentry>
 
+<qandaentry id="faq.using.same-with-permissions">
+<question><para>Why do my files have extra permissions after updating to Cygwin 1.7.34?</para></question>
+<answer>
+
+<para>The problem is exactly the same as with the key files of SSH.  See
+<xref linkend="faq.using.ssh-pubkey-stops-working"/>.</para>
+
+<para>The solution is the same:</para>
+
+<screen>
+  $ ls -l *
+  -rw-rwxr--+ 1 user group 42 Nov 12  2010 file1
+  -rw-rwxr--+ 1 user group 42 Nov 12  2010 file2
+  $ setfacl -b *
+  $ ls -l *
+  -rw-r--r--  1 user group 42 Nov 12  2010 file1
+  -rw-r--r--  1 user group 42 Nov 12  2010 file2
+</screen>
+
+<para>You may find that newly-created files also have unexpected
+permissions:</para>
+
+<screen>
+  $ touch foo
+  $ ls -l foo
+  -rw-rwxr--+ 1 user group 42 Nov 12  2010 foo
+</screen>
+
+<para>This probably means that the directory in which you're creating
+the files has unwanted default ACL entries that are inherited by
+newly-created files and subdirectories.  The solution is again the
+same:</para>
+
+<screen>
+  $ setfacl -b .
+  $ touch bar
+  $ ls -l bar
+  -rw-r--r--  1 user group 42 Nov 12  2010 bar
+</screen>
+
+</answer></qandaentry>
+
 <qandaentry id="faq.using.tcl-tk">
 <question><para>Why do my Tk programs not work anymore?</para></question>
 <answer>
-- 
2.5.3

Re: New FAQ entry about permissions since Cygwin 1.7.34

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]

On Oct 20 18:48, Ken Brown wrote:
> On 10/20/2015 3:25 PM, Corinna Vinschen wrote:
> >Hi Ken,
> >
> >On Oct  6 16:41, Ken Brown wrote:
> >>There have been several recent threads on the cygwin list stemming from the
> >>permissions change in 1.7.34.  I've pointed people to the FAQ about ssh
> >>public key authentication, which is not the first place where someone with
> >>this problem is likely to look.  The following patch attempts to remedy
> >>this:
> >
> >Unfortunately it doesn't apply cleanly.  There are weird differences in
> >whitespaces and a patch-breaking line wrap.  Can you check and resend,
> >please?
> 
> Sorry, my mailer must have messed it up.  Here it is as an attachment.

Thanks, applied.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]