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: <CA+55aFxNyH_i0=02S-ZLw2wLFEAY8Dkb0zm1HT9avp+KYNtVeg@mail.gmail.com>
Date:	Wed, 6 Apr 2016 14:32:30 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Kees Cook <keescook@...omium.org>
Cc:	Emrah Demir <ed@...sec.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dan Rosenberg <dan.j.rosenberg@...il.com>,
	"kernel-hardening@...ts.openwall.com" 
	<kernel-hardening@...ts.openwall.com>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH] KERNEL: resource: Fix bug on leakage in /proc/iomem file

On Wed, Apr 6, 2016 at 2:27 PM, Kees Cook <keescook@...omium.org> wrote:
>
> Hrm, okay. I still think just changing the perms would be less
> troublesome.

No, that would be much *more* trouble-some, because we have things
like bug-reporting documentation that tells people to send /proc/iomem
etc information on crashes. There may well be scripts like that out
there.

So it's much more likely that just removing the "Kernel code" etc
lines is not going to break anything.

            Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ