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]
Date:	Sat, 5 Mar 2011 00:10:39 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Dan Rosenberg <drosenberg@...curity.com>
Cc:	Matt Mackall <mpm@...enic.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Theodore Tso <tytso@....edu>, cl@...ux-foundation.org,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Make /proc/slabinfo 0400

Hi Dan,

On Fri, Mar 4, 2011 at 11:44 PM, Dan Rosenberg <drosenberg@...curity.com> wrote:
> This is a good point, and one that I've come to accept as a result of
> having this conversation.  Consider the patch dropped, unless there are
> other reasons I've missed.  I still think it's worth brainstorming
> techniques for hardening the kernel heap in ways that don't create
> performance impact, but I admit that the presence or absence of this
> debugging information isn't a crucial factor in successful exploitation.

I can think of four things that will make things harder for the
attacker (in the order of least theoretical performance impact):

  (1) disable slub merging

  (2) pin down random objects in the slab during setup (i.e. don't
allow them to be allocated)

  (3) randomize the initial freelist

  (4) randomize padding between objects in a slab

AFAICT, all of them will make brute force attacks using the kernel
heap as an attack vector harder but won't prevent them.

                        Pekka
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ