![]() I've tested it here on Windows 7 圆4 and XP 32bit right now and it is working properly, so I suspect the testing tools are not simulating malware accurately.Ĭontrol keys like capslock, backspace, shift, etc. There is a considerable amount of logic in place to allow legitimate screen capturing but block malicious use of screen data. I suggest not configuring system applications like explorer.exe as protected applications - it will definitely cause odd system behavior as it will prevent other components of the system from communicating with Explorer. I'm thinking that perhaps it is Norton interfering? I know Webroot plays nice, but that doesn't mean Norton isn't being a butt-head □. ![]() As for the screen capture, what's interesting about that is that I tested it again last night, and for the most part, most screenshots were blocked, but after a reboot, all my Webroot settings were defaulted (not really related to the original topic but thought I should mention it) and the program was again able to grab screenshots, even though Webroot said in its Identity Protection settings that the file was set to "block". So, most of the password (that is not a real password by the way :P) was blocked, if it was whitelisted wouldn't it have picked up everything? I could be wrong though, please correct me if I am □. Interestingly though, Webroot did block the screenshots in one test case installation, but not in any of the others using the same program.Īs far as I know, it is not a "remote keylogger", meaning that it won't actually send my keystrokes off like a real piece of spyware, its more like a "spy tool" that you would put on your computer to see what people are doing on your own computer, but, it is not one of the reputable ones like "Net Nanny", it is one of those kind of shady ones that's like "free see what people are typing" if you know what I mean, so I don't think it's whitelisted either, for that reason and because I would type something like "StarTrek_DaxFan-1985" and the keylogger would pick up "S _ n 1 8". Webroot allowed the screenshots even though it was an unknown file, and I verified that the padlock was on the Webroot icon in testing this as well. I had it set to grab a screenshot every 60 seconds, also running silently in the background. As for the screencapture, I was using an "Unknown" file, and I verified it was unknown by using Webroot's system control. No, that is not enough for a keylogger user to be able to actually get any useful information, but I thought I should mention it. That's what I mean about most but not all being blocked. All of those are keystrokes that I actually typed so I know it wasn't just my real keystrokes being scrambled. To be a little more specific about not all keystrokes being blocked, I mean I would go to my email (I have an address I use for testing) or Facebook and type in login information, and when I reviewed the keystroke log it would look like this "f E dax h. I made sure that they lock icon was over the Webroot icon as I was typing and it was the whole time. I am using a keylogger that runs in the background, not the foreground. Webroot® Legacy Products (2011 and Prior) 33.Webroot® SecureAnywhere™ - Antivirus for PC Gamers 553.Webroot® Security Awareness Training 55.Webroot® Business Endpoint Protection 1130.Webroot Mobile Security for Android 938. ![]() Webroot® Consumer/Business - for Macs 370.Webroot® SecureAnywhere™ - Complete 3826.Webroot® SecureAnywhere™ - Internet Security Plus 2468.Webroot® SecureAnywhere™ - Antivirus 6973.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |