From: Eric Blake <ebb9@byu.net>
To: cygwin@cygwin.com
Subject: Re: [BUG 1.7] Read-only files are not.
Date: Thu, 01 Jan 2009 00:07:00 -0000 [thread overview]
Message-ID: <loom.20090101T000200-655@post.gmane.org> (raw)
In-Reply-To: <495C00DF.5020208@acm.org>
David Rothenberger <daveroth <at> acm.org> writes:
>
> It seems that read-only files in Cygwin 1.7 are not truly
> read-only. The sequence of steps below shows that "chmod 444 file1"
> does not make the file read-only in Cygwin 1.7, while it does in
> Cygwin 1.5. It may have something to do with the Read Only DOS
> attribute. This is set by Cygwin 1.5 but not by Cygwin 1.7. If I
> manually set it for Cygwin 1.7, the file does become read-only.
Are you perchance running as an Administrator, and therefore you have backup
privileges? If so, then you have root-like power, and cygwin exposes that by
opening files with intent to backup even when the ACLs would otherwise make the
file unreadable. Therefore, even though none of S_IRUSR, S_IRGRP, S_IROTH are
set in the posixy st_mode bits, access(file, R_OK) returns 0 and open() is able
to exploit your root-like powers to read that file.
I thought Corinna mentioned this in the release notes.
>
> (This issue was brought to my attention by a failing subversion test
> after building for 1.7.)
The findutils testsuite also had to make accomodations to skip certain tests
when run with root-like privileges.
--
Eric Blake
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2009-01-01 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 23:32 David Rothenberger
2008-12-31 23:59 ` Christopher Faylor
2009-01-01 1:17 ` David Rothenberger
2009-01-01 0:07 ` Eric Blake [this message]
2009-01-01 0:57 ` David Rothenberger
2009-01-01 3:39 ` Christopher Faylor
2009-01-07 14:31 ` 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=loom.20090101T000200-655@post.gmane.org \
--to=ebb9@byu.net \
--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).