linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Northup <digitaleric@google.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kees Cook <keescook@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
	Jarkko Sakkinen <jarkko.sakkinen@intel.com>,
	Matthew Garrett <mjg@redhat.com>,
	Matt Fleming <matt.fleming@intel.com>,
	Dan Rosenberg <drosenberg@vsecurity.com>,
	Julien Tinnes <jln@google.com>, Will Drewry <wad@chromium.org>
Subject: Re: [PATCH 3/3] x86: kernel base offset ASLR
Date: Thu, 4 Apr 2013 14:04:44 -0700	[thread overview]
Message-ID: <CAG7+5M0ohMrCG1obmy1kaP+R1Qykcu1nn_L1c4L8RFpvrWmgcQ@mail.gmail.com> (raw)
In-Reply-To: <7b09fa09-8ab7-4189-b86b-59fa6a9fbe0e@email.android.com>

On Thu, Apr 4, 2013 at 2:01 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> What system monitoring?  Most systems don't have much...

The security of an unmonitored system is going to be much lower than
of a well-monitored system.  That's true independent of whether kASLR
is deployed.

>
> Kees Cook <keescook@chromium.org> wrote:
>
>>On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>>> It seems to me that you are assuming that the attacker is targeting a
>>specific system, but a bot might as well target 256 different systems
>>and see what sticks...
>>
>>Certainly, but system monitoring will show 255 crashed machines, which
>>is a huge blip on any radar. :)
>>
>>-Kees
>>
>>>
>>> Kees Cook <keescook@chromium.org> wrote:
>>>
>>>>On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>>>>> On 04/04/2013 01:07 PM, Kees Cook wrote:
>>>>>> However, the benefits of
>>>>>> this feature in certain environments exceed the perceived
>>>>weaknesses[2].
>>>>>
>>>>> Could you clarify?
>>>>
>>>>I would summarize the discussion of KASLR weaknesses into to two
>>>>general observations:
>>>>1- it depends on address location secrecy and leaks are common/easy.
>>>>2- it has low entropy so attack success rates may be high.
>>>>
>>>>For "1", as Julien mentions, remote attacks and attacks from a
>>>>significantly contained process (via seccomp-bpf) minimizes the leak
>>>>exposure. For local attacks, cache timing attacks and other things
>>>>also exist, but the ASLR can be improved to defend against that too.
>>>>So, KASLR is useful on systems that are virtualization hosts,
>>>>providing remote services, or running locally confined processes.
>>>>
>>>>For "2", I think that the comparison to userspace ASLR entropy isn't
>>>>as direct. For userspace, most systems don't tend to have any kind of
>>>>watchdog on segfaulting processes, so a remote attacker could just
>>>>keep trying an attack until they got lucky, in which case low entropy
>>>>is a serious problem. In the case of KASLR, a single attack failure
>>>>means the system goes down, which makes mounting an attack much more
>>>>difficult. I think 8 bits is fine to start with, and I think start
>>>>with a base offset ASLR is a good first step. We can improve things
>>in
>>>>the future.
>>>>
>>>>-Kees
>>>>
>>>>--
>>>>Kees Cook
>>>>Chrome OS Security
>>>
>>> --
>>> Sent from my mobile phone. Please excuse brevity and lack of
>>formatting.
>>
>>
>>
>>--
>>Kees Cook
>>Chrome OS Security
>
> --
> Sent from my mobile phone. Please excuse brevity and lack of formatting.

  reply	other threads:[~2013-04-04 21:04 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 20:07 [PATCH 0/3] kernel ASLR Kees Cook
2013-04-04 20:07 ` [PATCH 1/3] x86: routines to choose random kernel base offset Kees Cook
2013-04-05  7:24   ` Ingo Molnar
2013-04-05  7:36     ` Ingo Molnar
2013-04-05 18:15       ` H. Peter Anvin
2013-04-04 20:07 ` [PATCH 2/3] x86: build reloc tool for both 64 and 32 bit Kees Cook
2013-04-05  7:13   ` Ingo Molnar
2013-04-04 20:07 ` [PATCH 3/3] x86: kernel base offset ASLR Kees Cook
2013-04-04 20:12   ` H. Peter Anvin
2013-04-04 20:19     ` Julien Tinnes
2013-04-04 20:23       ` Julien Tinnes
2013-04-04 20:27         ` H. Peter Anvin
2013-04-04 20:48           ` Julien Tinnes
2013-04-05  7:05             ` Ingo Molnar
2013-04-04 20:54     ` Kees Cook
2013-04-04 20:58       ` H. Peter Anvin
2013-04-04 21:00         ` Kees Cook
2013-04-04 21:01           ` H. Peter Anvin
2013-04-04 21:04             ` Eric Northup [this message]
2013-04-04 21:06             ` Kees Cook
2013-04-04 21:00         ` Julien Tinnes
2013-04-04 21:01         ` Eric Northup
2013-04-05  7:55           ` Ingo Molnar
2013-04-04 20:21   ` H. Peter Anvin
2013-04-04 20:47     ` Eric Northup
2013-04-05  1:08       ` H. Peter Anvin
2013-04-05  8:04     ` Ingo Molnar
2013-04-05 15:30       ` H. Peter Anvin
2013-04-08 11:58         ` Ingo Molnar
2013-04-08 14:58           ` H. Peter Anvin
2013-04-05 18:17       ` H. Peter Anvin
2013-04-05 20:01     ` Yinghai Lu
2013-04-05 20:05       ` H. Peter Anvin
2013-04-05 20:19         ` Yinghai Lu
2013-04-05 20:29           ` H. Peter Anvin
2013-04-05  7:11   ` Ingo Molnar
2013-04-05 22:06     ` Julien Tinnes
2013-04-05 22:08       ` H. Peter Anvin
2013-04-05 22:13         ` Julien Tinnes
2013-04-05  7:34   ` Ingo Molnar
2013-04-05 12:12   ` Jiri Kosina
2013-04-05 14:49   ` Borislav Petkov
2013-04-05 20:19     ` Julien Tinnes
2013-04-05 20:43       ` Borislav Petkov
2013-04-05 23:18         ` Kees Cook
2013-04-06 10:10           ` Borislav Petkov
2013-04-08 12:13         ` Ingo Molnar
2013-04-11 20:52 ` [PATCH 0/3] kernel ASLR H. Peter Anvin
2013-04-11 21:28   ` Kees Cook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG7+5M0ohMrCG1obmy1kaP+R1Qykcu1nn_L1c4L8RFpvrWmgcQ@mail.gmail.com \
    --to=digitaleric@google.com \
    --cc=drosenberg@vsecurity.com \
    --cc=hpa@zytor.com \
    --cc=jarkko.sakkinen@intel.com \
    --cc=jln@google.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=mjg@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=wad@chromium.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).