3 ms·
>decades ago we had time sharing systems where rarely or never did the work of one user cause security problems for another user. How much of that was due to p
by DuskStar 9y ago
>decades ago we had time sharing systems where rarely or never did the work of one user cause security problems for another user.
How much of that was due to people not trying to cause those problems, though?
- graycat 9y agoWell, they wrote and ran a lot of software with outrageous bugs, especially writing out of array bounds. But likely a biggie difference is that the attack surface was smaller. Also it may be that some of what Microsoft is still struggling with is being able still to have Windows run old software that thinks it's just fine to read files from nearly anywhere, write lots of files it should have no business writing, run other programs, etc. E.g., on Windows, I can download and install software, e.g., a new version of Firefox. That writes to my boot drive. What the heck security door did that software pass through? I'd like to know the details of Windows security, but so far I've never seen any good descriptions or documentation. I'm interested in Windows security because Windows is the source of the computing for my startup. Otherwise, and in general, I hope that Microsoft gets the security problems fixed.