From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Dumper issue, revisited; invalid realloc/free Date: Wed, 04 Feb 2015 22:36:28 +0200 Message-ID: <83fvalfm7n.fsf@gnu.org> References: <20150204175709.GX23507@brightrain.aerifal.cx> <83oap9fppc.fsf@gnu.org> <20150204193732.GZ23507@brightrain.aerifal.cx> <83k2zxfomm.fsf@gnu.org> <20150204194910.GA23507@brightrain.aerifal.cx> <83iofhfo5d.fsf@gnu.org> <20150204200215.GB23507@brightrain.aerifal.cx> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1423082210 19552 80.91.229.3 (4 Feb 2015 20:36:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 4 Feb 2015 20:36:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Rich Felker Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 04 21:36:46 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YJ6gm-0007cq-PF for ged-emacs-devel@m.gmane.org; Wed, 04 Feb 2015 21:36:44 +0100 Original-Received: from localhost ([::1]:38685 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ6gm-0000OG-61 for ged-emacs-devel@m.gmane.org; Wed, 04 Feb 2015 15:36:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39279) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ6gh-0000MI-In for emacs-devel@gnu.org; Wed, 04 Feb 2015 15:36:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YJ6ge-0002UZ-Th for emacs-devel@gnu.org; Wed, 04 Feb 2015 15:36:39 -0500 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:51379) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ6ge-0002UH-MC for emacs-devel@gnu.org; Wed, 04 Feb 2015 15:36:36 -0500 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NJ900C00KYPGL00@mtaout29.012.net.il> for emacs-devel@gnu.org; Wed, 04 Feb 2015 22:32:53 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NJ9005Y7L2S7Q60@mtaout29.012.net.il>; Wed, 04 Feb 2015 22:32:53 +0200 (IST) In-reply-to: <20150204200215.GB23507@brightrain.aerifal.cx> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:182402 Archived-At: > Date: Wed, 4 Feb 2015 15:02:15 -0500 > From: Rich Felker > Cc: emacs-devel@gnu.org > > glibc is maintained by a consensus-based community these days, and I > don't think sacrificing the ability to detect serious memory > corruption that likely indicates an exploit attempt for the sake of > satisfying emacs' invalid assumptions about malloc would be popular. It can be done without sacrificing anything. > The same checks can be made on the emacs side before calling the > underlying realloc/free Yes, they can. Both alternative require some knowledge of the other side, so they are both equivalent to some degree.