Your message dated Tue, 11 Sep 2018 14:55:50 +0200 with message-id <d096b3351988f29d482bcd9c0bd4ef1c@debian.org> and subject line Re: Bug#908570: linux 4.18: dmesg readable as normal user has caused the Debian Bug report #908570, regarding linux 4.18: dmesg readable as normal user to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 908570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908570 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux 4.18: dmesg readable as normal user
- From: Philipp Kern <pkern@debian.org>
- Date: Tue, 11 Sep 2018 12:01:32 +0200
- Message-id: <[🔎] 48e0eb3a5a0e0044de4559aa916ffdf7@debian.org>
Source: linux Version: 4.18.6-1Unfortunately I have experienced this on a rebuilt package and cannot easily test with the one actually in Debian unstable, but for me dmesg seems to work as a normal user again. "cat /dev/kmsg" just works:[...] open("/dev/kmsg", O_RDONLY|O_NONBLOCK) = 3 lseek(3, 0, SEEK_DATA) = 0 read(3, "5,0,0,-;Linux version 4.18.0-1ro"..., 8191) = 157 [...] % grep DMESG /boot/config-4.18.0-1rodete1-amd64 CONFIG_SECURITY_DMESG_RESTRICT=y(We do very, very minimal patching to the kernel to make it work for us, hence the different ABI version. And it'd really help us if the ABI version were to be bumped with every upload.)Kind regards and thanks Philipp Kern
--- End Message ---
--- Begin Message ---
- To: Yves-Alexis Perez <corsac@debian.org>
- Cc: 908570-done@bugs.debian.org
- Subject: Re: Bug#908570: linux 4.18: dmesg readable as normal user
- From: Philipp Kern <pkern@debian.org>
- Date: Tue, 11 Sep 2018 14:55:50 +0200
- Message-id: <d096b3351988f29d482bcd9c0bd4ef1c@debian.org>
- In-reply-to: <[🔎] 56b8085026e4453a377b84aace529f4370fe4684.camel@debian.org>
- References: <[🔎] 48e0eb3a5a0e0044de4559aa916ffdf7@debian.org> <[🔎] 56b8085026e4453a377b84aace529f4370fe4684.camel@debian.org>
On 2018-09-11 13:03, Yves-Alexis Perez wrote:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, 2018-09-11 at 12:01 +0200, Philipp Kern wrote:Source: linux Version: 4.18.6-1 Unfortunately I have experienced this on a rebuilt package and cannot easily test with the one actually in Debian unstable, but for me dmesg seems to work as a normal user again. "cat /dev/kmsg" just works: [...] open("/dev/kmsg", O_RDONLY|O_NONBLOCK) = 3 lseek(3, 0, SEEK_DATA) = 0 read(3, "5,0,0,-;Linux version 4.18.0-1ro"..., 8191) = 157 [...] % grep DMESG /boot/config-4.18.0-1rodete1-amd64 CONFIG_SECURITY_DMESG_RESTRICT=y(We do very, very minimal patching to the kernel to make it work for us,hence the different ABI version. And it'd really help us if the ABI version were to be bumped with every upload.)what's the content of kernel.dmesg_restrict sysctl?Thanks Yves, for pointing out the obvious. Looks like I got confused between machines and we indeed set that to 0. Sorry for the noise and thanks a lot for the help.Kind regards Philipp Kern
--- End Message ---