Bug#867747: reopening 867747, reassign 867747 to initscripts ...

Dmitry Bogatov KAction at debian.org
Mon Nov 19 13:05:24 GMT 2018

[2017-07-11 03:35] Michael Biebl <biebl at debian.org>
> reopen 867747 
> reassign 867747 initscripts 
> retitle 867747 /var/log/dmesg world-readable despite kernel.dmesg_restrict = 1
> thanks

Interesting. On my system `/var/log/dmesg' is 640, root:adm, which is
quite restrictive. If I run `/etc/init.d/bootlogs' again, it stays so.

But if I remove `/var/log/dmesg' and re-run `/etc/init.d/bootlogs',
`/var/log/dmesg' becomes 644.

I believe adjustment to `/etc/init.d/bootlogs' to check
`kernel.dmesg_restrict' is needed. By the way, any ideas how could I
have 640 `/var/log/dmesg' in first place?

More information about the Debian-init-diversity mailing list