3 ms·
> There have been bad operating systems in the past (pre come-to-Jesus Microsoft, like 98 and XP...) Desktop OSes are generally pretty bad. Unsandboxed Windows
by TazeTSchnitzel 11y ago
> There have been bad operating systems in the past (pre come-to-Jesus Microsoft, like 98 and XP...)
Desktop OSes are generally pretty bad. Unsandboxed Windows and OS X apps can do an awful lot with your computer.
- rdl 11y agoYeah, but they've been getting better over time. It's monotonically non-decreasing security, at least, and the desktop->mobile transition has been amazing from a security perspective. This is a step backward. The only question is how big is that step.
- deleted 11y ago[deleted]
- pjmlp 11y agoTraditional UNIX is no different. Without containers every p0wned process has full access to $HOME and can do everything the user is capable of. I really like that Apple and Microsoft are pushing for sandbox models in their OSes.
- lazaroclapp 11y agoIn all fairness, you don't run any modern UNIX server without giving each sensitive server its own user, which effectively sandboxes it (not quite the same as chroot/containers/VMs, but still). Of course, desktop UNIX/Linux tends to have many important processes running as the same user, but that falls under "Desktop OSes are generally pretty bad".
- rdl 11y agoEveryone sane runs sensitive systems "system high" now, where there's a machine dedicated per task. User/process/thread security in UNIX/POSIX/etc. is bullshit weak sauce, sadly. You can use VMs for some of that, but that's the limit on sharing (and that's if you trust your hypervisor to be a separation kernel thing; reasonable for many people. Not for others.) Docker/containers isn't enough. Users aren't enough. Processes aren't enough.
- zanny 11y agoYou can also use MAC and avoid container overhead. SELinux is the worst of the bunch because its a PITA to work with, while AppArmor profiles are pretty easy to write but its not particularly foolproof, Tomoyo has nobody developing good profiles for it, and we should all be running Grsec Kernels + PaX since its the best of all worlds but again nobody wants to put in the effort to develop all the profiles for all the programs we use, and learning modes are just unacceptable.
- pjmlp 11y agoThat is GNU/Linux specific, not UNIX. Of course there are things like HP-UX safes, Tru64 and Solaris trusted zones. None of them are POSIX. Besides the average user would not even know where to start.
- gopowerranger 11y ago>Without containers every p0wned process has full access to $HOME and can do everything the user is capable of. You presume such a thing can happen. You must be a Windows users with no Unix experience. Your comment gives you away. No experienced Unix user, even most beginners, would say such a thing.
- voltagex_ 11y agoIf I run a shell script under my user account, that shell script has full access to anything my account has access to, UNLESS I'm running SELinux or something like that.
- gopowerranger 11y agoAnd another Windows user who runs "p0wned" shell scripts on his system. Or believe everyone does this on a regular basis. "Just like Windows!"
- voltagex_ 11y agoSigh. Yes, I'll assume you're perfect and never run anything you didn't write yourself. Edit: Okay, think about it this way - if you're the perfect sysadmin who doesn't run anything bad, how do you go about protecting your non-so-perfect users? How do you protect the server you're tasked to maintain?
- pjmlp 11y agoJust go do a wget site | sh for me will you? Thanks. Afterwards we can discuss UNIX security models.