Windows is being bombarded by malware every second of every day. Linux, with its 6% of desktop user market share - not so much.
Linux dominates the server space. Basically any company with access to lots of capital or trade secrets is running Linux servers. It is a massive, massive opportunity for hackers to hit jackpots. Linux gets bombarded by attackers constantly and holds steadfast. I’m not sure where you get this idea that this isn’t the case…
Edit: Just to really drive this point home, 65% of Microsoft Azure servers are Linux. Let that sink in, the majority of even Microsoft’s cloud servers are Linux. That is the one company you would think would be pushing Windows, yet here they are talking about their high quality Linux offerings!
“With over 65% of Azure workloads running Linux, our commitment to delivering high-quality Linux VM images and platforms remains unwavering.” - Microsoft
But the discussion is about user-space. Not everything from server-Linux translates 1:1 into desktop-Linux.
For example, there are no anti social engineering security measures in Linux. Just sudo and break anything and everything. Whereas on Windows, if you try doing something stupid, most probably Windows won’t let you, or will at least make you jump through some hoops.
They’re very much not, that’s the point. There are things that require the NT AUTHORITY\SYSTEM account permissions. Admin can do a lot in Windows, but not everything.
EDIT: also, Windows throws the UAC prompt around much less than Linux asks for the root permissions. ANY software update on Linux needs root. Even regular users are starting to get that if they see the UAC prompt, something big is about to happen.
You do have a point—Linux does not warn users against running superuser commands constantly and naggingly. Also not the beginner-friendly distros like Zorin, Mint and Ubuntu (as far as I know).
To me that’s fine, because I know not to just run any command, but my grandma who gets an email from a trustworthy-sounding person telling them to run “sudo install this keyboard logger and Rustdesk scripted installer” will not know better.
So then that begs the question, given you seem to know something about it: how should this be addressed? (I assume you know something about this—I don’t even know what an UAC prompt is.)
On the other hand: How does Windows stop users from running the .exe file a trustworthy-sounding person emailed them? You could argue that’s easier to ask people to do than to open the terminal and write a command in there.
That’s basically the equivalent of the root credentials prompt in Linux.
So then that begs the question, given you seem to know something about it: how should this be addressed?
I’m not sure it can be addressed. It would require completely redefining how permissions work in Linux, I think.
The way Windows handles it is that if updates are coming in through “secure” channels (official OS updates, Store application updates, updates to applications that do not touch any protected areas), administrator permissions are just never required. For example, a browser update just happens in the background. You open your browser, use it, you close it for the day, you open it the next day, and it’s the new version already.
I don’t think this could ever work in Linux due to the fundamental difference in how software is installed. In Windows, applications have their own folders, in Linux everything is dropped, based on type, to just a couple of “centralised” folders, right? So, every app must have access to those folders, which prevents this kind of “if you don’t touch this, you won’t need admin” approach.
Maybe things like Flatpacks could solve it, since the apps (to my understanding) are more self-contained, a bit like UWP apps in Windows.
On the other hand: How does Windows stop users from running the .exe file a trustworthy-sounding person emailed them?
The UAC prompt has a very specific design and will warn you with an orange colour band if the application is not signed with appropriate certificates. If it’s a suspected dangerous application, the band will be red.
You could argue that’s easier to ask people to do than to open the terminal and write a command in there.
You can send them an .sh file for the exact same effect. Bah, you can send them a .pdf file that’s actually an executable script in Linux.
Linux dominates the server space. Basically any company with access to lots of capital or trade secrets is running Linux servers. It is a massive, massive opportunity for hackers to hit jackpots. Linux gets bombarded by attackers constantly and holds steadfast. I’m not sure where you get this idea that this isn’t the case…
Edit: Just to really drive this point home, 65% of Microsoft Azure servers are Linux. Let that sink in, the majority of even Microsoft’s cloud servers are Linux. That is the one company you would think would be pushing Windows, yet here they are talking about their high quality Linux offerings!
“With over 65% of Azure workloads running Linux, our commitment to delivering high-quality Linux VM images and platforms remains unwavering.” - Microsoft
But the discussion is about user-space. Not everything from server-Linux translates 1:1 into desktop-Linux.
For example, there are no anti social engineering security measures in Linux. Just
sudoand break anything and everything. Whereas on Windows, if you try doing something stupid, most probably Windows won’t let you, or will at least make you jump through some hoops.Windows gives you a UAC prompt or needs one to run a cmd prompt as admin, both of which are functionally the same as sudo…
But, to circle back to the core statement. Yes it is. And Linux holds steadfast.
They’re very much not, that’s the point. There are things that require the
NT AUTHORITY\SYSTEMaccount permissions. Admin can do a lot in Windows, but not everything.EDIT: also, Windows throws the UAC prompt around much less than Linux asks for the root permissions. ANY software update on Linux needs root. Even regular users are starting to get that if they see the UAC prompt, something big is about to happen.
You do have a point—Linux does not warn users against running superuser commands constantly and naggingly. Also not the beginner-friendly distros like Zorin, Mint and Ubuntu (as far as I know).
To me that’s fine, because I know not to just run any command, but my grandma who gets an email from a trustworthy-sounding person telling them to run “sudo install this keyboard logger and Rustdesk scripted installer” will not know better.
So then that begs the question, given you seem to know something about it: how should this be addressed? (I assume you know something about this—I don’t even know what an UAC prompt is.)
On the other hand: How does Windows stop users from running the .exe file a trustworthy-sounding person emailed them? You could argue that’s easier to ask people to do than to open the terminal and write a command in there.
That’s basically the equivalent of the root credentials prompt in Linux.
I’m not sure it can be addressed. It would require completely redefining how permissions work in Linux, I think.
The way Windows handles it is that if updates are coming in through “secure” channels (official OS updates, Store application updates, updates to applications that do not touch any protected areas), administrator permissions are just never required. For example, a browser update just happens in the background. You open your browser, use it, you close it for the day, you open it the next day, and it’s the new version already.
I don’t think this could ever work in Linux due to the fundamental difference in how software is installed. In Windows, applications have their own folders, in Linux everything is dropped, based on type, to just a couple of “centralised” folders, right? So, every app must have access to those folders, which prevents this kind of “if you don’t touch this, you won’t need admin” approach.
Maybe things like Flatpacks could solve it, since the apps (to my understanding) are more self-contained, a bit like UWP apps in Windows.
The UAC prompt has a very specific design and will warn you with an orange colour band if the application is not signed with appropriate certificates. If it’s a suspected dangerous application, the band will be red.
You can send them an .sh file for the exact same effect. Bah, you can send them a .pdf file that’s actually an executable script in Linux.