orion
cargo-auditable
orion | cargo-auditable | |
---|---|---|
5 | 23 | |
236 | 553 | |
- | 2.7% | |
6.6 | 7.8 | |
about 3 years ago | 4 days ago | |
Rust | Rust | |
MIT License | 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.
orion
-
orion 0.16 - const generics, organization changes and a new maintainer
GitHub: https://github.com/orion-rs/orion Crates.io: https://crates.io/crates/orion
-
Looking for an open-source project to join part-time
I'm the author and maintainer of a pure-Rust crypto library called Orion. I've been at it for a couple of years now, working on it in my spare time as well. There are a few people involved already, but we're still missing someone that is involved enough to be a "co-maintainer". There are some larger features that have been planned, but I lack the time currently to start too many new things. Of course, you can contribute in any amount you want.
-
Look-up tables for bcrypt, scrypt and Argon2?
Custom (the ones I have in the implementation I wrote)
-
How to implement a simple password-based encryption with ring?
With that said, i think multiple people are working on crypto libraries that take footguns out of it - which is what i think we definitely need. https://github.com/brycx/orion seems like a solid attempt at making crypto fool-proof , so i do have hope.
-
Does any interesting projects need help?
You're more than welcome to swing by at Orion (a pure-Rust crypto lib). You can also check the new Matrix room for a small chat.
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?
ring - Safe, fast, small crypto using Rust
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
rust-djangohashers - A Rust port of the password primitives used in Django Project.
auto-fuzz-test - Effortlessly fuzz libraries with large API surfaces
rust-crypto - A (mostly) pure-Rust implementation of various cryptographic algorithms.
cargo-supply-chain - Gather author, contributor and publisher data on crates in your dependency graph.
RustCrypto - Authenticated Encryption with Associated Data Algorithms: high-level encryption ciphers
eve-rs - A simple, intuitive, express-like HTTP library
octavo - Highly modular & configurable hash & crypto library
svntogit-community - Automatic import of svn 'community' repo (read-only mirror)
suruga - [INACTIVE] TLS 1.2 implementation in Rust
sandbox - A sand simulation game