On mer., 2016-01-13 at 15:29 -0500, Daniel Kahn Gillmor wrote:
> > It's not that they are not supported, but rather that you don't have
> > permission to write them. By chance, is kernel.grsecurity.grsec_lock set
> to 1?
>
> yes, it's set to 1 inside /etc/sysctl.d/grsec.conf itself (i haven't
>
Package: linux-grsec-base
Version: 5
Severity: normal
by default, the systemd-sysctl.service service cannot start up
successfully on this machine, because of some kernel settings in
/etc/sysctl.d/grsec.conf which do not appear to be supported.
here is relevant output from journalctl:
-- Unit
On mer., 2016-01-13 at 13:44 -0500, Daniel Kahn Gillmor wrote:
> by default, the systemd-sysctl.service service cannot start up
> successfully on this machine, because of some kernel settings in
> /etc/sysctl.d/grsec.conf which do not appear to be supported.
It's not that they are not supported,
On Wed 2016-01-13 15:05:02 -0500, Yves-Alexis Perez wrote:
> On mer., 2016-01-13 at 13:44 -0500, Daniel Kahn Gillmor wrote:
>> by default, the systemd-sysctl.service service cannot start up
>> successfully on this machine, because of some kernel settings in
>> /etc/sysctl.d/grsec.conf which do not
On in https://bugs.debian/810920, Yves-Alexis Perez wrote:
> Didn't test yet, but if sysctl are applied in initrd, yes that makes sense.
> Unfortunately there's not much I can do here.
Maybe this needs to be reassigned to systemd or dracut or something if
it's not a bug in grsec itself?
How
5 matches
Mail list logo
