Unable to load image

Linux :marseypenguin: being secure :marseycop2: is a common misconception in the security :capyhacker: and privacy :marseypedo: realm :marseyspyglow::!marseyjewoftheorientglow:

https://madaidans-insecurities.github.io/linux.html

GNU+Linux bros :marseypenguin: I don't feel so good :marseydisintegrate::marseyhacker::capyhacker:

!codecels discuss

57
Jump in the discussion.

No email address required.

Most programs on Linux are written in memory unsafe languages, such as C or C++, which causes the majority of discovered security vulnerabilities. Other operating systems have made more progress on adopting memory safe languages, such as Windows, which is leaning heavily towards Rust, a memory safe language, or macOS which is adopting Swift. While Windows and macOS are still mostly written in memory unsafe languages, they are at least making some progress on switching to safe alternatives.

This is an r-slured fricking paragraph and plain wrong. All the OSes have experimented with rust without any using it to any significant degree.

The Linux kernel itself is also extremely lacking in security. It is a monolithic kernel, which means that it contains a colossal amount of code all within the most privileged part of the operating system and has no isolation between internal components whatsoever.

and then

Other kernels, such as the Windows and macOS kernels, are somewhat similar too, in that they are also large and bloated monolithic kernels with huge attack surface

xD

The rest of it is scraping the barrel for things to criticise. Maybe someone will pretend to be sudo. derp.

The one valid point that the article does make is that OSes were designed to be multi-user where you'd not trust the other users. Now they're almost always single user but you wanna be suspicious of the applications instead. But I'm not sure if there is really any good way to solve that without completely redesigning how computers work.

Jump in the discussion.

No email address required.

But I'm not sure if there is really any good way to solve that without completely redesigning how computers work.

It's solved by mobile OSes with their strict sandboxing and easy gui permissions settings, but yes, the desktop is a long ways away. With Linux all we have are janky cowtools like selinux, apparmor, firejail, flatpak (bleh) and so on. Qubes OS is a usable system that actually makes good progress towards solving the problem, while something more like Genode/Sculpt OS is experimental but with a cleaner design and where we need to be heading towards in the long run.

Jump in the discussion.

No email address required.

>Qubes OS is a usable system

:marsey#xdoubt:

Jump in the discussion.

No email address required.

its completely usable yes

Jump in the discussion.

No email address required.

I wonder how well stuff like Guix and Nix solve this issue, if at all.

Jump in the discussion.

No email address required.

>rust is safe because le memory-safety

Isn't Lemmy written in Rust, and didn't they just announce a massive XSS vuln? Memory-safe doesn't mean well written.

Jump in the discussion.

No email address required.

>xss in typescript

>rust le bad

:#marseyravecope:

Jump in the discussion.

No email address required.

I actually like programming in rust but I wish the let's rewrite the whole of Linux in rust people would frick off.

Jump in the discussion.

No email address required.

they are legit glowies who want their non-foss spyware rust backdoors in

there's a reason rust freaked the frick out at someone making a compiler

Jump in the discussion.

No email address required.

why do you think Rust is non-FOSS? :marseyconfused:


Follower of Christ :marseyandjesus: Tech lover, IT Admin, heckin pupper lover and occasionally troll. I hold back feelings or opinions, right or wrong because I dislike conflict.

Jump in the discussion.

No email address required.

He's not saying it's non-FOSS, he's bringing up how there's basically just the one official rust compiler instead of there being multiple competing compilers like with C and C++, and most other programming languages. This is due to the fact that Rust doesn't actually have a formal specification, specification is whatever the Official Compiler does. This isn't a wise move because it doesn't guarantee that rust code written in the past will behave the same in the future or present. It also makes it borderline impossible to create an alternative compiler, since there's nothing saying that a specific keyword should exist or behave a certain way. This is bad.

Jump in the discussion.

No email address required.

not saying it’s non-FOSS


non-foss spyware

:marseysurejan:

no spec

The fact I’ve heard this as the paramount complaint of Rust in current year actually inspires more confidence in it imo.

There’s no document that people would ignore anyway but it’s super duper important so a neurodivergent neckbeard can get a half-broken gcc port? This is the biggest complaint about Rust?


Follower of Christ :marseyandjesus: Tech lover, IT Admin, heckin pupper lover and occasionally troll. I hold back feelings or opinions, right or wrong because I dislike conflict.

Jump in the discussion.

No email address required.

I mean there's the fact that the actual rust compiler is obscenely aids to actually bootstrap, etc. I think you're just being contrarian here because you want marseycoin or something. It's pretty clear that this is an actual issue.

Jump in the discussion.

No email address required.

I can write it less smugly but I don’t legitimately think a single compiler ecosystem is that big of an issue, no.


Follower of Christ :marseyandjesus: Tech lover, IT Admin, heckin pupper lover and occasionally troll. I hold back feelings or opinions, right or wrong because I dislike conflict.

Jump in the discussion.

No email address required.

More comments

GNU Hurd chads simply can't stop winning. monolithicels stay seething

Jump in the discussion.

No email address required.

Imagine not having to interject any longer

https://i.rdrama.net/images/16891991024874403.webp

Jump in the discussion.

No email address required.

>someone might sneak a bash script on your system to intercept your sudoer password :marseypearlclutch:

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.