From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: Re: New FAQ entry about permissions since Cygwin 1.7.34
Date: Tue, 20 Oct 2015 22:48:00 -0000 [thread overview]
Message-ID: <5626C4CC.3000603@cornell.edu> (raw)
In-Reply-To: <20151020192559.GC17374@calimero.vinschen.de>
[-- 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
next prev parent reply other threads:[~2015-10-20 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 20:41 Ken Brown
2015-10-20 19:26 ` Corinna Vinschen
2015-10-20 22:48 ` Ken Brown [this message]
2015-10-21 8:24 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5626C4CC.3000603@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).