lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 3 Sep 2021 09:13:43 +0800
From:   Sandy Harris <sandyinchina@...il.com>
To:     Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
        linux-hardening@...r.kernel.org
Subject: memset() in crypto code

Doing this the crypto directory:
grep memset *.c | wc -l
I get 137 results.

The compiler may optimise memset() away, subverting the intent of
these operations. We have memzero_explicit() to avoid that problem.

Should most or all those memset() calls be replaced?

Powered by blists - more mailing lists