From: Rik van Riel <riel@redhat.com>
To: Daniel Micay <danielmicay@gmail.com>,
Kees Cook <keescook@chromium.org>,
Arjan van Ven <arjan@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
kernel-hardening@lists.openwall.com,
LKML <linux-kernel@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [kernel-hardening] [PATCH] use get_random_long for the per-task stack canary
Date: Thu, 04 May 2017 10:04:59 -0400 [thread overview]
Message-ID: <1493906699.29205.1.camel@redhat.com> (raw)
In-Reply-To: <20170504133209.3053-1-danielmicay@gmail.com>
On Thu, 2017-05-04 at 09:32 -0400, Daniel Micay wrote:
> The stack canary is an unsigned long and should be fully initialized
> to
> random data rather than only 32 bits of random data.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Daniel Micay <danielmicay@gmail.com>
>
Acked-by: Rik van Riel <riel@redhat.com>
next prev parent reply other threads:[~2017-05-04 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 13:32 [kernel-hardening] [PATCH] use get_random_long for the per-task stack canary Daniel Micay
2017-05-04 13:32 ` Daniel Micay
2017-05-04 13:33 ` [kernel-hardening] " Arjan van de Ven
2017-05-04 13:33 ` Arjan van de Ven
2017-05-04 14:04 ` Rik van Riel [this message]
2017-05-04 14:29 ` [kernel-hardening] " Kees Cook
2017-05-05 8:10 ` [tip:core/urgent] stackprotector: Increase the per-task stack canary's random range from 32 bits to 64 bits on 64-bit platforms tip-bot for Daniel Micay
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=1493906699.29205.1.camel@redhat.com \
--to=riel@redhat.com \
--cc=arjan@linux.intel.com \
--cc=danielmicay@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.