public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [TESTERS needed] New POSIX permission handling
Date: Sat, 11 Apr 2015 09:35:00 -0000	[thread overview]
Message-ID: <20150411093456.GA19111@calimero.vinschen.de> (raw)
In-Reply-To: <F9F79D9B-8AA5-4911-96D7-22FA4795CEA0@etr-usa.com>

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

On Apr 10 15:13, Warren Young wrote:
> On Apr 10, 2015, at 4:07 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> > 
> >  This should help in Cygwin<->Windows interoperability.
> 
> That’s pretty vague.
> 
> Would you care to list some specific expected improvements from this
> change?  Are there known problem scenarios in the current world which
> we can test both ways, which should behave differently under the new
> DLL?
> 
> For instance, does it fix the well-known problem with chmod 600
> ~/.ssh/* resulting in mode 660 until you kick the ACLs around a bit?

Yes.  This has been discussed and I was originally opposing this change,
but not very loudly.  Other than that, please read the archives. You'll
find the threads discussing this in the last two months.


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

  reply	other threads:[~2015-04-11  9:35 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 10:07 Corinna Vinschen
2015-04-10 21:13 ` Warren Young
2015-04-11  9:35   ` Corinna Vinschen [this message]
2015-04-11  0:00 ` Steven Penny
2015-04-11  9:40   ` Corinna Vinschen
2015-04-11 10:07     ` Corinna Vinschen
2015-04-11 16:26       ` Ernie Rael
2015-04-12  8:22         ` Corinna Vinschen
2015-04-11 10:23     ` Corinna Vinschen
2015-04-11 10:47     ` Steven Penny
2015-04-11 14:30       ` Corinna Vinschen
2015-04-11 16:05       ` Andrey Repin
2015-04-12 17:37         ` Adam Dinwoodie
2015-05-16  2:39   ` Steven Penny
2015-05-17  7:44     ` Duncan Roe
2015-05-19  7:52     ` Jiří Engelthaler
2015-04-11  8:47 ` Achim Gratz
2015-04-11  9:02   ` David Macek
2015-04-11  9:08     ` Achim Gratz
2015-04-11  9:51       ` David Macek
2015-04-11 11:51         ` Achim Gratz
2015-04-11 10:00     ` Corinna Vinschen
2015-04-11 12:36       ` David Macek
2015-04-11 14:31         ` Corinna Vinschen
2015-04-11  9:44   ` Corinna Vinschen
2015-04-11 11:11     ` Bryan Berns
2015-04-11 14:32       ` Corinna Vinschen
2015-04-11 16:05   ` Andrey Repin
2015-04-11 17:11 ` donmez
2015-04-12  8:35   ` Corinna Vinschen
2015-04-12 13:21     ` İsmail Dönmez
2015-04-12 14:25       ` Corinna Vinschen
2015-04-15 15:42         ` Corinna Vinschen
2015-04-16 10:20           ` Ismail Donmez
2015-04-16 11:03             ` Corinna Vinschen
2015-04-16 16:09               ` Ismail Donmez
2015-04-16 16:24                 ` Corinna Vinschen
2015-04-16 16:48                   ` Ismail Donmez
2015-04-17  7:30                     ` Corinna Vinschen
2015-04-17 10:06                       ` Corinna Vinschen
2015-04-17 15:17                         ` Ismail Donmez
2015-04-17 16:22                           ` 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=20150411093456.GA19111@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@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).