From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: romain@orebokech.com, emacs-devel@gnu.org
Subject: Re: [PATCH] POSIX ACL support
Date: Wed, 21 Nov 2012 10:25:21 -0800 [thread overview]
Message-ID: <50AD1C91.5030708@cs.ucla.edu> (raw)
In-Reply-To: <83k3tevn0l.fsf@gnu.org>
On 11/21/12 10:17, Eli Zaretskii wrote:
> Can a user on a Posix
> host always copy the ACLs, no matter what access right these ACLs
> specify?
I don't know of any exception, no, though I don't pretend to be
an expert on Posix ACLS.
> And in addition, this could be inconvenient or even dangerous: you
> could set access rights on a file you created that give you no access
> at all, not even read access.
This couldn't happen for files that you're copying, since if you can't
read them you can't copy them anyway. But anyway, it's OK to create
files that you can't read -- Emacs already can do that, I expect.
Romain's point about special file handlers is a good one. If we
want this to work with Tramp we have to have a way in C or in Lisp
to represent all the file metadata, so that we can copy it. Doing
this correctly would solve not only this problem, but some other bugs
in this area (e.g., group or group permission is wrong, time stamps
are truncated).
next prev parent reply other threads:[~2012-11-21 18:25 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 [this message]
2012-11-21 19:09 ` Achim Gratz
2012-11-21 19:40 ` Eli Zaretskii
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=50AD1C91.5030708@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.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.
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).