linux-kernel - Fwd: Request: Regarding the phasing out of "a.out support" in Linux Kernels

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>] [day] [month] [year] [list]

Message-ID: <CADt9uB=RkXXbvOOSCPmx8sMnoESd4yA+apda2fo-Yy5jYPYe3Q@mail.gmail.com>
Date:   Sat, 9 Apr 2022 16:38:21 +0100
From:   NULL <ayz.out@...il.com>
To:     unlisted-recipients:; (no To-header on input)
Cc:     linux-kernel@...r.kernel.org
Subject: Fwd: Request: Regarding the phasing out of "a.out support" in Linux Kernels

 Forwarding To Relevant People.
 (Have been unable to respond to previous talks, many apologies for
the late input.)

  --------- Forwarding message --------
From: <ayz.out@...il.com>
Date: Apr 9, 2022
 Subject: Request: Regarding the phasing out of "a.out support" in Linux Kernels

To: <bp@...en8.de>, <x86@...nel.org>
Cc: <linux-kernel@...r.kernel.org>, <bp@...e.de>, <arnd@...db.de>

Noticed in the previous conversations that it was mentioned nobody had
complained of it being removed, I do understand that everything must
be taken out eventually...

But I still wanted to ask that it remain active in 5.18's full release
while announced that it would be inactive/turned off by default in the
future 5.19 & 5.20 releases (5.20 being the last that would have it as
inactive before full removal of related code) if LTS

I feel that would be considered a fair & reasonable 'heads up' and
provide a modern LTS version of the kernel that has the function still
available by default.
 This is just a simple request from an interested user of Linux that
wouldn't be as qualified or experienced as some of the others involved
in the decision making process & I always would of-course respect
whatever final decision that everyone lands on after the discussions
are closed. :3