miniserde
trophy-case
miniserde | trophy-case | |
---|---|---|
4 | 14 | |
726 | 394 | |
- | 1.0% | |
7.7 | 2.8 | |
17 days ago | 28 days 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.
miniserde
-
Hey Rustaceans! Got a question? Ask here (8/2023)!
It's pretty common to avoid macros as they can seem too magical a lot of the time. And with traits, there's experiments like miniserde which specifically avoid monomorphization overhead. I also see people who want to avoid having lots of dependencies relatively often.
-
venial 0.1 - A lightweight alternative to syn
Right now, the next step would be to try to reimplement miniserde with venial, and publish benchmarks.
- Rust takes a major step forward as Linux's second official language
-
The Serde Rust Framework
The only downside is compile time bloat.
Serde generates heaps and heaps of generic code. This gets optimized away to be very efficient, but it can be quite cumbersome.
Ever tried working on a crate with hundreds or thousands of de/serializable types? Compile times shoot through the roof really quickly.
The maintainer of serde also created `miniserde` [1], which uses dynamic dispatch and can have 4x compile time improvements.
Due to Rusts lack of orphan instances you really depend on a pervasive standard for serializiation which is used by all libraries, so the ecosystem is really locked in to serde by now.
[1] https://github.com/dtolnay/miniserde
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?
nanoserde - Serialisation library with zero dependencies
diem - Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.
ComLightInterop - Cross-platform COM interop library for .NET Core 2.1 or newer
go-fuzz - Randomized testing for Go
serde_v8 - Moved to https://github.com/denoland/deno
gccrs - GCC Front-End for Rust
pfr - std::tuple like methods for user defined types without any macro or boilerplate code
BLAKE3 - the official Rust and C implementations of the BLAKE3 cryptographic hash function
serde - Serialization framework for Rust
bitwarden_rs - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
sapio - A Bitcoin Programming Language
go - The Go programming language