All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lehmann <aaronl@vitelus.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, Eric Youngdale <eric@andante.org>,
	Eric Youngdale <ericy@cais.com>
Subject: Re: [PATCH] stronger ELF sanity checks v2
Date: Mon, 12 Jan 2004 19:32:34 -0800	[thread overview]
Message-ID: <20040113033234.GD2000@vitelus.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0401130228490.2265@jju_lnx.backbone.dif.dk>

On Tue, Jan 13, 2004 at 02:55:07AM +0100, Jesper Juhl wrote:
> Here's the second version of my patch to add better sanity checks for
> binfmt_elf

I assume this breaks Brian Raiter's tiny ELF executables[1]. Even
though these binaries are evil hacks that don't comply to standards
and serve no serious purpose, I'm not sure what the purpose of the
sanity checks is. Are there any risks associated with running
non-compliant ELF executables? (Now that I mention it, the
proof-of-concept exploit for the brk() hole comes to mind, but I don't
know offhand if that did anything against the spec.) I don't mean to
question the usefulness of your work, especially as I don't know much
about ELF, but I'm personally curious about why you think additional
sanity checks are worth a slight increase in code complexity.

1. http://www.muppetlabs.com/~breadbox/software/tiny/

  reply	other threads:[~2004-01-13  3:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  1:55 [PATCH] stronger ELF sanity checks v2 Jesper Juhl
2004-01-13  3:32 ` Aaron Lehmann [this message]
2004-01-13 10:39   ` Eric W. Biederman
2004-01-16 16:08   ` Pavel Machek
2004-01-16 19:55     ` Jesse Pollard
2004-01-16 21:36       ` Pavel Machek
2004-01-13 17:35 ` Jakub Jelinek
2004-01-13 19:54   ` Jesper Juhl
2004-01-15  7:43     ` Ulrich Drepper
     [not found] <1dmam-2Xk-11@gated-at.bofh.it>
     [not found] ` <1dAQW-109-3@gated-at.bofh.it>
     [not found]   ` <1dCSg-5vk-55@gated-at.bofh.it>
     [not found]     ` <1eaqw-6Dk-29@gated-at.bofh.it>
2004-01-15 13:13       ` Pascal Schmidt

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=20040113033234.GD2000@vitelus.com \
    --to=aaronl@vitelus.com \
    --cc=akpm@osdl.org \
    --cc=eric@andante.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.