5 ms·
I remember reading (~10 years ago) that F* was created as part of a "Project Everest" a long time back, with the goal of creating a provable TLS implementation.
by daxfohl 2y ago
I remember reading (~10 years ago) that F* was created as part of a "Project Everest" a long time back, with the goal of creating a provable TLS implementation. I never saw that anything came out of that though. If it's that hard to create something as well-defined as a TLS implementation, it seems futile to think this could ever be used for hand-wavy things we encounter in day-to-day work, no? Or are there real-world use cases where this could really be applied?
- octachron 2y agoThe Everest project did publish a proved TLS implementation: https://mitls.org https://mitls.org. And at least the EverCrypt* cryptographic primitives has been used outside of academia.
- lambdanik 2y agoF* existed before Project Everest, but Everest did power a lot of its development. We have built verified systems and components in the TLS ecosystem, including parts of TLS, QUIC and related protocols, and continue to do so: https://project-everest.github.io/ https://project-everest.github.io/ Some of it is deployed in production systems: * Verified parsers in the Windows kernel and elsewhere: https://www.microsoft.com/en-us/research/blog/everparse-hardening-critical-attack-surfaces-with-formally-proven-message-parsers/ https://www.microsoft.com/en-us/research/blog/everparse-hard... * Verified crypto in Linux, Firefox, Python, ... https://github.com/hacl-star/hacl-star https://github.com/hacl-star/hacl-star
- daxfohl 2y agoSo _would_ it possibly be useful for business apps? Or is that still a long way off?