News for hackers. Stuff that matters.
Re:What a one line change did to the Chrome sandbox by mehrdadn on Thursday April 23, 2020 @06:41AM (#22954537)
Does anyone else feel like if Windows was still a classic OS instead of "as a service" then these types of changes would have a chance to get more scrutiny during development and hopefully get caught?
Re:What a one line change did to the Chrome sandbox by hedora on Thursday April 23, 2020 @10:52AM (#22956666)
Since they supported multiple versions at once, important bugfixes were backported, but risky new features were not. For a year or so after each release, the previous release was more stable. This let the customer choose between security/stability and new features.

I think it’s a great model, but it breaks down when the new version is a feature/usability regression vs the old version.

Once that started happening more often than not, the “aas” models came out, where the vendors started force upgrading users instead of trying to compete with version N-1.

This is worse for the users, but better for deadline-focused middle management, so it’s become incredibly popular.

Re:What a one line change did to the Chrome sandbox by SahAssar on Thursday April 23, 2020 @07:05AM (#22954676)
Are you saying that these sort of changes were never part of a patch or service-pack before Win10?
Re:What a one line change did to the Chrome sandbox by mehrdadn on Thursday April 23, 2020 @07:24AM (#22954797)
Do you think it's sensible for me to make such a claim?
Re:What a one line change did to the Chrome sandbox by SahAssar on Thursday April 23, 2020 @02:16PM (#22959090)
No, but that's what it sounded like you were doing.
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.
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?