From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New KASLR values in 'sysctl.conf' lead to errors
Date: Wed, 17 Jul 2019 17:27:27 +0100
Message-ID: <D89F36BF-650C-49C5-AFDA-B37C345EE9C6@ipfire.org>
In-Reply-To: <c7d2a953a74fea58df5eeb5769e5a3c5@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6908102719972171853=="
List-Id: <development.lists.ipfire.org>

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

Hi,

Arne, would you prefer an extra file for x86_64, or an initscript that checks=
 the architecture and then calls sysctl?

-Michael

> On 17 Jul 2019, at 16:40, Arne Fitzenreiter <Arne.Fitzenreiter(a)ipfire.org=
> wrote:
>=20
> Ths parameters are absent on all archs except x86_64 because they configure=
 KPTI/KASLR.
>=20
>=20
> On 2019-07-13 14:10, Matthias Fischer wrote:
>> Hi,
>> sorry, next one:
>> Commit
>> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3Def21f3e49d29=
98eb4a223c05ef05f169ae99537a#patch1
>> "Changed sysctl values are:
>> vm.mmap_rnd_bits =3D 32 (default: 28)
>> vm.mmap_rnd_compat_bits =3D 16 (default: 8)"
>> After 'sysctl -p' I get:
>> ***SNIP***
>> ...
>> error: "Invalid argument" setting key "vm.mmap_rnd_bits"
>> error: "vm.mmap_rnd_compat_bits" is an unknown key
>> ...
>> ***SNAP***
>> Tested on Core 134/32bit, fresh install.
>> Can anyone confirm?
>> Best,
>> Matthias


--===============6908102719972171853==--