I installed Opera and used it exclusively.
Why do people use Opera? It's a proprietary Chrome fork owned by a Chinese company.
I installed Opera and used it exclusively.
Why do people use Opera? It's a proprietary Chrome fork owned by a Chinese company.
Me in an alternate timeline where Linux is proprietary and the defacto OS on the majority of computers:
#8 reawakened my nervousness about the lack of virus protection on Linux. With every milestone we celebrate it becomes more likely that malicious people target desktop Linux with their malware, and I don't think the "Linux is inherently secure" mentality helps. I hope clamav's on access scanner is fixed and improved so it becomes commonplace before there's some big newsworthy scandal.
People were saying the exact same thing when I first started using Linux in 1999-ish
What is survivorship bias aka gambler's fallacy?
I'm not saying Linux is immune, just that people have said that, practically word-for-word, forever.
That's not it though. Linux doesn't have a problem with viruses, didn't have it before, doesn't have it now. Predicting that it's going to start right now 20 years in a row isn't a good idea refardless, and pointing it out is a right thing to do.
Which doesn't mean it couldn't really start one day.
"I have never been hacked before. Why would it start happening now?"
No one said that though. What was said was that as more people use Linux we will see more malware. And they've been saying that forever.
Here is an article talking about it from 2003 https://www.theregister.com/2003/10/06/linux_vs_windows_viruses/
If I knew how to search Usenet these days I'm sure I could find something from the 90s
It's not untrue, actually, is common sense that there will be more malware, but it implies Linux's only advantage is security through obscurity.
People have been worrying Linux is going basically become Windows over the next couple of years for 2-3 decades now. Malware is a serious problem that Linux users should take precautions from, but it seems clear by now that what security advantages it has aren't based on obscurity.
Granular permissioned access for apps from trusted supply chains is better than attempting deny lists based on signatures (AV).
I still use it, but I put way more effort into SLSA, securing containers, flatpaks, and limiting their blow back. From there its keeping up with CVEs in ways that do not create more or break functionality.
I will say A LOT of the Linux software ecosystem is was more secure than Window's default.
I don't think a Linux anti virus program would be such a big security win. Phishing is the biggest security threat to most users, and no amount of software can prevent that.
Sure, downloading and running random shit is a concern, but people in that group are a bit of a lost cause. The best solution for that is to harden the OS, prevent running executables through the GUI, or from user folders (I think SELinux could do that), disable sudo on the user account, and only allow installing Flatpaks. The security of Flathub may not be perfect, but it's a smaller attack surface than the whole internet.
But even if you do that, an Indian call center scam is still going to manipulate your grandma into buying Amazon gift cards, so... It's a lost cause.
... but people in that group are a bit of a lost cause.
touche. I don't think the existence of other threats is a reason to dismiss this one. And I don't think simply prohibiting running random executables is sufficient as it isn't 'most users' who are switching to Linux. The people likely to switch to Linux are also the people likely to want to run programs that aren't yet distributed in repos. I can imagine a scenario where the malware is hidden in a program hosted on a custom flatpak repo and requires permissions for normal operation that'd make flatseal ineffective for stopping the malware.
The ideal anti-virus in my mind would ignore programs installed from official repos and on access scan ones installed from anywhere else. It'd also keep track of critical vulnerabilities to give you a heads up about updating your system.
There is virus protection for Linux if you really want it (both free and paid).
Why are we shouting?
Anyway, don't waste your time with "antivirus" software. That is not how you secure a system.
That is not how you secure a system.
Yes, but projects like Wayland which are trying to do this get shouted down.
Your viewer must be parsing #8 as # 8.
You're free to not 'waste time' with anti-virus but I prefer the peace of mind.
You need to put a backslash before the hash tag. In Markdown a # is a headet
No? There needs to be a space between on piefed and that's how it works on github too.
https://www.markdownguide.org/basic-syntax/
Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn't specify it per se.
As Lojcs said...
The Markdown format expects a space after whatever number of #s you put at the start, for it to be a corresponding level header.
Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches.
e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using discount, I realised where I was being wrong.
The whole problem is because format doesn't actually expects the space there, and it's left to the interpretation of the parser
I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown.
I personally like how Doxygen implements it.
Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement.
The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different
AV is a joke. Best thing is ephemerality. No persistence
Immutable, ephemerable, granularly permissioned, and encrypt EVERYTHING to enforce said permissions.
1000x better than software signature hunting
You lost me at the encryption part. How does encrypting enforce permissions?
Enforces confidentiality and integrity.
Encryption on transports protects from man in the middle and sniffing. At rest protects evil maid exploits, which for these systems is more about preventing malicious software being swapped in place of trusted software.
The same applies to encryption of links like pcie and memory with the time of transport and rest changing.
It's all fun and games until some asshole slips something into your trusted package manager.
Exploits are the deal pain
Well yeah, you need to use Linux, the Linux way to make it secure.
If you are running VSCode as root after having logged into the DE as root and installing extensions willy-nilly, it won't matter that your RHEL has SELinux installed.
Here's my comments on it being a mostly normal user of Windows.
Three big problems if ads is becoming a thing. Three medium problems. One small, one you, and one what the fuck.
I agree that an email program is not Microsoft’s problem. However, there was a real issue there.
His point was that he knew how to easily use SSH to get around a badly behaved Linux GUI program that was monopolizing or disabling the UI. He did not know how to accomplish that on Windows.
As a Linux user, this scores points for me as it does highlight the flexibility, power, and control that Linux offers. It is also true that you have more power at the Linux command-line (even in a world with PowerShell) which is what SSH gives you access to.
That said, this article came across too much like “Windows does not work exactly like Linux and does not have all the things I love about Linux”. It also came across like a Linux expert being frustrated with a system he does not know as well.
We have had years of these kinds of articles slamming Linux when Windows people expect it to work exactly like Windows does. Those articles are dumb. We do not need to start filling the world with Linux versions of the same.
All of the stuff on this arrival is small time, first time run noise. Use it for a month and give an honest assessment of the pros and cons. What saved you time once the system was set up? What took longer? What entirely new capabilities got added to your workflow? What limitations were you just not able to overcome?
The two that I think are more systemic are OneDrive and Ads. Those are going to continue to drag on you long after the initial setup issues have faded into the background.
Hello, my name is Jack Wallen, and I'm a glutton for punishment.
Bro really wants us to know hes been a bad boy 😭
This feels like an article for non-tech Linux users who hate Windows and want their bias confirmed.
Ok, that's what it felt like
To me, it felt like an obvious imitation of the myriad of articles that often have someone try Linux out, shortly, and then – often with obvious not understanding or just a surface level insight – proudly and definitively stating (or, at least, subtextually implying) that Linux was interesting but clearly not ready to be a Real™ operating system, etc.
But it seems most didn't read it as that, either.
Would love to see someone who spent 30 years on Windows spend a week on Linux...oh boy..
We have seen that a lot. It often ends with an article a lot like this.
That said, many, maybe even most Linux users started Windows users first. So, not everyone writes a snarky article and goes back.
I think a Windows user that is adventurous enough to try Linux is more likely to be pragmatic and open minded about it. They can push through basic issues like the ones raised in this article to get to the real experience underneath. Many of them like what they find enough to stick around.
But we get our fair share Linux sucks articles that are not better than this one.
top 56 comments