Sure, except that you have functions like processing fonts and image formats in the kernel. Layer on userland stuff like OLE and IE and you have a cocktail for security hell.

When things work correctly, NT has historically had a more robust and accessible set of controls, although I think modern UNIX closed that gap. But things often don't work correctly, and the complexity of the ecosystem makes it pretty trivial to exploit.

It is not perfect, but it possible to configure properly.

Also NT always focused on the user productivity first and as server afterwards.

Whereas UNIX always focused on the server first and user productivity afterwards.

It is always a mix and match between security and productivity.

A security model defeated by a bonkers architecture.

I’m especially baffled that font processing is in the kernel. Allegedly, Windows 10 now moves non-system fonts into a restricted user-mode process, so exploits are a lot harder. But it still acts like the kernel is doing the processing, for backwards compatibility.

>object capabilities, much more powerful than UGW permissions.

    man 5 acl

>If people decide to run as root that's their problem. Also you don't need root to exploit UNIX users, getting hold of their $HOME is way more valuable than getting hold of the OS.

Same on windows.

>>getting hold of their $HOME is way more valuable

>Same on Windows

Windows 8 Metro/Modern/UWP apps do not have access to your home directory.

What is being done to improve the situation on the Linux side of things?

I believe Flatpak/Snap (Fedora/Ubuntu's new app packaging formats) makes this possible quite easily. It'll take quite some time until these initiatives really take off, but then again things aren't all that different on Windows today. A typical Windows system is still one Office macro away from losing $HOME.

But then no standard desktop OS is immune to users executing code from untrusted sources, you need something more locked down like iOS for that.

To get a macro running in office the user has to explicitly ignore security warnings to do it, this would be the same in linux or MacOS where code execution capabilities were present.

I'm making a comparison to Windows, and my point was that it's no different there today despite the fact that Metro apps exist (just like Flatpak/Snap exists on Linux). Walled gardens such as iOS are definitely superior in that respect.

> To get a macro running in office the user has to explicitly ignore security warnings to do it, this would be the same in linux or MacOS where code execution capabilities were present.

Sure, but it's pretty easy to ignore those warnings when you see something like [1] or [2].

[1]: https://3.bp.blogspot.com/-ginpmnFHC_E/V3J3kFADrxI/AAAAAAAAo...

[2]: https://pbs.twimg.com/media/CiqwqUOWgAAVTzE.jpg:large

indeed those messages are good examples of social engineering, but when comparing OS security there's nothing inherent about MacOS or Linux that would make them any more resistent to the same kind of social engineering attack.

I'd suggest that the reason that there are fewer attacks of that nature on those platforms isn't down to superior OS security but less profit available to attackers, due to smaller market share and perhaps lack of a ubiquitous target app. like office.

I think you're missing my point. I'm not saying either is better in that respect (like zyx321 claims for Windows), I'm just saying they're both just as vulnerable despite the existence of sandboxed apps.

The IEEE 1003.1e draft 17 ("POSIX.1e") document describes several security extensions to the IEEE 1003.1 standard. While the work on 1003.1e has been abandoned, many UNIX style systems implement parts of POSIX.1e draft 17, or of earlier drafts.

Note the implement parts of, that is not something UNIX has in any portable way.