From: Arjan van de Ven <arjan@linux.intel.com>
To: Daniel Micay <danielmicay@gmail.com>,
Kees Cook <keescook@chromium.org>, Ingo Molnar <mingo@elte.hu>,
kernel-hardening@lists.openwall.com,
LKML <linux-kernel@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] use get_random_long for the per-task stack canary
Date: Thu, 4 May 2017 06:33:15 -0700 [thread overview]
Message-ID: <e358b217-7bae-07bb-4245-12d62513c733@linux.intel.com> (raw)
In-Reply-To: <20170504133209.3053-1-danielmicay@gmail.com>
On 5/4/2017 6:32 AM, 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.
that makes sense to me... ack
next prev parent reply other threads:[~2017-05-04 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 13:32 [PATCH] use get_random_long for the per-task stack canary Daniel Micay
2017-05-04 13:33 ` Arjan van de Ven [this message]
2017-05-04 14:04 ` [kernel-hardening] " Rik van Riel
2017-05-04 14:29 ` 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=e358b217-7bae-07bb-4245-12d62513c733@linux.intel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox