Bonum Certa Men Certa

How Secure Boot Could Have Ruined My First Linux Experience And Why IBM Is Making Things Worse.

Reprinted with permission from Ryan Farmer. Also available in Gemini

Historically, using Free and Open Source Software has been a “license to tinker”, and Linux was no exception.



If it didn’t do something you needed it to do, you could patch it with “something I found”.



If that hadn’t been the case, I would have never been able to start using Mandrake Linux in the 1990s.



You see, the family computer had this horrible piece of hardware in it called a “Winmodem”. And let me tell you about those.



Pretty much as the name implies, the manufacturer dropped a Windows driver, which essentially was the modem.



Theoretically, this had benefits, like the modem could be updated by simply installing a new driver, since most of the logic for the thing is in the software, which runs on the computer, in the Windows 98 kernel in my case.



But that benefit hardly ever materialized. If any manufacturer actually sold you a modem and then later updated you to v.90 or v.92 or something, I’m not aware of it.



They left me at K56Flex and x2, two competing specifications written by rival companies, that predated the ITU standard for v.90 and v.92 56k dial up modems.



Fortunately, most ISPs supported one, the other, or both, in which case it would go ahead and work, but the modem itself was STILL a problem.



Because you only had the Windows driver, and because it implemented the entire modem, without Windows, the modem did nothing. You had no Internet access at all. Dead hardware.



Fortunately, I found the source code to a module that I could compile and add to Linux, and it made the modem work well enough, that I could at least get by until I had saved enough to buy a Zoom 56k modem that supported the actual ITU standards.



The Winmodem was a parasite. Even under Windows, the damn thing made the entire system hang whenever it picked up or hung up the phone line, and then while it was running, it stole CPU time for the driver.



So, this is basically my “Richard Stallman and the Printer” story.



Eventually I was able to remove the Winmodem and the (somewhat unstable) out-of-tree driver, but when I needed to patch the kernel, nothing stopped me. Nothing could have stopped me because nobody had lost their mind and thought Microsoft was a security company.



We didn’t have these ridiculous “Security” charades by the purveyor of the least secure software on the planet.



(“Secure” Boot offers no advantages and the GNOME Desktop has even been tarred and feathered by a “Security” Theater screen by people at IBM Red Hat…… I use KDE now.)



While it is much less common now to encounter the need to run unsigned modules, everyone should be allowed to, without Microsoft in their way. Or in the way of even booting the computer.



Unfortunately with IBM Red Hat’s assistance, crazier things than “Secure” Boot are happening.



This includes the outlandish notion that most of the file system should be read-only (“immutable”) and shouldn’t be within the user’s reach because Apple does this with a toy OS.



How is the user supposed to edit flat configuration files to make systemd (their other disaster) behave differently? How is the user supposed to take software they want in /opt and put it in /opt?



I don’t think you can. And the “Transactional Upgrade” system sounds horrible.



An “everything or nothing” upgrade of every package on the system, even if some are broken, and the only thing you can do if some are is roll the entire thing back?



I will never install a distribution with an immutable file system.



These distributions are worse than useless.



Even IBM Fedora, which has been banging this drum the loudest, has had an immutable “spin” forever, says they’ll make it “Workstation” someday, and well, that hasn’t happened.



There’s just no way to make it actually work. Not if you want to configure the system at all, or do something like dnf update –security.



Don’t even get me started on “kernel lockdown”, where even root is somehow not allowed to change kernel variables.



If a user has so seriously misconfigured their system that a vulnerability exists, let them live with that.



But this really has nothing to do with Security. It’s about walling the user off from their own computer to enforce Windows, or at the very least, make Digital Restrictions Malware (DRM) more effective on Linux.



Quit screwing up my laptop.

Recent Techrights' Posts

Richard Stallman 'Unveils' His January 20 Talk in Montpellier, France
It's free (gratis)
Links 19/01/2025: Gaza Ceasefire and PR Stunt by Fentanylware (TikTok), Faking It by "Going Dark" to Incite American Addicts (Users)
Links for the day
They Won't Buy Vista 11 PCs or "Hey Hi" Copilot+++++++ PCs of Microsoft (With TPM)
Windows at 8%
No Time Left for President Biden to Pardon Julian Assange
At least they tried
Total Lock-down Ambitions - Part IV - The Latest Examples and the Perils (in Summary)
For further reading take a look at Musial's nice outline
FOSDEM is Called "FOSDEM" Because of Richard Stallman (RMS)
The overlap there seems timely; yesterday RMS spoke in French-speaking (in part) Switzerland where questions in French were accepted
 
Gemini Links 20/01/2025: Magnetic Fields, NixOS, and Pleroma
Links for the day
BetaNews Spreads Donald Trump Propaganda, Promotes Scams, and Publishes Fake 'Articles' About "Linux"
This is typical BetaNews
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, January 19, 2025
IRC logs for Sunday, January 19, 2025
[Meme] Hardware RAID and Hardware Raid
We're expecting attacks on the press in Trump's second term (no need to impress anyone for another election cycle) to be far worse than the first
What's Running on the Laptops
12 months have passed
[Meme] 404, Not Found
Kuhn: I'd like to interject for a moment, we made an alliance with the Microsoft-dominated LF to outsource projects to Microsoft GitHub and rich people gave us money to do this
Links 19/01/2025: TikTok (Fentanylware) Now Banned in the US, Convicted Felon Talks to Fentanylware CEO and Pooh-Tin About Undoing the Ban Despite the Supreme Court Unanimously Upholding It
Links for the day
FTC Realises Microsoft Buying Fake 'Clients' to Fake "Revenue" (Microsoft 'Buying' Services and Products From Itself!)
Ponzi scheme
Total Lock-down Ambitions - Part III - The Web Browser as DRM Pusher
A lot of "streaming" stuff is DRM
Video: University in Peru Honours Richard Stallman
Tomorrow, January 20, Richard Stallman speaks in France
IBM Termination Story and Information From Microsoft About Mass Layoffs
In 2 weeks of 2025 Microsoft already had 2 waves of layoffs
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, January 18, 2025
IRC logs for Saturday, January 18, 2025
Links 18/01/2025: Restoring the Great Wall of China and Economic Expansion in China
Links for the day
Guardian Digital (linuxsecurity.com) is Spamming the Web With Microsoft's Promotional LLM Slop About UEFI 'Secure' Boot (Which is Against Real Security)
This is an attack on honest journalism
Links 18/01/2025: TikTok's Endgame, "Car Freedom", and Spying in Cars 'Fines' GM (Settlement)
Links for the day
January 20: Richard Stallman Talk in Europe
evening time in Europe, around midday in the United States and Canada
Links 18/01/2025: Apple Getting Out of Hey Hi (AI) Slop (Too Much Misinformation), Chaffbots/Chatbots Try to Settle Copyright Infringement Lawsuits
Links for the day
What Fake News Sites Are Doing to GNU/Linux
The LLM slop about Linux serves two purposes
Links 18/01/2025: Microsofters Upset at Microsoft's Ridiculous Rebrands (Excuse for Massive Price Hikes), Chaffbot Company ('Open'AI) Faces More Lawsuits
Links for the day
Gemini Links 18/01/2025: Surge in Illnesses, ctags, and Gemsync
Links for the day
Slopwatch: Too Lazy to Write Real Articles, Offloading to Chatbots Instead (LLM Slop About "Linux")
The Web was already full of garbage before the LLM frenzy. Now it's even worse.
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, January 17, 2025
IRC logs for Friday, January 17, 2025