News for hackers. Stuff that matters.
Re:Memory Safe Languages in Android 13 by raggi on Thursday December 01, 2022 @10:25PM (#33826375)
WireGuard is a recent and prominent example of a system that has been formally verified (https://www.wireguard.com/formal-verification/). There are implementations in a variety of languages due to integration considerations.

You will find at the bottom of that page C implementations of curve25519 that are proofed and derived from F* and Coq. Curve25519 is a relatively simple implementation and only one part of any system that uses it. As you can see in both of these implementations the papers recognize a team of contributors each - this should provide some insight as to the cost of such work. That doesn't make it unimportant, it just makes it rare.

Re:Memory Safe Languages in Android 13 by ShredKazoo on Thursday December 01, 2022 @10:39PM (#33826470)
Out of curiosity did the Wireguard formal verification effort end up identifying any security issues in the implementation?
Re:Memory Safe Languages in Android 13 by harry8 on Thursday December 01, 2022 @11:50PM (#33826932)
Now that is interesting. I didn't know that and will have to look further to understand what it means.

Wireguard seems to be written almost entirely in C, is that right?

Re:Memory Safe Languages in Android 13 by KMag on Friday December 02, 2022 @02:34AM (#33827876)
The symbolic proofs of the protocol are independent of the implementation. The portions of the implementation that are formally verified are written in F* and Coq, and emitted as machine-generated C.