[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168564402237.2891605.1600418987887898293.b4-ty@chromium.org>
Date: Thu, 1 Jun 2023 11:27:03 -0700
From: Kees Cook <keescook@...omium.org>
To: keescook@...omium.org, paul.walmsley@...ive.com
Cc: ndesaulniers@...gle.com, linux-kernel@...r.kernel.org,
gustavoars@...nel.org, linux@...mhuis.info,
heiko.stuebner@...ll.eu, linux-hardening@...r.kernel.org,
aou@...s.berkeley.edu, linux-riscv@...ts.infradead.org,
joanbrugueram@...il.com, masahiroy@...nel.org,
conor.dooley@...rochip.com, ajones@...tanamicro.com, hi@...ssa.is,
palmer@...belt.com
Subject: Re: [PATCH v2] riscv/purgatory: Do not use fortified string functions
On Thu, 1 Jun 2023 09:00:28 -0700, Kees Cook wrote:
> With the addition of -fstrict-flex-arrays=3, struct sha256_state's
> trailing array is no longer ignored by CONFIG_FORTIFY_SOURCE:
>
> struct sha256_state {
> u32 state[SHA256_DIGEST_SIZE / 4];
> u64 count;
> u8 buf[SHA256_BLOCK_SIZE];
> };
>
> [...]
Applied to for-next/hardening, thanks!
[1/1] riscv/purgatory: Do not use fortified string functions
https://git.kernel.org/kees/c/ca2ca08f479d
--
Kees Cook
Powered by blists - more mailing lists