I just ran SpyShelter’s test http://www.spyshelter.com/download/AntiTest.zip and it was able to take screenshots. Privatefirewall for example warns me and allows me to block the screen capture, but CIS allows it even with HIPS set to Paranoid and the application partially sandboxed as Untrusted.
I wasn’t able to test the application in the background (I read somewhere that CIS blocks screen capture only if they are requested by background apps), but I think allowing screen capture for any foreground application is a security concern.
I have the BB set to Restricted and it blocked all of the attempts. I then disabled BB, removed Antitest from the Unrecognised Files list and ran with D+ in Safe Mode. It blocked all screen capture attempts.
Ok, I just did some additional tests and the results are… well, see for yourself:
BB enabled as Untrusted + HIPS enabled in Safe Mode —> screen successfully captured
BB enabled as Untrusted without HIPS —> screen successfully captured
BB enabled as Restricted without HIPS —> screen capture failed
BB disabled + HIPS Safe Mode —> screen capture failed (HIPS warned and allowed me to block it)
So I don’t know what is happening, if more people could reproduce this test to see if it’s my installation or a generalised bug, please do! Shouldn’t Untrusted be more strict than Restricted? For the moment, I’m disabling the BB and sticking to HIPS only.
I forgot to tell that I am running Proactive Security Configuration. If you are running in Internet Security please try again in Proactive.
May be your configuration got corrupted somehow. Try importing a factory default configuration from the CIS installation folder. When importing give it an applicable name like CIS - Proactive Security Test Profile. Let us know if that makes a difference.
I wasn’t running Proactive Security config, but a heavily tuned Internet Security. Anyway, enabled Proactive, same results. Restricted BB blocks screen captures but Untrusted BB doesn’t.
Tried importing Proactive from the installation folder as you said, same results again.
hey people and can you block the keylogging? i am having this problem since i first time installed comodo (4-5 years or more) it can’t block keyloggers
no meter what i do when i test REFOG keylogger (or few others) and when i am blocking access to keystrokes it can log it anyway
wanted to report that but i am too lazy to do all that stuff
I did a quick search on the forum, and for what it’s worth, it looks like the issue with this test is nothing new. A poster back in 2010 said that on “limited” and “restricted” CIS passed, but not on “untrusted,” so the results were not consistent. Three years later, here we are…
Jaspion. Could you file a bug report about this in the bug report section? Please follow the reporting protocol closely. That way you’ll be sure the bug gets seen by Comodo staff.