unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: David Engster <deng@randomsample.de>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 33587@debbugs.gnu.org
Subject: bug#33587: [PROPOSED] Default to disabling ImageMagick
Date: Tue, 04 Dec 2018 12:00:48 -0500	[thread overview]
Message-ID: <ds36rdjkfz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87tvjtkzgg.fsf@randomsample> (David Engster's message of "Tue, 04 Dec 2018 17:51:11 +0100")

David Engster wrote:

> Question is: will disabling Imagemagick by default also have an impact
> on how Emacs is shipped in distributions?

I don't know. It depends whether they go with the default configure
options or not.

> I don't think so, at least as long as they don't drop Imagemagick
> completely.

Note that Red Hat Enterprise Linux 8 _will_ drop ImageMagick completely
(though it will probably be available from an add-on repository),
presumably because they don't feel able to keep up with the security
issues. That's what prompted me to first raise this in

http://lists.gnu.org/r/emacs-devel/2018-12/msg00036.html

> If for instance Debian has to take care of Imagemagick security issues
> anyway, why shouldn't Emacs link to it?

(For reference:
https://security-tracker.debian.org/tracker/source-package/imagemagick )

Because one can never guarantee all security issues are fixed, and if a
project has a history of having a lot of them, it may be considered
likely to be insecure. Also there are the various Emacs crash reports
due to ImageMagick.





  reply	other threads:[~2018-12-04 17:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 18:09 bug#33587: [PROPOSED] Default to disabling ImageMagick Paul Eggert
2018-12-02 18:15 ` Eli Zaretskii
2018-12-02 19:13 ` Andreas Schwab
2018-12-02 23:51   ` Paul Eggert
2018-12-03 21:09     ` Alan Third
2018-12-03 19:08 ` Glenn Morris
2018-12-03 19:35   ` Paul Eggert
2018-12-03 19:40     ` Glenn Morris
2018-12-04 16:51   ` David Engster
2018-12-04 17:00     ` Glenn Morris [this message]
2018-12-04 17:38       ` David Engster
2018-12-04 18:16       ` Glenn Morris
2018-12-10 17:49 ` Paul Eggert
     [not found] <8336qb3upt.fsf@gnu.org>
     [not found] ` <20190102211241.GA53734@breton.holly.idiocy.org>
     [not found]   ` <837efk335e.fsf@gnu.org>
     [not found]     ` <20190104190914.GA61852@breton.holly.idiocy.org>
     [not found]       ` <8336q82myq.fsf@gnu.org>
     [not found]         ` <20190104224558.GA63257@breton.holly.idiocy.org>
     [not found]           ` <20190110194250.GA22478@breton.holly.idiocy.org>
     [not found]             ` <cda98d78-268c-2464-36d3-cc03a4db97ef@cs.ucla.edu>
2019-05-14  6:15               ` 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=ds36rdjkfz.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=33587@debbugs.gnu.org \
    --cc=deng@randomsample.de \
    --cc=eggert@cs.ucla.edu \
    /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).