From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New KASLR values in 'sysctl.conf' lead to errors
Date: Wed, 17 Jul 2019 17:40:24 +0200
Message-ID: <c7d2a953a74fea58df5eeb5769e5a3c5@ipfire.org>
In-Reply-To: <9b3fc69d-ecce-c32e-aa4c-cba12b07cc36@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3039931169066239011=="
List-Id: <development.lists.ipfire.org>

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

Ths parameters are absent on all archs except x86_64 because they=20
configure KPTI/KASLR.


On 2019-07-13 14:10, Matthias Fischer wrote:
> Hi,
>=20
> sorry, next one:
>=20
> Commit
> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3Def21f3e49d299=
8eb4a223c05ef05f169ae99537a#patch1
>=20
> "Changed sysctl values are:
>=20
> vm.mmap_rnd_bits =3D 32 (default: 28)
> vm.mmap_rnd_compat_bits =3D 16 (default: 8)"
>=20
> After 'sysctl -p' I get:
>=20
> ***SNIP***
> ...
> error: "Invalid argument" setting key "vm.mmap_rnd_bits"
> error: "vm.mmap_rnd_compat_bits" is an unknown key
> ...
> ***SNAP***
>=20
> Tested on Core 134/32bit, fresh install.
>=20
> Can anyone confirm?
>=20
> Best,
> Matthias

--===============3039931169066239011==--