[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1505906284.3490.5.camel@opteya.com>
Date: Wed, 20 Sep 2017 13:18:04 +0200
From: Yann Droneaud <ydroneaud@...eya.com>
To: Solar Designer <solar@...nwall.com>, riel@...hat.com
Cc: linux-kernel@...r.kernel.org, danielmicay@...il.com, tytso@....edu,
keescook@...omium.org, hpa@...or.com, luto@...capital.net,
mingo@...nel.org, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org, catalin.marinas@....com,
linux-sh@...r.kernel.org, ysato@...rs.sourceforge.jp,
kernel-hardening@...ts.openwall.com
Subject: Re: [kernel-hardening] [PATCH v2 0/5] stackprotector: ascii armor
the stack canary
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
Powered by blists - more mailing lists