linux-kernel - Re: [PATCH 13/13] android: ram_console: honor dmesg

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]

Message-ID: <20120307221041.GD16652@kroah.com>
Date:	Wed, 7 Mar 2012 14:10:41 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Nick Kralevich <nnk@...gle.com>,
	Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH 13/13] android: ram_console: honor dmesg_restrict

On Wed, Mar 07, 2012 at 01:58:23PM -0800, John Stultz wrote:
> From: Nick Kralevich <nnk@...gle.com>
> 
> The Linux kernel has a setting called dmesg_restrict. When true,
> only processes with CAP_SYSLOG can view the kernel dmesg logs. This
> helps prevent leaking of kernel information into user space.
> 
> On Android, it's possible to bypass these restrictions by viewing
> /proc/last_kmsg.
> 
> This change makes /proc/last_kmsg require the same permissions as
> dmesg.
> 
> Bug: 5555691

In what bugzilla does this bug number reference?  Random integers don't
do much for people when looking back at the history of things :)

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/