Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] checking Monocypher
- Subject: [Frama-c-discuss] checking Monocypher
- From: rod at proteancode.com (Roderick Chapman)
- Date: Thu, 30 Apr 2020 12:17:05 +0100
- In-reply-to: <78e60fea435b87e9c08199d36b78f2aa@disroot.org>
- References: <bb759614-31c3-0ec0-5de9-9da763cf42e9@cea.fr> <e63c109dad96e6491a13600f4eddf717@disroot.org> <CA+yPOVibHp68er_=rvDD+8-Ap1ydpJjVEwLAB_q4oKRuzj1B1Q@mail.gmail.com> <78e60fea435b87e9c08199d36b78f2aa@disroot.org>
If you're interested in Monocypher, then you might also take a look at SPARKNaCl.  https://github.com/rod-chapman/SPARKNaCl In short - this is TweetNaCl, re-written in SPARK and with an automatic "auto-active" proof of type safety and some other interesting properties. A more detailed blog entry also here:  https://blog.adacore.com/proving-constant-time-crypto-code-in-sparknacl  - Rod Chapman
- References:
- [Frama-c-discuss] checking Monocypher
- From: julien.signoles at cea.fr (Julien Signoles)
- [Frama-c-discuss] checking Monocypher
- From: tankf33der at disroot.org (Mike)
- [Frama-c-discuss] checking Monocypher
- From: virgile.prevosto at m4x.org (Virgile Prevosto)
- [Frama-c-discuss] checking Monocypher
- From: tankf33der at disroot.org (Mike)
- [Frama-c-discuss] checking Monocypher
- Prev by Date: [Frama-c-discuss] checking Monocypher
- Next by Date: [Frama-c-discuss] Issues with analyzing the nginx webserver using the eva plugin
- Previous by thread: [Frama-c-discuss] checking Monocypher
- Next by thread: [Frama-c-discuss] checking Monocypher
- Index(es):