News for hackers. Stuff that matters.
Re:An Empirical Study of Vulnerabilities in Cryptographic Li... by chrisseaton on Sunday July 25, 2021 @08:42AM (#27948757)
What tools do you use for verification? We don’t have many verified compilers yet so even if you verify the code how do you verify it’s compiled correctly?
Re:An Empirical Study of Vulnerabilities in Cryptographic Li... by lucb1e on Sunday July 25, 2021 @08:54AM (#27948821)
For all I know I've got 5G implanted, how am I to verify that? Obviously the implant will make whatever measurements I do return the wrong results.

Gotta trust something, we decided we mainly trust the OS download and the repository keys that came with it.

Anyway we seem to have been talking about different kinds of verification, like checking that what Joan Daemen and Vincent Rijmen wrote is really what your CPU is executing versus verifying that implementations of a trusted algorithm aren't broken. We're not in the conspiracy theory or incident response business, so unless someone comes with something that sounds like we should forward them to incident response, the former is not what we do.

Re:An Empirical Study of Vulnerabilities in Cryptographic Li... by chrisseaton on Sunday July 25, 2021 @09:03AM (#27948871)
Formal verification is a thing people do - and I think that’s what most people think from ‘verified’. They aren’t conspiracy theorists they’re proving things like that your C implementation code is defined and matches what you think you’ve written, since that’s where these errors creep in.
Re:An Empirical Study of Vulnerabilities in Cryptographic Li... by rocqua on Sunday July 25, 2021 @10:20AM (#27949354)
you can do those things under the assumption "the compiler is correct". That still very much counts as formal verification.