public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: Vasiliy Kulikov <segoon@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] BINFMT_ELF_AOUT (was: -ow features)
Date: Sat, 30 Jul 2011 22:20:02 +0400	[thread overview]
Message-ID: <20110730182002.GA4128@albatros> (raw)
In-Reply-To: <20110729224201.GA14029@openwall.com>

Solar,

On Sat, Jul 30, 2011 at 02:42 +0400, Solar Designer wrote:
> > like STRICT_DEVMEM?
> 
> I'm not sure why you mention this one as an example.

Because it guards some doubtful feature, which is considered harmful for
the generic system.

>  I think the
> CONFIG_BINFMT_ELF_AOUT name may be used, and this option will thus look
> (and work) similar to other CONFIG_BINFMT_* options.
> 
> > Looks like a good plan - kernel developers don't
> > like to support legacy stuff.  If it is moved to a config option, then
> > in some years it could be even fully removed (if I understand the AOUT
> > significance).
> 
> Right.  This stuff has been obsolete for 15+ years, at least for native
> Linux binaries.

Looks like it was almost fully removed in 2.6.25:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d20894a23708c2af75966534f8e4dedb46d48db2

The only untouched part is load_elf_library().  I think I can simply
remove it in the proposed patch as full a.out removal from ELF format
was scheduled in 2.6.25.

Thanks,

-- 
Vasiliy

      reply	other threads:[~2011-07-30 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 16:27 [kernel-hardening] -ow features Solar Designer
2011-07-29  9:00 ` Vasiliy Kulikov
2011-07-29 17:30   ` Solar Designer
2011-07-29 18:00     ` Vasiliy Kulikov
2011-07-29 18:06     ` Vasiliy Kulikov
2011-07-29 22:42       ` Solar Designer
2011-07-30 18:20         ` Vasiliy Kulikov [this message]

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=20110730182002.GA4128@albatros \
    --to=segoon@openwall.com \
    --cc=kernel-hardening@lists.openwall.com \
    /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