From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: larsi@gnus.org, yamaoka@jpl.org, emacs-devel@gnu.org
Subject: Re: master 739593d 3/5: Make gnus-copy-file act like copy-file etc.
Date: Thu, 14 Sep 2017 05:35:04 +0300 [thread overview]
Message-ID: <83d16unh2f.fsf@gnu.org> (raw)
In-Reply-To: <ad829af5-65a1-9538-42bc-e34b900ebafc@cs.ucla.edu> (message from Paul Eggert on Wed, 13 Sep 2017 13:07:47 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 13 Sep 2017 13:07:47 -0700
> Cc: emacs-devel@gnu.org
>
> On 09/13/2017 12:33 PM, Lars Ingebrigtsen wrote:
> > Breaking this ages-old (and convenient) behaviour doesn't seem like a
> > good idea to me either.
>
> It's an area where convenience and security collide. I'm open to
> suggestions to restoring convenience, but would rather not see security
> holes reintroduced.
I thought we agreed that the security issue is less of a concern in
interactive use of these functions, because interactive invocations
are less predictable, whereas the attack scenario in this case
requires that the attacker know in advance that Emacs will issue a
certain system call.
Based on that, I believe we agreed to leave the interactive behavior
alone, and only change the non-interactive one.
prev parent reply other threads:[~2017-09-14 2:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170911053128.28763.28434@vcs0.savannah.gnu.org>
[not found] ` <20170911053130.C5F002068F@vcs0.savannah.gnu.org>
2017-09-11 23:14 ` master 739593d 3/5: Make gnus-copy-file act like copy-file etc Katsumi Yamaoka
2017-09-12 2:12 ` Ken Brown
2017-09-12 2:33 ` Katsumi Yamaoka
2017-09-12 19:22 ` Paul Eggert
2017-09-14 4:17 ` Stefan Monnier
2017-09-14 16:54 ` Eli Zaretskii
2017-09-14 17:59 ` Paul Eggert
2017-09-14 18:38 ` Eli Zaretskii
2017-09-15 4:04 ` Paul Eggert
2017-09-15 9:16 ` Eli Zaretskii
2017-09-12 2:42 ` Eli Zaretskii
2017-09-13 19:33 ` Lars Ingebrigtsen
2017-09-13 20:07 ` Paul Eggert
2017-09-13 20:11 ` Lars Ingebrigtsen
2017-09-13 20:41 ` Paul Eggert
2017-09-13 21:10 ` Lars Ingebrigtsen
2017-09-13 23:32 ` Paul Eggert
2017-09-14 11:25 ` Lars Ingebrigtsen
2017-09-14 2:35 ` Eli Zaretskii [this message]
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=83d16unh2f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.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).