From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: larsi@gnus.org, 19565@debbugs.gnu.org
Subject: bug#19565: Emacs vulnerable to endless-data attack (minor)
Date: Sun, 06 Oct 2019 20:32:28 +0300 [thread overview]
Message-ID: <83a7ad3hlf.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnhZzczftBeTPhDYt3Nctw7eonUyfHD1EsRYSjX2h2yXw@mail.gmail.com> (message from Stefan Kangas on Sun, 6 Oct 2019 05:13:27 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sun, 6 Oct 2019 05:13:27 +0200
> Cc: 19565@debbugs.gnu.org
>
> I think this affects more than just package.el. AFAICT, anywhere we
> use the url library, an endless data attack can get Emacs to fill up
> all available memory (wasting also bandwidth resources, of course).
At which point the system will kill the Emacs process. Why is that a
problem we need to work, given that we already have at least some
protection against stack overflows and running out of memory?
> For example, a new keyword argument :max-size, which would make it
> stop after having reached that many bytes.
The Gnu Coding Standards frown on having arbitrary limits in a
program. So this could only work if we had some reasonable way of
computing a limit that is not arbitrary.
next prev parent reply other threads:[~2019-10-06 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 11:12 bug#19565: Emacs vulnerable to endless-data attack (minor) Kelly Dean
2015-01-11 18:33 ` Richard Stallman
2015-01-11 21:18 ` Kelly Dean
2019-10-06 3:13 ` Stefan Kangas
2019-10-06 17:32 ` Eli Zaretskii [this message]
2019-10-07 1:51 ` Lars Ingebrigtsen
2019-10-07 12:50 ` Stefan Kangas
2019-10-07 16:13 ` Eli Zaretskii
2019-10-08 16:27 ` Lars Ingebrigtsen
2019-10-08 16:47 ` Eli Zaretskii
2019-10-08 16:50 ` Stefan Kangas
2019-10-08 17:22 ` Eli Zaretskii
2019-10-08 17:38 ` Stefan Kangas
2019-10-08 18:02 ` Eli Zaretskii
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=83a7ad3hlf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19565@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).