Date: Wed, 8 Nov 2017 07:51:48 +1100 From: "Tobin C. Harding" <me@...in.cc> To: Greg KH <gregkh@...uxfoundation.org> Cc: kernel-hardening@...ts.openwall.com, "Jason A. Donenfeld" <Jason@...c4.com>, Theodore Ts'o <tytso@....edu>, Linus Torvalds <torvalds@...ux-foundation.org>, Kees Cook <keescook@...omium.org>, Paolo Bonzini <pbonzini@...hat.com>, Tycho Andersen <tycho@...ker.com>, "Roberts, William C" <william.c.roberts@...el.com>, Tejun Heo <tj@...nel.org>, Jordan Glover <Golden_Miller83@...tonmail.ch>, Petr Mladek <pmladek@...e.com>, Joe Perches <joe@...ches.com>, Ian Campbell <ijc@...lion.org.uk>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <wilal.deacon@....com>, Steven Rostedt <rostedt@...dmis.org>, Chris Fries <cfries@...gle.com>, Dave Weinstein <olorin@...gle.com>, Daniel Micay <danielmicay@...il.com>, Djalal Harouni <tixxdz@...il.com>, linux-kernel@...r.kernel.org, Network Development <netdev@...r.kernel.org>, David Miller <davem@...emloft.net> Subject: Re: [PATCH v4] scripts: add leaking_addresses.pl On Tue, Nov 07, 2017 at 11:50:27AM +0100, Greg KH wrote: > On Tue, Nov 07, 2017 at 09:32:11PM +1100, Tobin C. Harding wrote: > > Currently we are leaking addresses from the kernel to user space. This > > script is an attempt to find some of those leakages. Script parses > > `dmesg` output and /proc and /sys files for hex strings that look like > > kernel addresses. > > > > Only works for 64 bit kernels, the reason being that kernel addresses > > on 64 bit kernels have 'ffff' as the leading bit pattern making greping > > possible. On 32 kernels we don't have this luxury. > > > > Scripts is _slightly_ smarter than a straight grep, we check for false > > positives (all 0's or all 1's, and vsyscall start/finish addresses). > > > > Output is saved to file to expedite repeated formatting/viewing of > > output. > > > > Signed-off-by: Tobin C. Harding <me@...in.cc> > > --- > > > > This version outputs a report instead of the raw results by default. Designing > > this proved to be non-trivial, the reason being that it is not immediately clear > > what constitutes a duplicate entry (similar message, address range, same > > file?). Also, the aim of the report is to assist users _not_ missing correct > > results; limiting the output is inherently a trade off between noise and > > correct, clear results. > > > > Without testing on various real kernels its not clear that this reporting is any > > good, my test cases were a bit contrived. Your usage may vary. > > > > It would be super helpful to get some comments from people running this with > > different set ups. > > > > Please feel free to say 'try harder Tobin, this reporting is shit'. > > > > Thanks, appreciate your time, > > Tobin. > > > > v4: > > - Add `scan` and `format` sub-commands. > > - Output report by default. > > - Add command line option to send scan results (to me). > > As the script is already in Linus's tree, you might need to send a patch > on top of that, instead of this one, as this one will not apply anymore. Your awareness of what is going on never ceases to amaze me Greg, you're the man. thanks, Tobin.
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.