linux-kernel - Re: [RFC] Deprecate a.out ELF interpreters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200708020059.25383.ak@suse.de>
Date:	Thu, 2 Aug 2007 00:59:25 +0200
From:	Andi Kleen <ak@...e.de>
To:	Theodore Tso <tytso@....edu>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Deprecate a.out ELF interpreters

On Thursday 02 August 2007 00:14:48 Theodore Tso wrote:
> Do you mean deprecate a.out interpreters?

No, just a.out interpreters for ELF binaries.

> I could imagine that there might be some people running some very old
> statically linked programs from a decade or so ago, but I agree they
> are pretty small in number.

Nothing would change for them.

The only thing that would change is that if someone has a a.out system
with ELF executables then they would need to update their ELF ld.so to ELF.
Dynamically linked a.out executables should also still run because they
use a different ld.so.

> Is the fs/binfmt_aout.c causing problems? 
> It's only 562 lines of code...

I'm not concerned about binfmt_aout; just about the special case a.out ld.so 
code in binfmt_elf.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/