From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 08/21] linux: Compile binfmt_misc as a module
Date: Tue, 27 Dec 2022 12:23:41 +0100
Message-ID: <F64E1E93-486F-4EDA-B3AB-5890ECF6566B@ipfire.org>
In-Reply-To: <901fdb4c-371d-520c-3720-03a73a2840ed@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4401074712546884937=="
List-Id: <development.lists.ipfire.org>

--===============4401074712546884937==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I believe some people see this as a security feature.

In IPFire 2 we don=E2=80=99t use this I think, so a module will be just fine.

Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 26 Dec 2022, at 20:27, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> Backported from IPFire 3.x as aea3e8471c0c11d4a5a1164efbe7c7c948667b6e.
>=20
> Signed-off-by: Peter M=C3=BCller <peter.mueller(a)ipfire.org>
> ---
> config/kernel/kernel.config.x86_64-ipfire | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>=20
> diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kern=
el.config.x86_64-ipfire
> index e3a57b18a..519fc8770 100644
> --- a/config/kernel/kernel.config.x86_64-ipfire
> +++ b/config/kernel/kernel.config.x86_64-ipfire
> @@ -902,7 +902,7 @@ CONFIG_COMPAT_BINFMT_ELF=3Dy
> CONFIG_ELFCORE=3Dy
> CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=3Dy
> CONFIG_BINFMT_SCRIPT=3Dy
> -CONFIG_BINFMT_MISC=3Dy
> +CONFIG_BINFMT_MISC=3Dm
> CONFIG_COREDUMP=3Dy
> # end of Executable file formats
>=20
> --=20
> 2.35.3


--===============4401074712546884937==--