From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: New KASLR values in 'sysctl.conf' lead to errors
Date: Sat, 13 Jul 2019 14:10:29 +0200
Message-ID: <9b3fc69d-ecce-c32e-aa4c-cba12b07cc36@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7529443592240773082=="
List-Id: <development.lists.ipfire.org>

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

Hi,

sorry, next one:

Commit
https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3Def21f3e49d2998e=
b4a223c05ef05f169ae99537a#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

--===============7529443592240773082==--