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

Glenn Morris writes:
> 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

RHEL can do this because they're supporting way less packages than other
distributions. As you know, enterprise customers have other priorities
than home desktop users. Debian cannot remove Imagemagick because many
other packages depend on it, at least currently.

>> 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.

I understand the reasoning. To me, image scaling is essential for what
I'm doing with Emacs, so I'm willing to take that risk. But that's just
one data point.

Don't get me wrong: I don't object to disable it by default. Let's see
what happens. Maybe distributions will then disable it as well, but they
have their own ways to see how changes like these affect users (by
having an 'unstable' tree or whatever).

-David





  reply	other threads:[~2018-12-04 17:38 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
2018-12-04 17:38       ` David Engster [this message]
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=87pnuhkx8s.fsf@randomsample \
    --to=david@engster.org \
    --cc=33587@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=rgm@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 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).