diem
trophy-case
diem | trophy-case | |
---|---|---|
15 | 14 | |
16,700 | 417 | |
0.0% | 0.7% | |
0.0 | 3.3 | |
13 days ago | 3 months ago | |
Rust | ||
Apache License 2.0 | Creative Commons Zero v1.0 Universal |
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.
diem
- Diem – Facebook open source Cryptocurrency written in Rust
- Zig, the Small Language
-
Fuzzcheck (a structure-aware Rust fuzzer)
I implemented this for proptest + cargo fuzz a while ago as well: https://github.com/diem/diem/blob/main/testsuite/diem-fuzzer/src/lib.rs
-
Are there any big projects written in Rust without any use of unsafe code?
I believe diem has over 250kLOC and no unsafe code
-
Crowdloans on Kusama continue. Important news!
Pontem is an experimental network for the Diem coin (previously the project had the designation LIBRA and has been under development for several years). The project site is diem.com.
- the diem coin will be built on a native Facenook Blockchain or is the hypothesis that it can be based on Algorand well founded and has a minimum of sense?
-
Async Rust: history strikes back
This is a common confusion for newcomers, as the keyword has a different (yet somewhat related) meaning depending on the context. Libra actually had a soundness bug because of confusion about this in combination with unsafe.
trophy-case
-
Rust from a security perspective, where is it vulnerable?
You could check cargo-fuzz trophy case, which is a list of issues that have been found via fuzzing.
-
capnproto-rust: out-of-bound memory access bug
I've added it to the trophy case.
-
[LWN] A pair of Rust kernel modules
That said, what's present in what quantities under what circumstances in the Rust fuzzing trophy case does a pretty good job of illustrating how effective the Rust compiler is at ruling out entire classes of bugs.
-
Looking for simple rust programs to crash
The same fuzzing techniques applied to Rust yielded a lot of bugs as well. But in Rust's case only 7 out of 340 fuzzer-discovered bugs, or 2%, were memory corruption issues. Naturally, all of the memory corruption bugs were in unsafe code.
-
Everything Is Broken: Shipping rust-minidump at Mozilla, Part 1
https://github.com/rust-fuzz/trophy-case has like 70 of my issues in it, including the nine minidump bugs
-
Fuzzcheck (a structure-aware Rust fuzzer)
If you have found any bugs with this tool, perhaps add them to the Rust fuzz trophy case?
-
Rust is more portable than C for pngquant/libimagequant
Source: https://github.com/rust-fuzz/trophy-case (over 40 of those are just from me).
-
Rust takes a major step forward as Linux's second official language
But to bring some data, check out the fuzz trophy case. It shows that failures in Rust are most often assertions/panics (equivalent to C++ exception) with memory corruption being relatively rare (it's not never—Rust isn't promising magic—but it's a significant change).
-
Shouldn't have happened: A vulnerability postmortem
You need to read the list more carefully.
• The list is not for Rust itself, but every program every written in Rust. By itself it doesn't mean much, unless you compare prevalence of issues among Rust programs to prevalence of issues among C programs. For some context, see how memory unsafety is rare compared to assertions and uncaught exceptions: https://github.com/rust-fuzz/trophy-case
• Many of the memory-unsafety issues are on the C FFI boundary, which is unsafe due to C lacking expressiveness about memory ownership of its APIs (i.e. it shows how dangerous is to program where you don't have the Rust borrow checker checking your code).
• Many bugs about missing Send/Sync or evil trait implementations are about type-system loopholes that prevented compiler from catching code that was already buggy. C doesn't have these guarantees in the first place, so lack of them is not a CVE for C, but just how C is designed.
- Safer usage of C++ in Chrome
What are some alternatives?
go-concise-encoding - Golang implementation of Concise Binary and Text Encoding
go-fuzz - Randomized testing for Go
hyperspace - Metaverse Hyperspace Chain, Hybrid PoW/PoS consensus full node with EVM compatible VM and smart tokens(FT/NFT).
BLAKE3 - the official Rust and C implementations of the BLAKE3 cryptographic hash function
cardano-serialization-lib - This is a library, written in Rust, for serialization & deserialization of data structures used in Cardano's Haskell implementation of Alonzo along with useful utility functions.
gccrs - GCC Front-End for Rust
cl-test-grid - Collaborative testing of Common Lisp libraries
bitwarden_rs - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
Demo
go - The Go programming language
abstreet - Transportation planning and traffic simulation software for creating cities friendlier to walking, biking, and public transit
mrustc - Alternative rust compiler (re-implementation)