Posted by admin in scaesar.com
Hi
after updating op to version 3.0.557.5918 (437) i noticed that active buttons on several home pages are not shown with their actual picture and text but only as [EXT]. I see the full button in disabling blockage of active vontent in op, I dont recall having this experiance with previous version, all settings unchanged.
Is this a new feature ?
Should i permit "external active content" ?
(PS i have allowed "outpostfirewall.com", it solves the specific problem here, but i see it a lot of other places after the update too)
regards Nolan
It's rather too broad brush to be of much use, unless you want to be buried in exceptions for tons of sites.
In the case of this forum, it picks up on the image SRC not being specified relatively, even though it actually points to the same domain. To be honest, I don't use much more protection than prompting for activeX, since a lot of the other options are just so obstructive to normal use.
If it worked well it might be a good tool against things like this (report):
http://www.f-secure.com/weblog/archives/archive-012006.html#00000795
Though I'm not sure if it's effective against that kind of URL encoding.
after updating op to version 3.0.557.5918 (437) i noticed that active buttons on several home pages are not shown with their actual picture and text but only as [EXT]. I see the full button in disabling blockage of active vontent in op, I dont recall having this experiance with previous version, all settings unchanged.
Is this a new feature ?
Should i permit "external active content" ?
(PS i have allowed "outpostfirewall.com", it solves the specific problem here, but i see it a lot of other places after the update too)
regards Nolan
In the case of this forum, it picks up on the image SRC not being specified relatively, even though it actually points to the same domain. To be honest, I don't use much more protection than prompting for activeX, since a lot of the other options are just so obstructive to normal use.
If it worked well it might be a good tool against things like this (report):
http://www.f-secure.com/weblog/archives/archive-012006.html#00000795
Though I'm not sure if it's effective against that kind of URL encoding.
#If you have any other info about this subject , Please add it free.# |