From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r107264: shr.el (shr-rescale-image): Allow viewing large images.
Date: Mon, 13 Feb 2012 21:01:32 +0100 [thread overview]
Message-ID: <874nuuwlib.fsf@gnus.org> (raw)
In-Reply-To: <jwvk43qzxom.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 13 Feb 2012 08:15:56 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> The whole purpose of max-image-size was to avoid crashes and
> denial-of-service, for example when viewing incorrectly-labeled images.
> So it's especially important for SHR which will display images
> downloaded from anywhere.
shr.el (if compiled with imagemagick support) will (by default) rescale
the images down. But to do that, it goes through the display engine,
anyway, so it's an issue anyway.
But what crashes and denials of service does `create-image' on a large
image result in?
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next prev parent reply other threads:[~2012-02-13 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1RwnLm-0007NV-Lm@vcs.savannah.gnu.org>
2012-02-13 13:15 ` [Emacs-diffs] /srv/bzr/emacs/trunk r107264: shr.el (shr-rescale-image): Allow viewing large images Stefan Monnier
2012-02-13 19:57 ` Andy Moreton
2012-02-13 20:03 ` Lars Ingebrigtsen
2012-02-13 20:01 ` Lars Ingebrigtsen [this message]
2012-02-13 20:29 ` [Emacs-diffs] " Paul Eggert
2012-02-13 20:33 ` Lars Ingebrigtsen
2012-02-13 20:41 ` Ted Zlatanov
2012-02-15 6:26 ` Chong Yidong
2012-02-15 13:40 ` Ted Zlatanov
2012-02-14 8:20 ` Paul Eggert
2012-02-14 14:49 ` Lars Ingebrigtsen
2012-02-14 15:56 ` Paul Eggert
2012-02-14 18:26 ` Lars Ingebrigtsen
2012-02-15 6:42 ` Chong Yidong
2012-02-15 6:27 ` Chong Yidong
2012-02-14 17:43 ` Stefan Monnier
2012-02-13 21:24 ` Stefan Monnier
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=874nuuwlib.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=yamaoka@jpl.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.