From: Eli Zaretskii <eliz@gnu.org>
To: charles@aurox.ch, larsi@gnus.org
Cc: eggert@cs.ucla.edu, 28350-done@debbugs.gnu.org
Subject: bug#28350: enriched.el code execution
Date: Sat, 16 Sep 2017 12:48:58 +0300 [thread overview]
Message-ID: <83a81vkm7p.fsf@gnu.org> (raw)
In-Reply-To: <83y3plqck1.fsf@gnu.org> (message from Eli Zaretskii on Mon, 11 Sep 2017 22:07:26 +0300)
> Date: Mon, 11 Sep 2017 22:07:26 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: larsi@gnus.org, eggert@cs.ucla.edu, 28350@debbugs.gnu.org
>
> > Date: Mon, 11 Sep 2017 20:44:19 +0200
> > From: charles@aurox.ch (Charles A. Roelli)
> > CC: eggert@cs.ucla.edu, larsi@gnus.org, 28350@debbugs.gnu.org
> >
> > > Here's the idea: we introduce a new form of a display property:
> > >
> > > ('disable-eval SPEC)
> > >
> > > where SPEC is anything supported in a display property.
> >
> > Thanks for suggesting this; it's much cleaner than sanitizing the
> > display specification from Lisp. Looks good to me.
>
> Thanks, I will wait for a few days before pushing.
Done.
Lars, I re-enabled support for enriched text in Gnus, as the
vulnerability is now removed. Feel free to disable it again, if you
don't want Gnus users to be able to display enriched text, ever.
I'm marking the bug done.
next prev parent reply other threads:[~2017-09-16 9:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 19:24 bug#28350: enriched.el code execution Charles A. Roelli
2017-09-06 19:25 ` Charles A. Roelli
2017-09-07 2:34 ` Eli Zaretskii
2017-09-09 12:23 ` Charles A. Roelli
2017-09-09 13:45 ` Eli Zaretskii
2017-09-09 15:57 ` Charles A. Roelli
2017-09-09 16:55 ` Eli Zaretskii
2017-09-09 20:37 ` Charles A. Roelli
2017-09-10 17:01 ` Eli Zaretskii
2017-09-11 16:32 ` Glenn Morris
2017-09-11 17:01 ` Eli Zaretskii
2017-09-09 22:43 ` Paul Eggert
2017-09-10 18:54 ` Charles A. Roelli
2017-09-10 21:46 ` Paul Eggert
2017-09-11 2:39 ` Eli Zaretskii
2017-09-11 14:22 ` Eli Zaretskii
2017-09-11 15:18 ` Eli Zaretskii
2017-09-11 18:44 ` Charles A. Roelli
2017-09-11 19:07 ` Eli Zaretskii
2017-09-16 9:48 ` Eli Zaretskii [this message]
2017-09-11 15:33 ` Glenn Morris
2017-09-11 16:38 ` Paul Eggert
2017-09-11 21:16 ` Glenn Morris
2017-09-12 19:59 ` Paul Eggert
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=83a81vkm7p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28350-done@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.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).