From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] -ow features
Date: Sat, 30 Jul 2011 02:42:01 +0400 [thread overview]
Message-ID: <20110729224201.GA14029@openwall.com> (raw)
In-Reply-To: <20110729180614.GB2623@albatros>
Vasiliy,
On Fri, Jul 29, 2011 at 10:06:14PM +0400, Vasiliy Kulikov wrote:
> On Fri, Jul 29, 2011 at 21:30 +0400, Solar Designer wrote:
> > In -ow, there's also CONFIG_BINFMT_ELF_AOUT. When it is not enabled -
> > and by default it is not - uselib(2) is disabled (returns -ENOSYS) and
> > parts of binfmt_elf.c responsible for loading a.out libraries for ELF
> > binaries are also disabled (truly ancient stuff). We need something
> > like this for 3.x and RHEL6 kernels too.
> >
> > Maybe the CONFIG_BINFMT_ELF_AOUT option may be accepted upstream on the
> > grounds that it's similar to other CONFIG_BINFMT_* options?
>
> Do you propose to move all ELF_AOUT code to a configurable option, just
Yes.
> like STRICT_DEVMEM?
I'm not sure why you mention this one as an example. 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.
Alexander
next prev parent reply other threads:[~2011-07-29 22:42 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 [this message]
2011-07-30 18:20 ` [kernel-hardening] BINFMT_ELF_AOUT (was: -ow features) Vasiliy Kulikov
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=20110729224201.GA14029@openwall.com \
--to=solar@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 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.