Comment by raw_anon_1111
Comment by raw_anon_1111 4 hours ago
Mac apps outside of the Mac App Store really doesn’t have any sandboxing.
And Android’s sandboxing is so bad, you always hear about the malware of the week especially outside of the Play Store.
ChromeOS also isn’t open source. And expecting end users to “configure sandboxes” you might as well not have one.
Firefox is s browser, and didn’t they tighten what third party extensions can run?
Android - or at least the version that most people use - is not “open source” by any stretch of the imagination.
> Mac apps outside of the Mac App Store really doesn’t have any sandboxing.
Apps can and do ship with sandboxing rules that will be applied at runtime.
> ChromeOS also isn’t open source. And expecting end users to “configure sandboxes” you might as well not have one.
I listed ChromeOS as one of four consumer operating systems used by billions of people that uses sandboxing, not as an open source OS.
Notice how I did use ChromiumOS when referring to open source software, along with Chromium.
> And expecting end users to “configure sandboxes” you might as well not have one.
Who said anything about expecting users to do that? I just mentioned that you could configure them if you wanted to, like I said in my GP.
Again, my point is that these are consumer products that billions of people use everyday that use sandboxing by default, yet somehow not even having to think about sandboxing is too onerous for end users?
> Firefox is s browser, and didn’t they tighten what third party extensions can run?
Yes, it is open source consumer software that does sandboxing by default without the user having to think about it.
> Android - or at least the version that most people use - is not “open source” by any stretch of the imagination.
AOSP is very much open source