FEfermuch·Nov 6, 2023
It seems like those changes are noted here: https://github.com/memorysafety/sudo-rs#differences-from-ori...
In The first stable release of a memory safe sudo implementationtrifectatechfoundation
sudo-rs
Rust2023–2026
trifectatechfoundation / sudo-rs
sudo-rs
A memory safe implementation of sudo and su.
21Distinct people
21Mentions
0Explicit recommenders
4.5KGitHub stars
What to know before exploring
What it is
A memory safe implementation of sudo and su.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year21 dated mentions
Observed mentions: 2023-04-26 19:56:43 UTC to 2026-09-15 08:17:31 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 0 | 3 |
What Hacker News says
8 sourcesI'm assuming this project's aim is to replace sudo, in which case hand-waving away "Leaving out less commonly used features" is a bit worrying. What are these features? How uncommonly are they used? In which way will it fail if a configuration uses those features?
Edit: Looks like their github readme outlines some of these limitations, https://github.com/memorysafety/sudo-rs#differences-from-ori...
In The first stable release of a memory safe sudo implementationThe sudo-rs Cargo.toml [1] file seems very reasonable. This is the curse of being cross platform. The inclusion of https://github.com/Stebalien/tempfile as a dependency is responsible for the overwhelming majority of lines due to including *-sys crates for multiple OSs.
~/Code/tempfile !! tokei vendor
===============================================================================
Language Files Lines Code Comments Blanks
===============================================================================
GNU Style Assembly 8 1405 1276 39 90
C 1 3 2 0 1
Shell 1 23 18 1 4
TOML 25
Read the rest
1536 1178 234 124
-------------------------------------------------------------------------------
Markdown 29 2193 0 1560 633
|- C 1 2 2 0 0
|- Rust 11 277 220 19 38
|- TOML 8 60 58 0 2
(Total) 2532 280 1579 673
-------------------------------------------------------------------------------
Rust 917 811953 792140 4536 15277
|- Markdown 304 17252 124 14364 2764
(Total) 829205 792264 18900 18041
===============================================================================
Total 981 817113 794614 6370 16129
===============================================================================
[1]: https://github.com/memorysafety/sudo-rs/blob/60985b2f5f7ffa8...
And this is what that small list of dependencies pulls in:
https://github.com/memorysafety/sudo-rs/blob/60985b2f5f7ffa8...
In Testing the memory safe Rust implementation of Sudo/SuThe dependency list[0] looks pretty reasonable, AFAICT the overwhelming majority of that line-of-code count comes from autogenerated Windows API methods.
edit actual counts:
$ cargo vendor && cd vendor && {
for p in * ; do
echo -n $p
tokei $p | rg '^\s+Rust'
done } | sort -n -k 4 | tabulate
---------------------------- ---- --- ------ ------ ---- ----
errno-dragonfly Rust 2 9 8 0 1
windows_aarch64_gnullvm Rust 2 11 9 0 2
windows_aarch64_msvc Rust 2 11 9 0 2
windows_i686_gnu Rust 2 11 9 0 2
windows_i686_msvc Rust 2 11 9 0 2
windows_x86_64_gnu Rust 2 11 9 0 2
windows_x86_64_gnullvm Rust 2
Read the rest
11 9 0 2
windows_x86_64_msvc Rust 2 11 9 0 2
winapi-i686-pc-windows-gnu Rust 2 25 13 12 0
winapi-x86_64-pc-windows-gnu Rust 2 25 13 12 0
windows-targets Rust 1 54 46 3 5
output_vt100 Rust 2 67 55 0 12
cfg-if Rust 2 164 131 16 17
instant Rust 4 316 260 6 50
countsctor Rust 2 331 254 21 56
errno Rust 5 375 280 41 54
diff Rust 4 561 485 9 67
autocfg Rust 9 702 558 41 103
yansi Rust 7 741 627 3 111
signal-hook-registry Rust 3 818 566 150 102
fastrand Rust 4 830 710 16 104
hermit-abi Rust 4 847 601 5 241
pretty_assertions Rust 5 1231 1072 33 126
glob Rust 2 1589 1291 113 185
bitflags Rust 20 1715 1373 105 237
unicode-ident Rust 11 1794 1697 36 61
signal-hook Rust 17 1969 1520 147 302
tempfile Rust 15 2367 1928 102 337
quote Rust 17 2458 1979 148 331
redox_syscall Rust 23 3595 2996 83 516
log Rust 9 3635 2970 97 568
io-lifetimes Rust 15 4218 3605 80 533
proc-macro2 Rust 17 5286 4514 139 633
cc Rust 13 5861 4767 488 606
rustix Rust 236 39927 33837 1467 4623
syn Rust 92 51956 48946 493 2517
libc Rust 224 109836 99688 2073 8075
linux-raw-sys Rust 61 145628 145455 84 89
winapi Rust 405 179933 176630 3299 4
windows-sys Rust 281 497624 497608 4 12
---------------------------- ---- --- ------ ------ ---- ----
[0]: https://github.com/memorysafety/sudo-rs/blob/60985b2f5f7ffa8...
Way to improve security of sudo: make a daemon instead of setuid bina
5 points · Open discussionsudo-rs: A memory safe implementation of sudo and su
9 points · Open discussionIf you read the README https://github.com/memorysafety/sudo-rs
> Our current target is to build a drop-in replacement for most basic use cases of sudo. ...
> Some parts of the original sudo are explicitly not in scope. Sudo has a large and rich history and some of the features available in the original sudo implementation are largely unused or only available for legacy platforms. In order to determine which features make it we both consider whether the feature is relevant for modern systems, and whether it will receive at very least decent usage. Finally of course a feature should not compromise the safety of the whole program.
So seems like they're on the same wavelength as you are.
In Bringing Memory Safety to sudo and su