Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1600859
| From | Krzysztof Kozlowski <krzk@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form |
| Date | 2017-03-14 21:00 +0100 |
| Message-ID | <tl0LU-4YP-15@gated-at.bofh.it> (permalink) |
| References | <tkZwu-4b2-3@gated-at.bofh.it> <tkZZv-4D5-9@gated-at.bofh.it> <tkZZv-4D5-7@gated-at.bofh.it> <tl09c-4Iz-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Mar 14, 2017 at 08:17:35PM +0100, Tobias Jakobi wrote: > Krzysztof Kozlowski wrote: > > On Tue, Mar 14, 2017 at 08:01:41PM +0100, Tobias Jakobi wrote: > >> Hello Krzysztof, > >> > >> I was wondering about the benefit of this. From a quick look these are > >> all messages that end up in the kernel log / dmesg. > >> > >> IIRC %pK does nothing there, since dmest_restrict is supposed to be used > >> to deny an unpriviliged user the access to the kernel log. > >> > >> Or am I missing something here? > > > > These are regular printks so depending on kernel options (e.g. dynamic > > debug, drm.debug) these might be printed also in the console. Of course > > we could argue then if access to one of the consoles is worth > > securing. > This here suggests otherwise. > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/sysctl/kernel.txt#n388 > > I have not tested this, but IIRC %pK is not honored by the kernel > logging infrastucture. That's why dmesg_restrict is there. > > Correct me if I'm wrong. The %pK will not help for dmesg or /proc/kmsg but it will help for console (/dev/ttySACN, ttySN etc) because effectively it uses the same vsprintf()/pointer() functions. As I said, we could argue whether securing console is worth... usually attacker having access to it has also physical access to the machine so everything gets easier... Best regards, Krzysztof
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] drm/exynos: Print kernel pointers in a restricted form Krzysztof Kozlowski <krzk@kernel.org> - 2017-03-14 19:40 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Krzysztof Kozlowski <krzk@kernel.org> - 2017-03-14 20:10 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Tobias Jakobi <tjakobi@math.uni-bielefeld.de> - 2017-03-14 20:20 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Krzysztof Kozlowski <krzk@kernel.org> - 2017-03-14 21:00 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Tobias Jakobi <tjakobi@math.uni-bielefeld.de> - 2017-03-14 21:50 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Andrzej Hajda <a.hajda@samsung.com> - 2017-03-15 08:40 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Tobias Jakobi <tjakobi@math.uni-bielefeld.de> - 2017-03-15 13:40 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Tobias Jakobi <tjakobi@math.uni-bielefeld.de> - 2017-03-14 20:10 +0100
Re: [PATCH] drm/exynos: Print kernel pointers in a restricted form Inki Dae <inki.dae@samsung.com> - 2017-03-15 06:00 +0100
csiph-web