Re:What a one line change did to the Chrome sandbox
by toyg on Thursday April 23, 2020 @06:46AM
(#22954560)
Nah. It would have just taken longer to fix, imho.
[ Parent
| on HN ]
Re:What a one line change did to the Chrome sandbox
by buckminster on Thursday April 23, 2020 @08:41AM
(#22955289)
This. Twenty years ago, if you reported a bug to MS and they agreed it was a bug and they agreed to fix it then you might actually have working code in three years time when the next version of Windows was released. Five years after that all of your customers might have upgraded to this new version of Windows. And then you could rely on the fix.
Important customers could get a hotfix. For anyone else reporting bugs was pointless.
Re:What a one line change did to the Chrome sandbox
by ChrisSD on Thursday April 23, 2020 @09:04AM
(#22955455)
In its consumer operating systems, MS used to not consider it a bug for a process to exploit other processes on the same machine. After all, why would you be running untrusted code?
I'd also add that Microsoft used to be notoriously bad at security, such that even Mac owners would make fun of them. We're still dealing with the design decisions made during that era. It's only since XP SP1 that security was taken more seriously and it wasn't until Vista that they truly started to grapple with the whole mess from the ground up.
Re:What a one line change did to the Chrome sandbox
by ocdtrekkie on Thursday April 23, 2020 @09:27AM
(#22955673)
> even Mac owners would make fun of them
Although, in reality, Mac owners really only were secure by way of being too few and far between to bother writing malware for.
Just this past year, Apple essentially implemented UAC into OS X.
Re:What a one line change did to the Chrome sandbox
by jamesgeck0 on Thursday April 23, 2020 @02:06PM
(#22958943)
Hasn't Mac software run with non-admin user permissions by default since the first version of OS X?