summaryrefslogtreecommitdiffstats
path: root/crypto/tgr192.c
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2014-08-27 05:16:35 +0200
committerTheodore Ts'o <tytso@mit.edu>2014-10-17 17:37:29 +0200
commitd4c5efdb97773f59a2b711754ca0953f24516739 (patch)
tree83ededeb92d6d529e8081b97b2f9cdf491094b78 /crypto/tgr192.c
parentLinux 3.17-rc1 (diff)
downloadlinux-d4c5efdb97773f59a2b711754ca0953f24516739.tar.xz
linux-d4c5efdb97773f59a2b711754ca0953f24516739.zip
random: add and use memzero_explicit() for clearing data
zatimend has reported that in his environment (3.16/gcc4.8.3/corei7) memset() calls which clear out sensitive data in extract_{buf,entropy, entropy_user}() in random driver are being optimized away by gcc. Add a helper memzero_explicit() (similarly as explicit_bzero() variants) that can be used in such cases where a variable with sensitive data is being cleared out in the end. Other use cases might also be in crypto code. [ I have put this into lib/string.c though, as it's always built-in and doesn't need any dependencies then. ] Fixes kernel bugzilla: 82041 Reported-by: zatimend@hotmail.co.uk Signed-off-by: Daniel Borkmann <dborkman@redhat.com> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Cc: Alexey Dobriyan <adobriyan@gmail.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: stable@vger.kernel.org
Diffstat (limited to 'crypto/tgr192.c')
0 files changed, 0 insertions, 0 deletions