>>110270693
GNU was right again.

>>110270693
minimalists btfo'd once again

>>110270693
>>switches to Musl Libc to be secure
tarding off the bat. cute.
>>gets hacked by default (ssh)
>OMG if you use these exact software versions, allow root in ssh, and use no key auth, you can get HACKED. IT'S OVER.
>>(btw rusttrannies as vulnerable, it's purely a logical bug in musl crypto lib logic)

% rg 'crypt\(' ~/.rustup/toolchains/*/lib/rustlib/src/rust/library
%
% readelf -s ~/.rustup/toolchains/*/lib/rustlib/*-musl/lib/libstd*so | rg crypt
%

>OMG IT'S REALLY OVER

>>110270693
>Switches to permissive cuck license tranny code
>Gets hacked
Couldn't be me. Another GNUGOD victory.

if you allow password auth security was never a priority, on the other side imagine all the routers you can hack now since they all fork openwrt nowdays.

>>110272599
>if you allow password auth security was never a priority
for any local user, AFAIR

>>110270693
GNU was correct all along.

One day people will understand that correctness trumps quirky one-liners in the long run.

>>110270693
Rust would absolutely have fixed it. The cause was, as is so often with C, in-band error values.
A Rust implementation would probably have used Option or Result. It's quite sad, too, cos Thompson had it figured out in 73 already.
See INTRO ( II ) in https://dspinellis.github.io/unix-v4man/v4man.pdf, in particular:
>From assembly language an erroneous call is always indicated by turning on the c-bit of the condition codes.
>The presence of an error is most easily tested by the instructions bes and bec (‘‘branch on error set (or clear)’’).

>>110270693
Of C had options instead of sentinels, this wouldn't be an issue

>>110273470
you misunderstood.
tech illiterate /g/eet op thought "rust" (he doesn't know the difference between lang, lib, and lib impl) was vulnerable because std depends on libc.
as shown in >>110271936, std doesn't call crypt(), nor calls anything that calls crypt(). lol.
what you're pondering is not something a tech illiterate can grok.

>>110273736
>thought "rust" (he doesn't know the difference between lang, lib, and lib impl) was vulnerable because std depends on libc.
nope, you and the idiot you reply to, both failed to understand the obvious point: this is one of these bugs that "rewrite in rust bruuuuh (before you troon out)" would not help at all (and would probably break more things with more of logical bugs - as rusties even broken basic utils.

Rust broken (llm summary) : cp, shred, mv, ln sort date - and few more:

Command


What was broken

cp


Incorrect error handling for file paths ending in /

shred


Incorrect error when given a directory

mv


Incorrect source errors and missing error-message context

ln


Blamed the destination instead of the source

paste


Omitted filenames in read/open errors

sort


sort -c directory exited successfully instead of reporting an error

There was also a mv -n regression involving moving a file onto itself.

These were reported upstream with fixes and tests.
DEV Community
+1
2. More serious Ubuntu regressions

date – Ubuntu 25.10's version ignored date -r FILE, causing automatic update checks to malfunction.
Reddit

cp – A combination of -a -L -f broke Ubuntu live-image builds in July 2026.

>>110273830
>oh no "it" is even more retarded than previously thought

>>110272599
OpenWRT doesn't use OpenSSH

>>110273917
>I can't comprehend even simple ideas
yeah, we can tell

File: null_was_too_much_for_the(...).jpg (424 KB, 1200x1787)

424 KB JPG

This is were it went wrong. The old UNIX hackers back in the 90s knew that a function should return NULL for a string that doesn't exist. Weak millennials had to remove it cause they were too dumb and lazy to write an if to check if crypt returns null or not and they had to have their own special little wildcard string returned. IT'S FUCKING NULL YOU FAGGOT ONIONS DRINKING MILLENNIALS.
This is 100% the reason behind the existence of Rust. Cases like these, where programming in a real language made for real men was too hard for millennials who are used to webdev faggotry.

>>110274404
it can use whatever, it is a full fledged linux distro at this point minus the graphics parts.

>>110274631
we should normalize Result types that enforce checking

File: images (6).jpg (41 KB, 554x554)

41 KB JPG

>>110274631
how do you even drink an onion