From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: master fails to build on FreeBSD when ACL support is on Date: Mon, 22 Jan 2018 16:47:30 -0800 Organization: UCLA Computer Science Department Message-ID: <3b5337be-2050-7dce-17ad-4428bdbf4c00@cs.ucla.edu> References: <86o9lua0yx.fsf@phe.ftfl.ca> <834lnly8ht.fsf@gnu.org> <86vafy20sj.fsf@phe.ftfl.ca> <83o9lpuct5.fsf@gnu.org> <83lggtu1qn.fsf@gnu.org> <9dd64b10-78ce-c561-8c51-9e15b11e102c@cs.ucla.edu> <83bmhpt12i.fsf@gnu.org> <867escw93p.fsf@phe.ftfl.ca> <86vafwumqp.fsf@phe.ftfl.ca> <025ce2fd-a69a-12da-ce5b-c894d5636789@cs.ucla.edu> <83372zryx3.fsf@gnu.org> <4928e09c-e747-8754-973f-7b358ca3f5e7@cs.ucla.edu> <83inbtriv1.fsf@gnu.org> <83zi55zt7m.fsf@gnu.org> <83y3kpzlav.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1516668365 27624 195.159.176.226 (23 Jan 2018 00:46:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 23 Jan 2018 00:46:05 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 Cc: jrm@ftfl.ca, ashish@FreeBSD.org, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 23 01:46:00 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1edmie-0005z8-OH for ged-emacs-devel@m.gmane.org; Tue, 23 Jan 2018 01:45:44 +0100 Original-Received: from localhost ([::1]:50408 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edmkf-0003Up-3o for ged-emacs-devel@m.gmane.org; Mon, 22 Jan 2018 19:47:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57425) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1edmkT-0003UI-Mp for emacs-devel@gnu.org; Mon, 22 Jan 2018 19:47:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1edmkS-0007SD-Ts for emacs-devel@gnu.org; Mon, 22 Jan 2018 19:47:37 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:46720) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1edmkP-0007Pk-5D; Mon, 22 Jan 2018 19:47:33 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 251E61615AA; Mon, 22 Jan 2018 16:47:31 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id J6QQhJLj6Sfj; Mon, 22 Jan 2018 16:47:30 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 607C416161D; Mon, 22 Jan 2018 16:47:30 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KgB7qnnsU76E; Mon, 22 Jan 2018 16:47:30 -0800 (PST) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 427B71615AA; Mon, 22 Jan 2018 16:47:30 -0800 (PST) In-Reply-To: <83y3kpzlav.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:222159 Archived-At: On 01/22/2018 12:32 PM, Eli Zaretskii wrote: >> One way to move forward would be to change copy-file to have a three-way >> result, as set-file-acl does. That is, it could return t if successful, >> nil if mildly unsuccessful, and signal an error if severely >> unsuccessful. > The distinction between return values is not relevant to interactive > invocation. Sure, but this topic came up for a noninteractive invocation: the place where rename-file calls copy-file. If rename-file had a way of telling copy-file "Hey! use your best effort to copy permissions but don't signal an error if you can't", then rename-file could suppress the signal for failure to copy ACLs without suppressing the signal for other failures. (This may not be a good idea, though; please see below.) > ACLs are not universally supported, and giving up on copying them doesn't > mean the file is not protected. I'm afraid that it does mean that, at least for GNU/Linux ACLs, as they can prevent you from accessing a file that you could otherwise access. In other words, if you copy a file but not its ACLs, a user may be able to access the copy even though they cannot access the original. This is an argument against silently continuing when ACLs cannot be copied.