[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13fdd006-3070-fb6a-cd99-7f845deb6843@kernel.org>
Date: Thu, 4 Feb 2021 16:20:45 -0600
From: Timur Tabi <timur@...nel.org>
To: Kees Cook <keescook@...omium.org>, Pavel Machek <pavel@....cz>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
willy@...radead.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, roman.fietze@...na.com,
john.ogness@...utronix.de, akinobu.mita@...il.com
Subject: Re: [PATCH] lib/vsprintf: make-printk-non-secret printks all
addresses as unhashed
On 2/4/21 4:17 PM, Kees Cook wrote:
> It's just semantics. Printing addresses DOES weaken the security of a
> system, especially when we know attackers have and do use stuff from dmesg
> to tune their attacks. How about "reduces the security of your system"?
I think we're bikeshedding now, but I can replace "compromise" with
"reduce".
"Kernel memory addresses are exposed, which may reduce the security of
your system."
Powered by blists - more mailing lists