cc-rs
cargo-auditable
cc-rs | cargo-auditable | |
---|---|---|
8 | 23 | |
1,731 | 553 | |
0.2% | 3.8% | |
9.0 | 7.8 | |
10 days ago | 5 days 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.
cc-rs
-
RustPython – A Python-3 (CPython >= 3.11.0) Interpreter written in Rust
It does support calling into other compilers and toolchains through build scripts and such. Take cc-rs[0] for example: this allows building C and C++ files natively without even calling an executable yourself.
In practice, I'd expect libraries to just call make/cmake/ninja for you, or (like openssl-sys) ask you to install the necessary libraries using your favourite package manager.
[0]: https://github.com/rust-lang/cc-rs
-
Any crates for compiling C ( or other language ) from a rust binary?
The cc crate (https://github.com/rust-lang/cc-rs) is widely used for compiling C code from Rust (often in a build.rs file for the purpose of wrapping a C library so that it can be used from Rust). However, I believe it generally does expect a C compiler to be present.
-
Calling C code from Rust
It might be quite tedious to compile static library manually every time we make changes in C code. The better solution is to instead utilize the cc crate, which provides an idiomatic Rust interface to the compiler provided by the host.
- cc-rs is looking for new maintainers
-
Hello, youki! Faster container runtime is written in Rust
https://github.com/alexcrichton/cc-rs This crates lets you shell out to a C compiler when building your Rust project
-
Maintain It with Zig
> You're splitting hairs in a weird way. rustc cannot compile C code. zig can.
But why do I care? I don't use rustc directly, the build system of choice does. And very few of the major build systems have an issue handling multiple languages.
Cargo (rust's build system) supports build scripts and the community has already created C/C++ compiler hooks such as https://github.com/alexcrichton/cc-rs
rustup and cargo also provide easy cross-compilation support, too.
-
Windows can't find link exe
I think it's getting confused because link.exe is in your PATH. But it's not the link.exe it expects. Link tools are detected using the cc crate so it would need to be fixed there. Would you be willing to open an issue about this?
-
Most loved programming language Rust sparks privacy concerns
It’s not super well-documented, but there is an option to change this. --remap-path-prefix $(pwd)= in your RUSTFLAGS will usually do the trick. If you have any C dependencies you’ll also need similar things in CFLAGS, see https://github.com/alexcrichton/cc-rs/issues/593
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
What are some alternatives?
RIIR - why not Rewrite It In Rust
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
mach - zig game engine & graphics toolkit
auto-fuzz-test - Effortlessly fuzz libraries with large API surfaces
arocc - A C compiler written in Zig.
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
ohmygentool - LLVM/Clang based bindings generator for D language
eve-rs - A simple, intuitive, express-like HTTP library
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
svntogit-community - Automatic import of svn 'community' repo (read-only mirror)
utfcpp - UTF-8 with C++ in a Portable Way
sandbox - A sand simulation game