Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #62083 > unrolled thread

Bug#908570: linux 4.18: dmesg readable as normal user

Back to article view | Back to linux.debian.kernel

Contents

  Bug#908570: linux 4.18: dmesg readable as normal user Philipp Kern <pkern@debian.org> - 2018-09-11 12:10 +0200
    Bug#908570: linux 4.18: dmesg readable as normal user Yves-Alexis Perez <corsac@debian.org> - 2018-09-11 13:10 +0200
    Bug#908570: linux 4.18: dmesg readable as normal user Bastian Blank <waldi@debian.org> - 2018-09-11 13:20 +0200
    Bug#908570: marked as done (linux 4.18: dmesg readable as normal  user) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-09-11 15:00 +0200

#62083 — Bug#908570: linux 4.18: dmesg readable as normal user

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.)

Kind regards and thanks
Philipp Kern

[toc] | [next] | [standalone]

#62084

-----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.)

Hi,

what's the content of kernel.dmesg_restrict sysctl?

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAluXoQEACgkQ3rYcyPpX
RFvgjAf9Eved9RcnEV9wTL7afPosjoM0VdVBKZ80e9uYCTJHQ3zTkVkpBXAEVMgO
uGkqDhqImtnPp4bR9bHFFwXMnCOHbJL/GKEZQ9CikNZmUuj3OUgs7+jonJL3z+tP
XZCmU/A/BnHmuGLwc8wctS6Nz7rMROhOmdd/NAtsLtK0So6xS+s/T1rGq2HGdsrs
X6ltIqXoe/5FECbejurPR7GoeQuDULxK91NAoc6YeNu/ZmyD9A5vQdc5x9MPw4zg
kO6Z/S1qYuwjzqNpSr+0HYKg4kU3EqJLxyfLUC4ojGIdHg0Q17JmAy5h9cUW5PpS
lE+WhCsVNyhfjBQjZU5HmcrJ8KPOjQ==
=Jn7s
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#62085

On Tue, Sep 11, 2018 at 12:01:32PM +0200, Philipp Kern wrote:
> 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:

Unreproducible:

| % uname -a
| Linux tilthammer 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64 GNU/Linux
| % cat /dev/kmsg
| cat: /dev/kmsg: Operation not permitted

Bastian

-- 
Without freedom of choice there is no creativity.
		-- Kirk, "The return of the Archons", stardate 3157.4

[toc] | [prev] | [next] | [standalone]

#62086 — Bug#908570: marked as done (linux 4.18: dmesg readable as normal user)

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web