cargo-xwin
cargo-auditable
cargo-xwin | cargo-auditable | |
---|---|---|
6 | 23 | |
286 | 553 | |
7.3% | 3.8% | |
8.0 | 7.8 | |
13 days ago | 6 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | 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-xwin
-
[Review] Introducing cargo-xwin: A Solution for Cross-Compiling Rust on macOS to MSVC
Today, I am excited to introduce a real game-changer - the [cargo-xwin](https://github.com/rust-cross/cargo-xwin) crate! After countless trials and errors, cargo-xwin was the only one that truly met my needs.
-
Release Engineering Is Exhausting So Here's cargo-dist
I couldn't tell you the licensing implications but the cargo-zigbuild developer also made cargo-xwin: https://github.com/rust-cross/cargo-xwin
-
Crosscompiling from fedora to Windows
I thought you could already cross compile to -windows-msvc targets from Linux using cargo-xwin?
-
Cross-compilation in Rust
I've personally used cargo-zigbuild and cargo-xwin to distribute a GUI app built with iced.
-
cargo-xwinbuild v0.3.0 supports cross compile to Windows with CMake dependency
cargo-xwinbuild is a thin wrapper of xwin provides a Cargo subcommand xwinbuild to make cross compiling to Windows MSVC target just work.
-
Announcing cargo-xwinbuild: Cross compile Cargo project to Windows msvc target with ease
So I thought I can try to make another Cargo subcommand which integrates xwin and automates the boring stuffs for you, here comes cargo-xwinbuild: https://github.com/messense/cargo-xwinbuild
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?
cargo-dist - 📦 shippable application packaging
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
auto-fuzz-test - Effortlessly fuzz libraries with large API surfaces
xwin - A utility for downloading and packaging the Microsoft CRT headers and libraries, and Windows SDK headers and libraries needed for compiling and linking programs targeting Windows.
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
cargo-zigbuild - Compile Cargo project with zig as linker
eve-rs - A simple, intuitive, express-like HTTP library
darling - Darwin/macOS emulation layer for Linux
svntogit-community - Automatic import of svn 'community' repo (read-only mirror)
sandbox - A sand simulation game
SummerOfCode2021 - GSoC 2021 Idea List for Casbin