mike acker
December 26th, 2012, 12:31 PM
I have for some time suspected that web sites would modify web browsers for their own purposes
this essay tends to confirm that, in spades Reference C/Net 2012-12-26 (http://reviews.cnet.com/8301-3514_7-57560757/chrome-prepares-to-ax-silent-extensions/)
worse, it seems they let the "extension" (un authorized program) install itself and then graciously "permit" the owner to "authorize" it -- or leave it suspended
to me program modifications should be blocked, period. otherwise it leaves us to ask: what all is our browser actually doing ? it executes using the logged on user's authority and thus has access to everything the logged on user has access to .
do we have any detailed information on what the Canonical supplied app armor for Firefox protects ?
this essay tends to confirm that, in spades Reference C/Net 2012-12-26 (http://reviews.cnet.com/8301-3514_7-57560757/chrome-prepares-to-ax-silent-extensions/)
worse, it seems they let the "extension" (un authorized program) install itself and then graciously "permit" the owner to "authorize" it -- or leave it suspended
to me program modifications should be blocked, period. otherwise it leaves us to ask: what all is our browser actually doing ? it executes using the logged on user's authority and thus has access to everything the logged on user has access to .
do we have any detailed information on what the Canonical supplied app armor for Firefox protects ?