Re:What Spectre and Meltdown Mean for WebKit
by EgoIncarnate on Tuesday January 09, 2018 @04:17AM
(#16104703)
Would you consider yourself a typical example of a naive user? The security default needs to work for everyone. I think the sandbox approach is better than expecting everyone to correctly decide when it is or isn't okay to allow a site to run code.
Re:What Spectre and Meltdown Mean for WebKit
by pjmlp on Tuesday January 09, 2018 @05:10AM
(#16104936)
Yes in the context of iOS, Android and UWP native apps.
Re:What Spectre and Meltdown Mean for WebKit
by EgoIncarnate on Tuesday January 09, 2018 @06:07AM
(#16105186)
You must run in much better circles than I do. Nevermind a naive user, the average users I know wouldn't know how to disable javascript, or whitelist sites, or that there even were sandbox settings in the OS.
Some of the older people I know can't even correctly choose between between writing a text message, and a facebook post.
If you think you are a typical example of a naive user, I would hate to see what you expect of the average user.
Re:What Spectre and Meltdown Mean for WebKit
by pjmlp on Tuesday January 09, 2018 @06:42AM
(#16105369)
You completely misunderstood me.
iOS, Android and UWP sandboxes for native apps are always enabled, there isn't any configuration for naive user available.
You just allow or not the access to specific actions and that's it.
On UWP you cannot even access files directly, the user has to select them for your application.
You can only change the way sandboxes behave via developer settings, but that is only in the context of debugging, which naive users will never do anyway.
On the OSes I use, I make sure all sandbox options are turned on.