Know the exact crate versions used to build your Rust executable. Audit binaries for known bugs or security vulnerabilities in production, at scale, with zero bookkeeping.
This works by embedding data about the dependency tree in JSON format into a dedicated linker section of the compiled executable.
The implementation has gotten to the point where it's time to get some real-world experience with it, but the data format is not yet stable. Linux, Windows and Mac OS are currently supported.
The end goal is to get Cargo itself to encode this information in binaries instead of relying on an external crate. RFC for a proper implementation in Cargo, for which this project paves the way: rust-lang/rfcs#2801
Clone this repository:
git clone https://github.com/Shnatsel/rust-audit.git
cd rust-auditCompile the tooling and a sample binary with dependency tree embedded:
cargo build --releaseRecover the dependency tree we've just embedded.
target/release/rust-audit-info target/release/hello-auditableYou can also audit the recovered dependency tree for known vulnerabilities using cargo audit:
(cd auditable-serde && cargo build --release --features "toml" --example json-to-toml)
cargo install cargo-audit
target/release/rust-audit-info target/release/hello-auditable > dependency-tree.json
target/release/examples/json-to-toml dependency-tree.json | cargo audit -f -The auditable-extract crate allows your own tools to easily consume this info.
Add the following to your Cargo.toml:
build = "build.rs"
[dependencies]
auditable = "0.1"
[build-dependencies]
auditable-build = "0.1"Create a build.rs file next to Cargo.toml with the following contents:
fn main() {
auditable_build::collect_dependency_list();
}Add the following to the beginning your main.rs (or any other file):
static COMPRESSED_DEPENDENCY_LIST: &[u8] = auditable::inject_dependency_list!();Put the following in some reachable location in the code, e.g. in fn main():
// Actually use the data to work around a bug in rustc:
// https://github.com/rust-lang/rust/issues/47384
// On nightly you can use `test::black_box` instead of `println!`
println!("{}", COMPRESSED_DEPENDENCY_LIST[0]);Now you can cargo build and the dependency data will be embedded in the final binary automatically. You can verify that the data is actually embedded using the extraction steps from the demo.
See the auditable "Hello, world!" project for an example of how it all fits together.
Not really. A "Hello World" on x86 Linux compiles into a ~1Mb file in the best case (recent Rust without jemalloc, LTO enabled). Its dependency tree even with a couple of dependencies is < 1Kb, that's under 1/1000 of the size. We also compress it with zlib to drive the size down further. Since the size of dependency tree info grows linearly with the number of dependencies, it will keep being negligible.
Embedded platforms where you cannot spare a byte should not add anything in the executable. Instead they should record the hash of every executable in a database and associate the hash with its Cargo.lock, compiler and LLVM version, build date, etc. This would make for an excellent Cargo wrapper or plugin. Since that can be done in a 5-line shell script, writing that tool is left as an exercise to the reader.
The data format is designed not to disrupt reproducible builds. It contains no timestamps, and the generated JSON is sorted to make sure it is identical between compilations. If anything, this helps with reproducible builds, since you know all the versions for a given binary now.
It is interoperable with existing tooling that consumes Cargo.lock via the JSON-to-TOML convertor. You can also write your own tooling fairly easily - auditable-extract and auditable-serde crates handle all the data extraction and parsing for you. See the docs to get started.
It is not yet stabilized, so we do not have extensive docs or a JSON schema. However, these Rust data structures map to JSON one-to-one and are extensively commented. The JSON is Zlib-compressed and placed in a linker section with a name that varies by platform.
Yes. The data format is designed for interoperability with alternative implementations. You can also use pre-existing platform-specific tools or libraries for data extraction. E.g. on Linux:
objcopy -O binary --only-section=.rust-deps-v0 target/release/hello-auditable /dev/stdout | pigz -zd -However, don't run legacy tools on untrusted files. Use the auditable-extract crate or the rust-audit-info command-line tool if possible - they are written in 100% safe Rust, so they will not have such vulnerabilities.
TL;DR: The list of enabled features is the only newly disclosed information.
All URLs and file paths are redacted, but the crate names, feature names and versions are recorded as-is. At present panic messages already disclose all this info and more, except feature names. Also, chances are that you're legally obligated have to disclose use of specific open-source crates anyway, since MIT and many other licenses require it.
It's already there. Run strings your_executable | grep 'rustc version' to see it. Don't try this on files you didn't compile yourself - strings is overdue for a rewrite in safe Rust.
In theory we could duplicate it in the JSON for ease of access, but this can be added later in a backwards-compatible fashion.
Good question. I don't think they are exposed in any reasonable way right now. Would be a great addition, but not required for the initial launch. We can add it later in a backwards-compatible way later.
- Getting some real-world experience with this before committing to a stable data format
- rust-lang/rust#47384
Help on these points would be greatly appreciated.