From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin 1.7.35 reads file permissions differently, affects fetchmail
Date: Mon, 23 Mar 2015 09:14:00 -0000 [thread overview]
Message-ID: <20150323091056.GC3017@calimero.vinschen.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1503230918190.14799@vmdebian.local.koeppe-net.de>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
On Mar 23 09:57, Martin Koeppe wrote:
>
> Hi all,
>
> I just updated from cygwin 1.7.32 to 1.7.35,
> and now file permissions are calculated differently,
> which breaks fetchmail for me:
>
> Here are the Windows permissions:
> (no permissions for Domain Users / Domänen-Benutzer)
>
> $ cacls fetchmailrc.txt
> D:\fetchmail\fetchmailrc.txt NT-AUTORIT.T\SYSTEM:(ID)F
> NT-AUTORIT.T\LOKALER DIENST:(ID)C
> DOMAENE\LocalAdmin:(ID)F
> VORDEFINIERT\Administratoren:(ID)F
>
> cygwin-1.7.32 $ ls -l
> -rwx------+ 1 LocalService Domänen-Benutzer 1932 15. Aug 2014
> fetchmailrc.txt
>
> cygwin-1.7.35 $ ls -l
> -rwxrwx---+ 1 LocalService Domänen-Benutzer 1932 15. Aug 2014
> fetchmailrc.txt
>
>
> Now, there are group permissions set. For me it breaks fetchmail, because
> fetchmail only runs when the config file is owned by the user running
> fetchmail (LocalService in my case, a system user I never can login with)
> and with max 0700 permissions. While this check is ok/good for Unix, because
> you still can view/edit the file as user root, you now can't anymore as
> Administrator on Windows.
Huh? You can. Just open a Cygwin admin shell and take a look.
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 --]
next prev parent reply other threads:[~2015-03-23 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 9:11 Martin Koeppe
2015-03-23 9:14 ` Corinna Vinschen [this message]
2015-03-23 19:04 ` cygwin 1.7.35 reads file permissions differently, affects broken apps Linda Walsh
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=20150323091056.GC3017@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).