From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: plaice.adam+lists@gmail.com, emacs-devel@gnu.org
Subject: Re: bug#37656: 27.0.50; Arbitrary code execution with special `mode:'
Date: Wed, 16 Oct 2019 10:59:36 +0300 [thread overview]
Message-ID: <837e55f7dj.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=U1zfUsD4jTPj44mNvQX-h2gVrvXCkvjM5V7brhS71_Q@mail.gmail.com> (message from Stefan Kangas on Wed, 16 Oct 2019 00:55:08 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 16 Oct 2019 00:55:08 +0200
> Cc: 37656@debbugs.gnu.org, Emacs developers <emacs-devel@gnu.org>
>
> Here is a more complete patch. Does it look like the right fix?
As explained on the bug list (and let's please continue discussing
this there), I don't think this is the right solution.
Thanks.
next prev parent reply other threads:[~2019-10-16 7:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 21:05 bug#37656: 27.0.50; Arbitrary code execution with special `mode:' adam plaice
2019-10-15 22:23 ` Clément Pit-Claudel
2019-10-15 22:27 ` Stefan Kangas
2019-10-15 22:55 ` Stefan Kangas
2019-10-15 23:17 ` Stefan Kangas
2019-10-15 23:17 ` Stefan Kangas
2019-10-16 7:58 ` Eli Zaretskii
2019-10-16 11:51 ` Adam Plaice
2019-10-16 17:09 ` Eli Zaretskii
2019-10-16 19:09 ` Phil Sainty
2019-10-16 19:34 ` Eli Zaretskii
2019-10-16 21:02 ` Adam Plaice
2019-10-16 0:35 ` Adam Plaice
2019-10-16 7:57 ` Eli Zaretskii
2019-10-16 0:55 ` Phil Sainty
2019-10-16 0:55 ` Phil Sainty
2019-10-16 7:59 ` Eli Zaretskii [this message]
2019-10-15 22:27 ` Stefan Kangas
2019-10-16 6:43 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 8:48 bug#37656: 27.0.50; Opening file with specially crafted local variables can cause arbitrary code execution Inbox x adam plaice
2019-10-15 21:05 ` bug#37656: 27.0.50; Arbitrary code execution with special `mode:' adam plaice
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=837e55f7dj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=plaice.adam+lists@gmail.com \
--cc=stefan@marxist.se \
/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.