phc-discussions - RE: [PHC] RE: [FORGED] [PHC] Argon2 using memset still

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4AEC424@uxcn10-5.UoA.auckland.ac.nz>
Date: Mon, 31 Aug 2015 13:08:24 +0000
From: Peter Gutmann <pgut001@...auckland.ac.nz>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: RE: [PHC] RE: [FORGED] [PHC] Argon2 using memset still

Dmitry Khovratovich <khovratovich@...il.com> writes:

>as Samuel Neves pointed out, it seems there are few compilers (if any) that
>support memset_s

Sure, but hopefully that'll change over time, and the __STDC_LIB_EXT1__ will
mean it's enabled as soon as support appears.

>Visual Studio 2013 does not know about it, for example.

VS has had SecureZeroMemory() since VS 2005, so it doesn't really need it.
clang and gcc have partial C11 support now, so hopefully it'll appear
eventually.

Peter.