From: Christoph Hellwig <hch@infradead.org>
To: Maciej Zenczykowski <maze@cela.pl>
Cc: Jesper Juhl <juhl-lkml@dif.dk>,
Valdis.Kletnieks@vt.edu, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] invalid ELF binaries can execute - better sanity checking
Date: Fri, 9 Jan 2004 20:41:50 +0000 [thread overview]
Message-ID: <20040109204150.A28436@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401092105070.1739-100000@gaia.cela.pl>; from maze@cela.pl on Fri, Jan 09, 2004 at 09:20:53PM +0100
On Fri, Jan 09, 2004 at 09:20:53PM +0100, Maciej Zenczykowski wrote:
> I think this points to an 'issue', if we're going to increase the checks
> in the ELF-loader (and thus increase the size of the minimal valid ELF
> file we can load, thus effectively 'bloating' (lol) some programs) we
> should probably allow some sort of direct binary executable files [i.e.
> header 'XBIN386\0' followed by Read/Execute binary code to execute by
Like binfmt_flat? :)
next prev parent reply other threads:[~2004-01-09 20:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 2:19 [PATCH][RFC] invalid ELF binaries can execute - better sanity checking Jesper Juhl
2004-01-09 2:27 ` Jesper Juhl
2004-01-09 3:20 ` Andrew Morton
2004-01-09 3:36 ` Valdis.Kletnieks
2004-01-09 3:40 ` Jesper Juhl
2004-01-09 20:20 ` Maciej Zenczykowski
2004-01-09 20:41 ` Christoph Hellwig [this message]
2004-01-10 0:27 ` Xavier Bestel
2004-01-10 2:27 ` Maciej Zenczykowski
2004-01-10 9:52 ` Xavier Bestel
2004-01-10 13:41 ` Jesper Juhl
2004-01-10 22:38 ` Maciej Zenczykowski
2004-01-10 22:45 ` Jesper Juhl
2004-01-10 14:05 ` Willy Tarreau
2004-01-22 19:24 ` [PATCH][RFC] invalid ELF binaries can execute - better sanitychecking Adrian Bunk
2004-01-09 3:36 ` [PATCH][RFC] invalid ELF binaries can execute - better sanity checking Jesper Juhl
2004-01-09 4:15 ` Anton Blanchard
2004-01-09 10:28 ` Jakub Jelinek
2004-01-09 10:50 ` Jesper Juhl
2004-01-09 18:08 ` Mike Fedyk
2004-01-09 18:25 ` Jesper Juhl
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=20040109204150.A28436@infradead.org \
--to=hch@infradead.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@cela.pl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox