From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: New KASLR values in 'sysctl.conf' lead to errors
Date: Sun, 14 Jul 2019 14:16:00 +0000
Message-ID: <4ab74054-e6cc-5bc9-a653-40797641f0aa@ipfire.org>
In-Reply-To: <9b3fc69d-ecce-c32e-aa4c-cba12b07cc36@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3230623926424285614=="
List-Id: <development.lists.ipfire.org>

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

Hello Matthias,

hm, the systctls are present on my 64 bit testing machine:

> [root(a)maverick ~]# sysctl -p
> - snip -
> vm.mmap_rnd_bits =3D 32
> vm.mmap_rnd_compat_bits =3D 16
> - snip -
> [root(a)maverick ~]# arch
> x86_64

Unfortunately I do not have 32 bit hardware at hand, and
the absence of those parameters surprises me.

@All: Does anybody have access to something more uncommon
like ARM SOCs? What about those?

@All, second: Does it make sense to ship different sysctl
values for different platforms?

Sorry for the inconvenience.

Thanks, and best regards,
Peter M=C3=BCller


> 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
>=20

--=20
The road to Hades is easy to travel.
	-- Bion of Borysthenes

--===============3230623926424285614==--