[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5b86abe3-2c9d-1396-777d-a5a8f19555ef@nbd.name>
Date: Mon, 18 Dec 2017 10:55:34 +0100
From: Felix Fietkau <nbd@....name>
To: "Tobin C. Harding" <me@...in.cc>, kernel-hardening@...ts.openwall.com
Cc: Steven Rostedt <rostedt@...dmis.org>, Tycho Andersen <tycho@...ho.ws>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>, Andrew Morton
<akpm@...ux-foundation.org>, Daniel Borkmann <daniel@...earbox.net>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Alexei Starovoitov <ast@...nel.org>, linux-kernel@...r.kernel.org,
Network Development <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/3] kallsyms: don't leak address when symbol not found
On 2017-12-18 00:53, Tobin C. Harding wrote:
> Currently if kallsyms_lookup() fails to find the symbol then the address
> is printed. This potentially leaks sensitive information. Instead of
> printing the address we can return an error, giving the calling code the
> option to print the address or print some sanitized message.
>
> Return error instead of printing address to argument buffer. Leave
> buffer in a sane state.
>
> Signed-off-by: Tobin C. Harding <me@...in.cc>
I think there should be a way to keep the old behavior for debugging.
- Felix
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
