fiat-crypto
RFCs
fiat-crypto | RFCs | |
---|---|---|
10 | 33 | |
689 | 134 | |
1.0% | 0.7% | |
9.5 | 4.2 | |
9 days ago | 11 months ago | |
Coq | ||
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fiat-crypto
- Dilemma: very unhappy with a highly-paying tech job. What to do?
-
Go 1.20 Cryptography
> Both your comment here and some stuff FiloSottile implied in the comment above seem like they would be (largely) mitigated by what the "Go 1.20 Cryptography" post mentions about using formally verified primitives that are generated by "fiat-crypto".
> Beyond the curve primitive, wouldn't the majority of the code involved be shared/identical? These are closely related curves, not some oddball algorithm that requires a bespoke implementation.
Well, fiat-crypto only provides the curve implementations.
Each language, library, etc. that wants to support ed448 will need a SHAKE256 implementation too. That has historically not been a safe addition, in practice.
Also, I don't see Ed448 on here (but I do see P448?): https://github.com/mit-plv/fiat-crypto/tree/6e6809be8290a7d7...
- Program Synthesis is Possible (2018)
- fiat-crypto: Cryptographic Primitive Code Generation by Fiat
-
The technological case against Bitcoin and blockchain
I think this is a more interesting URL: https://github.com/mit-plv/fiat-crypto/issues/902
-
Orion 0.17 – X25519 with formally-verified field arithemtic and serde support
Hi, maintainer of the crate
The formal verification comes from [fiat-crypto](https://github.com/mit-plv/fiat-crypto), which generates the Rust code of the underlying Curve25519 field arithmetic. Correctness is checked by Coq.
Mention of fiat-crypto was included in the original posts on Reddit/Lobste.rs but seems it was missed in this cross-post.
-
Orion 0.17 - X25519 with formally-verified field arithemtic and serde support
Orion now supports X25519 (Diffie-Hellman over Curve25519), which uses formally-verified field arithmetic generated by fiat-crypto. Additionally, a lot of focus was put into hardening the CI/CD of the crate along with added support for serde. This work was championed by /u/vlmutolo.
-
"Serious" vulnerability found in Libgcrypt, GnuPG's cryptographic library - Help Net Security
I have great hopes for formal verification: - https://www.usenix.org/conference/usenixsecurity17/technical-sessions/presentation/bond - https://github.com/project-everest/hacl-star - https://github.com/mit-plv/fiat-crypto - https://saw.galois.com/
-
Synthesizing Correct-by-Construction Code for Cryptographic Primitives
A list of projects using the code generated by fiat-crypto: https://github.com/mit-plv/fiat-crypto/issues/902
RFCs
- Nim Sum types, 2024 variant
- Nim Roadmap 2024 and Beyond
- Nim v2.0 Released
-
Contribute to the Python-like Nim language
compiler support for object construction shorthand
-
Nim 2.0.0 RC2
Well, maybe not writing. Occasionally low-level C libraries - especially those that deal with keyboard input - decide to provide identifiers differing only in case... There's a WIP RFC for providing a way to deal with identifiers that need to be verbatium by surrounding them with backticks, though.
https://github.com/nim-lang/RFCs/issues/477
- please comment on "It totally sounds like the n-word" as well
- Nim goto intermediate representation (NGIR)
-
My Nim Development Weekly Report (3/12)
Following The Roadmap 2023 for community building , you could join us in the matrix space where we discuss how to build a community. We appreciate doable suggestions and helps, such as improving the workflow, implementing the roadmap, suggesting doable tasks, reviewing code from contributors. United we stand. We shall work together to make the community thrive.
- Nim Roadmap 2023
-
My Nim Development Weekly Report (2/19)
First of all, the Nim development follows The Roadmap 2023, which specifies what features might be implemented or removed in 2023. As we can see, completing incremental compilation and recursive module dependencies might be the most important tasks to be done in 2023. You might subscribe to the roadmap and write down your expectations of Nim in 2023 there.
What are some alternatives?
differential-dataflow - An implementation of differential dataflow using timely dataflow on Rust.
nimskull - An in development statically typed systems programming language; with sustainability at its core. We, the community of users, maintain it.