This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Potential Enhancement Of 'noacl'?
- From: Bryan Berns <bryan dot berns at gmail dot com>
- To: cygwin-developers at cygwin dot com
- Date: Fri, 17 Apr 2015 15:02:10 -0400
- Subject: Re: Potential Enhancement Of 'noacl'?
- Authentication-results: sourceware.org; auth=none
- References: <CADi7v6+DN=xZ0tMvoJBZ4wESM3PeAD0B+dre7xm91+sJ1HOV5w at mail dot gmail dot com> <20150417185606 dot GI3657 at calimero dot vinschen dot de>
On Fri, Apr 17, 2015 at 2:56 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Apr 17 14:11, Bryan Berns wrote:
>
>> Why would someone want to do this crazy thing? In short, I continue
>> to struggle with the current Cygwin permissions handling for certain
>> drives where programs do sanity checks on group readability (e.g.,
>> ssh).
>
> That puzzles me. OpenSSH is upstream Cygwin-aware, and the code skips
> permission checks on files if the underlying filesystem does not support
> permissions (e.g. noacl or FAT FS). What problem do you have in real
> life with noacl?
>
Hmm... good question. I honestly not sure I put it to a practical test
-- I just saw it was reporting group read via 'ls -l' and stopped
there. I'll give it a shot on Monday. You may have made my day.... I
really didn't *want* to do what I was proposing :P