News for hackers. Stuff that matters.
Re:Report on the technical vulnerabilities found in Huawei 5... by rurban on Saturday July 13, 2019 @04:00AM (#20427044)
Not arguing with your useless junk attitude. Useless junk is the glibc and its FORTIFY_SOURCE "maybe we catch it or maybe not" attempt.

But sodium_memzero() is not safer than memset_s. If only provides a compiler barrier, but no memory barrier. AFAIK only my safeclib memset_s is "safe", but I don't provide a clflush there. Maybe I should.

Re:Report on the technical vulnerabilities found in Huawei 5... by zrm on Saturday July 13, 2019 @03:48PM (#20429797)
All the more reason there should be a function in the C standard that does it properly and uniformly across platforms.