From: Yann Droneaud <ydroneaud@opteya.com>
To: Solar Designer <solar@openwall.com>, riel@redhat.com
Cc: linux-kernel@vger.kernel.org, danielmicay@gmail.com,
tytso@mit.edu, keescook@chromium.org, hpa@zytor.com,
luto@amacapital.net, mingo@kernel.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
linux-sh@vger.kernel.org, ysato@users.sourceforge.jp,
kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] [PATCH v2 0/5] stackprotector: ascii armor the stack canary
Date: Wed, 20 Sep 2017 11:18:04 +0000 [thread overview]
Message-ID: <1505906284.3490.5.camel@opteya.com> (raw)
In-Reply-To: <20170919171600.GA31441@openwall.com>
Hi,
Le mardi 19 septembre 2017 à 19:16 +0200, Solar Designer a écrit :
>
> We could put/require a NUL in the middle of the canary,
> but with the full canary being only 64-bit at most that would also
> make some attacks easier.
>
Are you suggesting to randomly select which byte to set to 0 in each
canary ?
Regards.
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2017-09-20 11:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 15:57 [PATCH v2 0/5] stackprotector: ascii armor the stack canary riel
2017-05-24 15:57 ` [PATCH 1/5] random,stackprotect: introduce get_random_canary function riel
2017-05-24 16:15 ` Kees Cook
2017-05-24 15:57 ` [PATCH 2/5] fork,random: use get_random_canary to set tsk->stack_canary riel
2017-05-24 16:16 ` Kees Cook
2017-05-24 15:57 ` [PATCH 3/5] x86: ascii armor the x86_64 boot init stack canary riel
2017-05-24 16:16 ` Kees Cook
2017-05-24 15:57 ` [PATCH 4/5] arm64: ascii armor the arm64 " riel
2017-05-24 16:16 ` Kees Cook
2017-05-24 15:57 ` [PATCH 5/5] sh64: ascii armor the sh64 " riel
2017-05-24 16:34 ` Rik van Riel
2017-05-24 16:35 ` Kees Cook
2017-09-19 17:16 ` [kernel-hardening] [PATCH v2 0/5] stackprotector: ascii armor the " Solar Designer
2017-09-19 20:22 ` Kees Cook
2017-09-19 21:10 ` Daniel Micay
2017-09-20 11:18 ` Yann Droneaud [this message]
2017-09-20 15:03 ` Solar Designer
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=1505906284.3490.5.camel@opteya.com \
--to=ydroneaud@opteya.com \
--cc=catalin.marinas@arm.com \
--cc=danielmicay@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=solar@openwall.com \
--cc=tytso@mit.edu \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).