View Single Post
chas_m

 
chas_m's Avatar
 
Member Since: Jan 22, 2010
Location: Victoria, BC
Posts: 17,048
chas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond reputechas_m has a reputation beyond repute
Mac Specs: 2012 MBP, Black speakers, Black Benq second monitor, black(ish) iPhone 5s, Black 2012 iPad, etc.

chas_m is offline
Sandboxing is, as you say, a basic level of protection -- both from unstable apps causing system crashes and from malware trying to extend its reach. But sandboxing shouldn't be mistaken from the kind of protection setting it to "only allow installs of apps from the Mac App Store or signed Apple developers" does.

Updates will quickly change the number of apps you have that honor the sandboxing thing over the next [couple of] year or so. Developers don't really have much choice in the matter. Most people will leave the security settings on their default or the middle choice.

PS. I don't know what version of Safari you're using, but yes it is sandboxed. The *application* will read "no," but Safari Web Content (the WebKit engine) will read "yes."
QUOTE Thanks