BluescreenOfDeath

joined 6 months ago
 
[–] BluescreenOfDeath 4 points 1 week ago* (last edited 1 week ago)

No no no, you just don't get it.

Windows can be full of all this anti-consumer, privacy invading, Orwellian bullshit, but it's OK. You can just use this program made by some random person online with no security auditing or available source code to reach into the bowels of the OS and remove all that stuff. Don't think too hard about it, it totally works.

Just ignore the small command prompt window that appears and disappears every 10 minutes, or the sudden constant CPU load by svchost.exe. That's just your computer computing ~~bitcoin~~ awesomeness!

[–] BluescreenOfDeath 3 points 1 week ago

Honestly, it reminds me of when I was a teenager. Full of that overwhelming sense of confidence that I knew better than others, looking for arguments to pick online. After a couple of times being shown clearly how little I knew, I started talking less and listening more.

With a fulltime tech job, two kids, and an ex-wife to deal with I just don't have the time to grind online axes anymore.

[–] BluescreenOfDeath 3 points 1 week ago (2 children)

If nothing else, he's very passionate about showing how much it bothers him that people can have different opinions about operating systems. He's obsessed over it, or else he wouldn't make two different communities and post in them daily about how much he hates Linux.

I hate Windows with a burning passion for a number of extremely valid reasons, but I only say something about it here and there. I've got too much to do IRL to be this bothered about anything online.

[–] BluescreenOfDeath 4 points 1 week ago* (last edited 1 week ago) (4 children)

20 lines of code you're going to compare to a single line of code that is commonly published and couldn't have happened by a simple typo or a common single line of code -seriously?

What's stopping some Russian virus writer from making a virus that bricks motherboards? The root problem for this isn't Windows or Linux, it's that motherboard manufacturers implement UEFI in a way that the operating system can interfere with the firmware and brick the motherboard. That it might be easier on Linux vs Windows isn't putting the blame where it belongs.

Windows in all ways makes it far more difficult to fuck up shit! (but Linux allows me to fuck shit up!) - It's not a fucking benefit!

Linux has some safeguards, too. Almost every desktop distribution of Linux ships with the version of rm that won't recursively delete from root without the flag -no_preserve_root and I don't think you're going to argue that someone could type that by accident.

But no, on the whole, Linux is a more advanced operating system, and the things I enjoy about it come from the things that make it different.

For one, it talks to me about what the problem is. If I'm having a problem, it doesn't just bluescreen and give me some random error code. Something will crash, but I can swap to a TTY when my GUI stops responding, check the kernel buffer, and see that I'm out of disk space on / for some reason. So I'll delete some files and get the system usable again, clean up my root disk to create some space, and keep going with my life.

Old sever based distros are insecure because 'old packages' (out-dated)

This is just flatly not true. Debian and other non-bleeding-edge distributions don't push the most modern version of packages, but they do push modern security patches.

https://www.debian.org/doc/manuals/securing-debian-manual/security-update.en.html

As soon as new security bugs are detected in packages, Debian maintainers and upstream authors generally patch them within days or even hours.

.

Cloud strike affected almost 0 desktop users and was entirely Cloud Strike's fault.

If it's fair game to point out how Intel made a bad driver for Linux that can damage a display, I think it's also fair game to point out that Cloudstrike caused major reputational damage to Windows because of the nature of their kernel-level driver having a bug that caused an almost global systems outage.

Like it or not, software is complex at a level we rarely give it credit for being, and it's all written by imperfect humans. Sometimes things happen.

You have a voice here.

Sure, because trolling in an echo chamber gets boring.

You're posting in here multiple times per day, almost every day, for months. Same with /c/linuxsucks.

I'm torn between being sad on your behalf or impressed that you're so dedicated to grinding this axe.

Did you think you were dealing with an idiot?

Given that you're not touching the TPM part of the conversation anymore, I'll say that while I don't think you're an idiot, I'm confident that you're not nearly as knowledgeable about this as you'd have everyone believe.

So now I'm just wondering how long it'll take for you to break out the banhammer because I'm not fitting into your little box the way you want me to.

[–] BluescreenOfDeath 5 points 1 week ago (6 children)

Currently stickied on r/linuxsucks with sources for the first two claims.

For shits and giggles, I decided to dig up the links, and you're not going to believe how this isn't the flex you think it is.

First off, the claim is that "Linux" is what causes the damage.

From your first link, that running sudo rm -rf / can brick a motherboard isn't a Linux only problem. From the very article you cite as a source, it says:

[...]with about 20 lines of code on Windows, you can cause the same havoc.

This isn't a Linux issue, it's an issue with how UEFI is implemented.

The second claim is damaging a display. The article cites a link to a Phoronix post about an Intel engineer admitting that Intel made the mistake in their driver, and rolled back the update shortly thereafter. This only affected people who ran bleeding edge distributions.

A botched driver on Windows would be capable of the same problems. Cloudstrike ringing any bells?

I'll also say I find it rather telling that you're the sole moderator and sole poster both here, and in /c/linuxsucks. Seems like a troll has found a bridge and is interested in picking fights.

[–] BluescreenOfDeath 2 points 1 week ago (2 children)

Your first reply isn't even an anecdote. You're simply doubting what I experienced and the experience is validated (source: CoPilot):

I'm not doubting that Windows could repair a drive that Linux couldn't. Linux filesystem repair tools for proprietary filesystems like NTFS and ExFAT aren't very good because they're reverse engineered.

What I doubt is that connecting an external HDD with filesystem errors would cause a Linux system to hang. I've connected countless drives in various stages of failure without ever having one hang the whole system.

$5 usb Bluetooth working fine in Windows. -Maybe Linux is simply racist?

The Chinese manufacturer only makes drivers for their cheap knockoff hardware for Windows. The vast majority of people's complaints about Linux can be solely attributed to lack of commercial support. Just look at how much has changed about Linux gaming since Valve started investing time and money into WINE/Proton.

It's not realistic to expect the community to develop flawless drivers for all the cheap hardware you'll find. Even if we assumed that all the hardware was fully documented (which it almost never is), there aren't enough people volunteering their time to actually write the code. When you add in the time required to reverse-engineer it, it gets even worse.

This I just flatly don't believe. Do you have any citations, or am I supposed to just take your word for it?

Currently stickied on r/linuxsucks with sources for the first two claims. The third was in the installation manual for RedHat which I no longer have access to or can find sources for. -Somewhere it's documented.

...So that's a no?

Yeah, ok. That hardware is better defense than a software solution and is backed by legit professionals.

I don't disagree that the TPM is a fantastic hardware solution for cryptographic key storage. I'm just not under the mistaken impression that it automagically makes Windows safer just by existing. If you knew anything at all about how it actually works, you'd see that it's not some panacea for malicious software. Assuming a user doesn't just click [Next>] whenever a software prompt appears, it can help safeguard a machine from invisible infections. But the vast majority of software infections come from software masquerading as legit and tricking the user into installing it.

There's nothing stopping a malicious actor from creating a program that tricks a user into installing a malicious key into the TPM and allowing that malicious software to run in the same trusted manner as the Windows bootloader would. Thus achieving the same rootkit/bootkit infections that are currently possible on non-TPM machines.

[–] BluescreenOfDeath 3 points 1 week ago (12 children)

Had Linux crash while a portable drive was attached. When mounting that drive in Linux, Linux would freeze.

Having used Linux for data recovery from failing hard drives for ~7 years, I find this hard to believe. I've recovered data from hard drives on Linux that Windows refused to enumerate with a drive letter, which tends to be a prerequisite for almost all commercial data recovery software.

'Chinese cloned' Bluetooth chips are an issue for Linux.

Dodgy hardware is dodgy? Say it ain't so!

Then there's the very real potential to destroy hardware which Linux has done. - Mainboards, displays, and optical drives.

This I just flatly don't believe. Do you have any citations, or am I supposed to just take your word for it?

TPM2 is a security measure that protects from rootkits, bootkits (Linux had one of these recently), and keyloggers

Tell me you know nothing about what TPM actually is without just telling me you don't know.

The TPM isn't some magical piece of hardware that makes Windows safer, it's a device that can store cryptographic keys to ensure software run is signed by a trusted source.

Short term, the TPM can prevent malicious software from running; but if a user can be tricked into running malicious software to install a bootkit, they can just as easily be tricked into running malicious software that installs a key into the TPM that was used to sign said malicious software, thus allowing it to run on a system with a TPM.

Don't get me wrong, Linux isn't perfect by any means. It's a community project, and it has its own peculiarities and issues. But I find them much easier to handle than fighting an operating system that I have to pay money for, that still looks for ways to further monetize me. I've been using Linux fulltime for almost 8 years now, and I find Linux's strangeness much easier to handle and work with than Windows' uncompromising enshittification.

[–] BluescreenOfDeath 5 points 1 week ago (14 children)

Windows "literally saved hardware from the trash" but windows 11 forcing people to upgrade to computers with a TPM?

Does not compute.

view more: next ›