linkme
fuzzcheck-rs
linkme | fuzzcheck-rs | |
---|---|---|
5 | 8 | |
222 | 421 | |
- | - | |
7.2 | 5.5 | |
over 2 years ago | 6 months ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | MIT License |
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.
linkme
-
Is there comptime reflection in Rust proc-macro?
You can make the code generated by your macro add to a distributed slice from the linkme crate and you can use values from that slice at compile time.
-
Match against function/symbol names
there was linkme which i think can be used for what you describe. from your perspective you get a slice and can put functions in it at link time with an attribute macro.
-
dtolnay/inventory got archived, is there an alternative ?
@dtolnay I noticed you just archived the repos for inventory, linkme, gflags, and typetag, which I assume implies a deprecation.
-
Is it possible to scan all structs/functions that have a specific #[macro] ?
An alternative to inventory which I find better for a lot of purposes: https://github.com/dtolnay/linkme
-
What's your favourite under-rated Rust crate and why?
I like dtolnay's inventory or linkme crates to register items in a central list, just using decentralized annotations.
fuzzcheck-rs
-
Fuzzcheck (a structure-aware Rust fuzzer)
Fuzzcheck is a structure-aware fuzzer for rust. "Fuzzing" means feeding large amounts of data into a program and checking for crashes (Fuzzcheck also checks to make sure that all the properties your program should uphold – e.g. a sorting algorithm applied to a list of n items should always return a list of n items – are upheld). Fuzzcheck is an "evolutionary" fuzzer – this means that it generates a set of random inputs, sees what percentage of the program is executed for each input, and keeps inputs which have high levels of percentage of program executed. It then "mutates" these inputs – whereas fuzzers such as AFL/Hongfuzz/etc mutate raw bytes in place (e.g. they swap bytes at different positions, or insert a random byte at a given position to generate inputs similar to the chosen "high coverage" inputs), Fuzzcheck works directly on the Rust types (so it might swap the order of two items in a vec, or randomly insert a new item). It's a really powerful tool for finding lots of bugs.
-
fuzzcheck 0.9 release - run coverage-guided fuzz tests alongside your regular unit tests + code coverage visualiser + new online guide and improved documentation
If you want help with Win support (issues/8) maybe post it here to get it added to TWIR.
-
What's everyone working on this week (43/2021)?
I am working on a code coverage viewer for my fuzzer (fuzzcheck). I described what I've done so far in this issue and I am hoping to release the first version within two weeks.
-
What's everyone working on this week (31/2021)?
The implications for my fuzzer, fuzzcheck, are huge! Compiling fuzz tests is a lot easier. There should be no more need to create a separate fuzz folder, fuzz tests can be regular #[test] functions, private implementation details can be fuzz-tested as well, rust-analyser works as expected, documentation can be easily generated, etc. I can also attach a human-readable coverage report to every test case :)
-
What's everyone working on this week (30/2021)?
Since I graduated, I have had a lot more time to work on fuzzcheck. I am trying to flesh it out, test it, and document it for a new release. It has always felt a bit rushed/experimental and now I am hoping to make it into something solid. I have also played with an egui interface for it, to visualise the tested code coverage, understand how the fuzzer’s decisions are made, and also to interactively tweak the fuzzer’s behaviour. It's a lot of work but it's slowly all coming together! :)
-
What's your favourite under-rated Rust crate and why?
fuzzcheck-rs is really cool. It combines property-testing with fuzzing, getting the nice, structured nature of the former, and the coverage-driven search of the latter, but it works by mutating the structure directly instead of going through a bit string. So if you have a binary tree, going from A(B, C) to A(C, B) can be a single mutation away if that makes sense in your use case, instead of being arbitrarily far away in the bitstring approach.
- Fuzzcheck: Structure and coverage guided fuzzing for Rust
What are some alternatives?
inventory - Typed distributed plugin registration
openapi-fuzzer - Black-box fuzzer that fuzzes APIs based on OpenAPI specification. Find bugs for free!
rust-djangohashers - A Rust port of the password primitives used in Django Project.
rs_pbrt - Rust crate to implement a counterpart to the PBRT book's (3rd edition) C++ code. See also https://www.rs-pbrt.org/about ...
schemafy - Crate for generating rust types from a json schema
phpass - PHPass, the WordPress password hasher, re-implemented in rust
redbpf - Rust library for building and running BPF/eBPF modules
structopt - Parse command line arguments by defining a struct.
parse-size - Parse byte size into integer accurately.
enum-map
yayagram - Play nonograms/picross in your terminal
uivonim - Fork of the Veonim Neovim GUI