From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 739593d 3/5: Make gnus-copy-file act like copy-file etc.
Date: Thu, 14 Sep 2017 21:38:07 +0300 [thread overview]
Message-ID: <83o9qdm8hc.fsf@gnu.org> (raw)
In-Reply-To: <4ee490a4-c3ce-c9b7-7ef8-8e0248881de9@cs.ucla.edu> (message from Paul Eggert on Thu, 14 Sep 2017 10:59:44 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 14 Sep 2017 10:59:44 -0700
>
> Although perhaps someone can come up with a better idea, "Just do interactive
> renames the way we were doing it" is not better, as it would leave interactive
> users vulnerable to the attack. Although users may like to think that they are
> "unpredictable" and are thus relatively invulnerable to the attack, they're not
> really that unpredictable.
Maybe you should again describe the attack scenario. Last time you
did, it was pretty clear to me that no bot or person can reasonably
know in advance what file or directory the user will copy/rename.
next prev parent reply other threads:[~2017-09-14 18:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o9qdm8hc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.