From: Andrew Morton <akpm@osdl.org>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org, ericy@cais.com
Subject: Re: [PATCH][RFC] invalid ELF binaries can execute - better sanity checking
Date: Thu, 8 Jan 2004 19:20:21 -0800 [thread overview]
Message-ID: <20040108192021.6c2aea60.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0401090236390.11276@jju_lnx.backbone.dif.dk>
Jesper Juhl <juhl@dif.dk> wrote:
>
> The current Linux kernel does only very basic sanity checking on ELF
> binaries.
I've always had little confidence in the elf loader. The problem is
complex, the code quality is not high and the consequences of an error are
severe.
I guess others realise this, and the bad guys have probably already
"audited" the code for us, but still.
I'll merge your additional checks for testing and would encourage you to
keep looking at the problem, thanks.
next prev parent reply other threads:[~2004-01-09 3:19 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 [this message]
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
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=20040108192021.6c2aea60.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ericy@cais.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox