cargo-auditable
auto-fuzz-test
cargo-auditable | auto-fuzz-test | |
---|---|---|
23 | 6 | |
553 | 69 | |
3.8% | - | |
7.8 | 0.0 | |
9 days ago | over 2 years ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
cargo-auditable
-
Rust Offline?
Further we use cargo-auditable and cargo-audit as part of both our pipeline and regular scanning of all deployed services. This makes our InfoSec and Legal super happy since it means they can also monitor compliance with licenses and patch/update timings.
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
This exists, see cargo auditable.
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
The Rust community seems to have settled on a perfectly reasonable way to address bit-rot in statically linked binaries. https://github.com/rust-secure-code/cargo-auditable
-
Release Engineering Is Exhausting So Here's cargo-dist
Would you be open to integrating cargo auditable into this pipeline in some form? It seems like a great match.
-
Swift Achieved Dynamic Linking Where Rust Couldn't
> and static compilation probably just hides the problem unless security scanners these days can identify statically compiled vulnerable versions of libraries
Some scanners like trivy [1] can scan statically compiled binaries, provided they include dependency version information (I think go does this on its own, for rust there's [2], not sure about other languages).
It also looks into your containers.
The problem is what to do when it finds a vulnerability. In a fat app with dynamic linking you could exchange the offending library, check that this doesn't break anything for your use case, and be on your way. But with static linking you need to compile a new version, or get whoever can build it to compile a new version. Which seems to be a major drawback of discouraging fat apps.
1: https://github.com/aquasecurity/trivy
2: https://github.com/rust-secure-code/cargo-auditable
-
'cargo auditable' can now be used as a drop-in replacement for Cargo
I have investigated a bunch of standardized formats - SPDX, CycloneDX, etc. All of them are unsuitable for a variety of reasons, chief of which are being way too verbose and including timestamps, which would break reproducible builds.
-
sccache now supports GHA as backend
The fix for interoperability with cargo auditable has also shipped in the latest release of sccache. You can use the released sccache now instead of building it from git!
-
`cargo audit` can now scan compiled binaries
I've been working to bring vulnerability scanning to Rust binaries by creating cargo auditable, which embeds the list of dependencies and their versions into the compiled binary. This lets you audit the binary you actually run, instead of the Cargo.lock file in some repo somewhere.
-
Here's how to patch the upcoming OpenSSL vulnerability in Rust
cargo auditable solves this problem by embedding the list of dependencies and their versions into the binaries. But until it becomes part of Cargo and gets enabled by default, static linking will remain problematic.
- Introducing cargo-auditable: audit Rust binaries for known bugs or vulnerabilities in production
auto-fuzz-test
-
We Don't Need a Stable ABI
Can confirm, https://github.com/rust-fuzz/auto-fuzz-test was hard write to write (and still isn't production ready) precisely because the compiler doesn't expose type information.
-
Win32 API fuzzer, to help develop Wine
This is super interesting! I've tried auto-generating fuzzing harnesses for arbitrary Rust functions as well: https://github.com/rust-fuzz/auto-fuzz-test
-
The `arbitrary` crate is approaching 1.0!
We've been leaning on this crate heavily in https://github.com/rust-fuzz/auto-fuzz-test, and it's really nice to see support for borrowed types materialize!
-
New:`cargo-fuzzcheck` 0.5.0 and a series of decent, fast-to-compile crates to replace `syn`, `quote`, `serde-json`, and `toml-rs`
Interesting! We'll need to try it with https://github.com/rust-fuzz/auto-fuzz-test, since we're getting mysterious segfaults from our cargo-fuzz/libfuzzer backend right now.
-
Unsafe Rust: How and when (not) to use it - LogRocket Blog
Specifically, I tried leading a fuzzing effort via https://github.com/rust-fuzz/auto-fuzz-test, but right now it's not quite production-ready. We have good progress in proc_macro branch, but that's geared towards crates, and it's not entirely clear how to apply that to the standard library.
-
Does any interesting projects need help?
https://github.com/rust-fuzz/auto-fuzz-test if you want something a bit more involved but with a huge potential
What are some alternatives?
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
pico-args - An ultra simple CLI arguments parser.
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
rust - Empowering everyone to build reliable and efficient software.
eve-rs - A simple, intuitive, express-like HTTP library
Win32Fuzzer - Winapi fuzzer to help Wine project in creating better Windows "emulator"
svntogit-community - Automatic import of svn 'community' repo (read-only mirror)
json - Strongly typed JSON library for Rust
sandbox - A sand simulation game
SummerOfCode2021 - GSoC 2021 Idea List for Casbin
Qarminer - Qarminer is fuzzer which automatically test Godot and its modules