linux-kernel - Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Apr 2016 16:00:05 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
Subject: Re: [PATCH v2] printk: Add kernel parameter to disable writes to
 /dev/kmsg

On Mon, 25 Apr 2016 12:54:37 -0700
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:

> > This systemd exposure has seriously eroded your sanity.  
> 
> See Andrew's message, this was added because of klibc :)

For the purpose to pass messages from early init through to final boot.
Systemd continued this for the same purpose. Which I agree is totally
legit. But where systemd fails, is that it continues to use this
interface far beyond the need.

I agree with Andrew, we should have had a way to close the pipe after
the system was up and running.

-- Steve