From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yuri D'Elia Newsgroups: gmane.emacs.devel Subject: Re: Allowing symlinked dir-locals files? Date: Mon, 16 Aug 2021 20:25:23 +0200 Message-ID: <877dgl6ycs.fsf@wavexx.thregr.org> References: <8735r91d73.fsf@wavexx.thregr.org> <83o89x6yyn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36086"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:IF0sW4GFe5pc/YoWevB6Y/4LRYc= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 16 20:26:52 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mFhJz-0009Fy-Cx for ged-emacs-devel@m.gmane-mx.org; Mon, 16 Aug 2021 20:26:51 +0200 Original-Received: from localhost ([::1]:55336 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mFhJy-00086X-7o for ged-emacs-devel@m.gmane-mx.org; Mon, 16 Aug 2021 14:26:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36690) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mFhIk-0006ZB-T4 for emacs-devel@gnu.org; Mon, 16 Aug 2021 14:25:34 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:43364) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mFhIg-000333-LP for emacs-devel@gnu.org; Mon, 16 Aug 2021 14:25:32 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mFhIe-0007Wu-Bs for emacs-devel@gnu.org; Mon, 16 Aug 2021 20:25:28 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:272457 Archived-At: On Mon, Aug 16 2021, Eli Zaretskii wrote: >> However I suspect that the rationale was to be proper as well as "safe", >> as this could be used to make emacs read/interpret another file if the >> symlink is under the control of a VCS or via a shared-filesystem. > > Yes. It could also be a symlink injected by malevolent hackers. Can we please benevolent hackers with a list or trusted directories? ;) I don't recall where I saw this approach used before (maybe there's already a variable for trusted paths), but I wouldn't mind explicitly marking certain trees where symlinks are explicitly allowed.