OpenDoas
rustsec
OpenDoas | rustsec | |
---|---|---|
29 | 33 | |
600 | 1,524 | |
- | 1.4% | |
0.0 | 9.5 | |
about 2 months ago | 16 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
OpenDoas
-
A simple guide for configuring sudo and doas
Aditionally,because doas was developed for OpenBSD,it also retains some of its quirks,like how user-installed executables are stored in /usr/local/bin,in contrast to /usr/bin where Linux stores them. As a result,doas can have problems on Linux so the following workaround can be used:
-
The First Stable Release of a Rust-Rewrite Sudo Implementation
https://github.com/Duncaen/OpenDoas/issues/106
That's a pretty severe unsolved security issue.
-
Doas – dedicated OpenBSD application subexecutor
2. https://github.com/Duncaen/OpenDoas/blob/master/timestamp.c
-
Testing the memory safe Rust implementation of Sudo/Su
If you want to move away from Sudo, but don't want to try this rust implementation just yet, I have had great success with OpenBSD's doas. It has been ported to every Linux distro I know of as well:
https://github.com/Duncaen/OpenDoas
-
Doas Mastery (2019)
There are, at both ends. Both the "script kiddies" who cannot deviate from scripts because they lack almost any knowledge at all; and the knowledgeable ones who know that there are subtle differences between sudo and doas which require doing things slightly differently to achieve the same effect.
* https://github.com/Duncaen/OpenDoas/issues/116#issuecomment-...
-
Help me on gentoo
Doas makes more in openbsd world In linux there are many api that need to be changed for porting, i'm no expert but the port might be flawed as not many developers has checked the codebase And how can you explain this vulnerability https://github.com/Duncaen/OpenDoas/issues/106
-
Linux users who are paranoid about security.... what's your opinion about OpenBSD?
Personally I'd prefer running Qubes OS, if only my device would have been more powerful. Currently I'm on Fedora Silverblue as I believe it provides a decent middle-ground in which I'm more secure than almost any other Linux distro while not losing any (meaningful) functionality. I do make use of doas and other technologies inspired from OpenBSD to further enhance the security.
-
Sudo and Su Being Rewritten in Rust for Memory Safety
Why not port https://github.com/Duncaen/OpenDoas to rust instead?
If the goal is security, then there is more to it than just using a memory safe language. Otherwise the result of this, possibly unwittingly, seems performative.
- Bringing Memory Safety to sudo and su
- Using doas instead of sudo on Debian 11
rustsec
-
Rust Tooling: 8 tools that will increase your productivity
cargo-audit is a simple Cargo tool for detecting vulnerable Rust crates. You can install it with cargo install cargo-audit, use cargo audit and you’re done! Any vulnerable crates will appear below, like so:
-
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.
-
Sudo and Su Being Rewritten in Rust for Memory Safety
Yeah your decade old single header libs get so many audits by comparison.
https://github.com/RustSec/rustsec/tree/main/cargo-audit
https://mozilla.github.io/cargo-vet/
cargo is not npm
-
A CVE has been issued for hyper. Denial of Service possible
PSA: before filing CVEs for other people's projects, file an issue with https://rustsec.org instead
-
Should atomics be unsafe?
Historically, such serious bugs get communicated broadly and addressed very quickly via security advisory blog posts and on https://rustsec.org.
-
Rust from a security perspective, where is it vulnerable?
For known vulnerabilities we have the rustsec vulnerability database. You could have a look over there for inspiration. There's also the related cargo-audit for checking dependencies for known vulnerabilities.
-
capnproto-rust: out-of-bound memory access bug
Would be cool if this was also reported to https://rustsec.org/ that way cargo audit could pick up and alert the users about it.
-
`cargo audit` can now scan compiled binaries
P.S. I also made scanning binaries 5x faster in the latest release of cargo audit.
-
My Rust development workflow (after 3+ years)
Thanks to cargo and the community, project maintenance is straightforward in rust. You'll need to install cargo-outdated and cargo-audit:
-
Mental models for learning Rust
Use the automated tools to assist you in the maintenance of your projects: rustfmt, clippy, cargo update, cargo outdated and cargo-audit.
What are some alternatives?
doas - A port of OpenBSD's doas which runs on FreeBSD, Linux, NetBSD, and illumos
opensnitch - OpenSnitch is a GNU/Linux interactive application firewall inspired by Little Snitch.
runas - An alternative to sudo and doas written in Rust
vulndb - [mirror] The Go Vulnerability Database
nixpkgs - Nix Packages collection & NixOS
gosec - Go security checker
bedrocklinux-userland - This tracks development for the things such as scripts and (defaults for) config files for Bedrock Linux
crates.io - The Rust package registry
tako - Run commands as another user
ripasso - A simple password manager written in Rust
koyo - Run commands as another user
advisory-db - Security advisory database for Rust crates published through crates.io