sudo
totally-safe-transmute | sudo | |
---|---|---|
17 | 48 | |
245 | 1,112 | |
- | 3.5% | |
0.0 | 9.5 | |
over 1 year ago | 3 days ago | |
Rust | C | |
- | 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.
totally-safe-transmute
-
Sudo Replacement
For example, there is this (pure safe Rust) code: https://github.com/ben0x539/totally-safe-transmute/blob/main... which accesses external resources (/proc/self/mem) in order to violate the safety guarantees.
-
A rust crate that lets you compress ASCII text to a single Unicode "character"
The first is the totally_safe_transmute crate. I mean, who wouldn't love library code that has .expect("welp") and .expect("oof") as its error handling? But that's not even the really scary part. Issue #2 ("i hate this") remains open to this day, but for obvious reasons there's no chance of resolution. This post has some context and a line-by-line explanation of how it works.
-
What do you expect from Rust in 2023?
You mean like this?
-
In C# you can transmute without `unsafe`
You can also do that in rust on linux: https://github.com/ben0x539/totally-safe-transmute/blob/master/src/lib.rs
-
Why choose Rust
I want to correct this statement: Rust can be safer, but not if a library you use contains unsound code. Unsoundness is most often caused by unsafe code, but not always (totally_safe_transmute, anyone?). There is a misconception that unsafe code blocks are always unsound and should be avoided at all costs, but they're completely fine if the safety contracts are upheld. In fact, unsafe blocks isolate the potential issues to make it easier to identify where undefined behavior may be occurring. unsafe code blocks are a feature of the language, and their usage should not be viewed as opting out of any safety the language provides, imo.
-
"# NONONONONONO DON'T YOU FUCKIN' DARE the safety features are there so that your programs aren't filled to the brim with security vulnerabilities. Unless you care A LOT(And I mean A LOT A LOT) about compile times, never use `unsafe`."
Just reimplement totally_safe_transmute in Zig. No need for unsafe.
-
I mean, it solves most library conflicts
Why transmute() when you can totally_safe_transmute()?
- Safe Transmute
-
Static Analyzer Rudra Found over 200 Memory Safety Issues in Rust Crates
Well, there is always the totally-safe-transmute.
-
// SAFETY: NO
They should use https://github.com/ben0x539/totally-safe-transmute
sudo
-
Run0 – systemd based alternative to sudo announced
It depends on whether sudo was compiled with --disable-env-reset or not, it's on by default[1].
Also some variables are inherited regardless (e.g. DISPLAY, TERM), and some useful ones (e.g. HOME) are initialized by sudo, but I can't tell where that's done.
[1]: https://github.com/sudo-project/sudo/blob/ef52db46f9b375d7ff...
- Sudo Contributors
-
Sudo for Windows
Side note that I've always found interesting: sudo is almost entirely maintained by one dude: https://github.com/sudo-project/sudo/graphs/contributors
-
Rowhammer Resistant Coding in Sudo
The n=2 case also occurs in the commit: https://github.com/sudo-project/sudo/commit/7873f8334c8d3103...
And indeed, the two values ate bitwise complements.
-
The First Stable Release of a Rust-Rewrite Sudo Implementation
One feature they didn't mention they left out was the ability to run `make me a sandwich` (https://github.com/sudo-project/sudo/blob/main/Makefile.in#L...)
-
to Linus Torvalds, maybe?
It's (kind of) back - https://github.com/sudo-project/sudo/commit/9757d29a24ac1872872cf09757b0439c54089707
-
Testing the memory safe Rust implementation of Sudo/Su
└───────────────────────────────────────────────────────────────────────────────────────┘
As a comparison, this is the output for https://github.com/sudo-project/sudo:
0.0439 secs
-
what is funniest prompt u have got from the terminal for incorrect password
Complete list (can be found here, files ins_*.h):
-
Get gnu gnu'd
Fun fact, the “incident will be reported” message was close to being removed from sudo recently: https://github.com/sudo-project/sudo/commit/6aa320c96a37613663e8de4c275bd6c490466b01
- ‘Godfather of AI’ quits Google and gives terrifying warning
What are some alternatives?
tinyvec - Just, really the littlest Vec you could need. So smol.
doas - A port of OpenBSD's doas which runs on FreeBSD, Linux, NetBSD, and illumos
tamago - TamaGo - ARM/RISC-V bare metal Go
cosmopolitan - build-once run-anywhere c library
rust - Rust language bindings for TensorFlow
php-docker - Docker Official Image packaging for PHP
usbarmory - USB armory - The open source compact secure computer
sudo-rs - A memory safe implementation of sudo and su.
advisory-db - Security advisory database for Rust crates published through crates.io
dotfiles
UnsoundCrates - Black list of all crates that promotes unsoundness
systemd - The systemd System and Service Manager