From: Eli Zaretskii <eliz@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] POSIX ACL support
Date: Wed, 21 Nov 2012 21:40:15 +0200 [thread overview]
Message-ID: <83d2z6vj6o.fsf@gnu.org> (raw)
In-Reply-To: <874nkidb8n.fsf@Rainer.invalid>
> From: Achim Gratz <Stromeko@nexgo.de>
> Date: Wed, 21 Nov 2012 20:09:12 +0100
>
> On windows at least it is possible to have all access rights, but
> specifically not to create or change ACL.
True. But I think this is unlikely to be a problem when _copying_ a
file, because the copy is created by you, so you get full access by
default, and that includes the "write DAC" (a.k.a. "change ACL")
privilege. However, it _can_ happen that after copying the ACL from
the original, you no longer can change the access rights, if that
privilege was denied in the original. Which is okay, I think.
next prev parent reply other threads:[~2012-11-21 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 22:27 [PATCH] POSIX ACL support Romain Francoise
2012-11-19 3:44 ` Eli Zaretskii
2012-11-19 21:41 ` Romain Francoise
2012-11-20 3:44 ` Eli Zaretskii
2012-11-19 17:11 ` Glenn Morris
2012-11-19 17:47 ` Eli Zaretskii
2012-11-19 18:11 ` Stefan Monnier
2012-11-19 21:33 ` Romain Francoise
2012-11-20 18:15 ` Stefan Monnier
2012-11-21 12:51 ` Romain Francoise
2012-11-21 14:25 ` Stefan Monnier
2012-11-21 15:36 ` Paul Eggert
2012-11-21 16:01 ` Romain Francoise
2012-11-21 18:17 ` Eli Zaretskii
2012-11-21 18:25 ` Paul Eggert
2012-11-21 19:09 ` Achim Gratz
2012-11-21 19:40 ` Eli Zaretskii [this message]
2012-11-21 19:52 ` Achim Gratz
2012-11-19 21:55 ` Paul Eggert
2012-11-20 18:16 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d2z6vj6o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).