From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 9196@debbugs.gnu.org
Subject: bug#9196: integer and memory overflow issues (e.g., cut-and-paste crashes Emacs)
Date: Sat, 30 Jul 2011 07:52:48 +0200 [thread overview]
Message-ID: <4E339C30.9090708@swipnet.se> (raw)
In-Reply-To: <4E332009.3090909@cs.ucla.edu>
Paul Eggert skrev 2011-07-29 23:03:
> Also, it's not really true that I won't be the one that has to take
> the time. I have been taking the time to maintain and improve these
> checks for months now. I've found several serious bugs in the
> process, some of which allow remote exploits. I expect to find more
> bugs, and I'll be happy to help in any future problems that crop up
> in this area. The goal is to have an Emacs implementation that is robust,
> rather than one that crashes when given input that was thought
> "couldn't happen".
I have no problem with checks that fixes bugs. But the checks that check for
more than 2 billion command line arguments or more than 2 billion scroll bars
or more than 250 million i/o sources simply does not make sense. It is just
clutter.
Jan D.
next prev parent reply other threads:[~2011-07-30 5:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 6:44 bug#9196: integer and memory overflow issues (e.g., cut-and-paste crashes Emacs) Paul Eggert
2011-07-29 10:01 ` Jan Djärv
2011-07-29 16:21 ` Paul Eggert
2011-07-29 16:49 ` Jan Djärv
2011-07-29 21:03 ` Paul Eggert
2011-07-30 5:52 ` Jan Djärv [this message]
2011-07-30 19:16 ` Paul Eggert
2011-07-31 8:57 ` Jan Djärv
2011-08-05 2:33 ` Paul Eggert
2011-08-05 9:26 ` Jan Djärv
2011-08-06 1:24 ` Paul Eggert
2011-08-08 18:01 ` Jan Djärv
[not found] ` <handler.9196.B.131192196724343.ack@debbugs.gnu.org>
2011-08-26 16:38 ` 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=4E339C30.9090708@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=9196@debbugs.gnu.org \
--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).