all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: enriched.el code execution
Date: Thu, 7 Sep 2017 14:24:42 -0700	[thread overview]
Message-ID: <65178e03-1e83-2175-deb3-330723a8c21c@cs.ucla.edu> (raw)
In-Reply-To: <yzsh8we5izi.fsf@marauder.physik.uni-ulm.de>

Reiner Steib wrote:
> If I understand correctly, this issue is serious enough (CVSS is 8.8,
> Common Vulnerability Scoring System, v3.0) that we should prepare a
> security fix release (from Emacs 25.2) as soon as we have a fix for
> this bug (or we should disable this feature of enriched mode).

I favor this as well. Although I hate maintaining the old branch, this bug is 
quite serious.



      reply	other threads:[~2017-09-07 21:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83tw0h0yem.fsf@gnu.org>
     [not found] ` <handler.s.C.150463767313430.transcript@debbugs.gnu.org>
2017-09-06  6:40   ` release bugs [was Re: Processed: enriched.el code execution] Glenn Morris
2017-09-06  9:41     ` John Wiegley
2017-09-06 10:00       ` Sven Joachim
2017-09-06 10:13         ` John Wiegley
2017-09-07  4:03         ` Richard Stallman
2017-09-07 14:43           ` Eli Zaretskii
2017-09-06 16:12     ` Eli Zaretskii
2017-09-07  6:30       ` Paul Eggert
2017-09-07 13:11         ` John Wiegley
2017-09-07 15:03         ` Eli Zaretskii
2017-09-07 21:32           ` Paul Eggert
2017-09-08  6:55             ` Eli Zaretskii
2017-09-08  7:11               ` Paul Eggert
2017-09-08  8:20                 ` Fabrice Popineau
2017-09-08 21:42                   ` Óscar Fuentes
2017-09-09 17:12                   ` Richard Stallman
2017-09-09 18:27                     ` Fabrice Popineau
2017-09-07 20:47         ` enriched.el code execution Reiner Steib
2017-09-07 21:24           ` Paul Eggert [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=65178e03-1e83-2175-deb3-330723a8c21c@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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.