Elise

I think it was just an example used here. Law enforcement won't typically want to investigate any computer without there being a reasonable suspicion of something illegal going on.

Yes, I was referring to the content of the file, not any database file obviously. Logging itself is not bad, logging private information is another thing.

Your computer is full with more or less personal data, if it's searched by law enforcement they'll be able to find personal data no matter what. The article talks about Avast that leaves an easily readable file containing browser data. This is not the same as having system logs that show when the AV was updated, what files or urls were blocked and such. In other words, no matter if you use incognito mode or browse normally, the only URL or files showing up in our logging database are those that are detected. It is impossible to use that database to track your browsing history.

That file is not used nor collected by us, for that reason this simply doesn't apply.

If you're not sure, you can always call to your internet provider (using the phone number on their website) and explain what happens. Usually they'll be able to confirm/deny that the call was from them.

No it can't because we don't collect that information. To read more about this: https://blog.emsisoft.com/en/26117/https-interception-what-emsisoft-customers-need-to-know/

Hallo Henry, Dit klopt, er was een probleem bekend wat met deze versie opgelost zou moeten zijn. Goed om te horen dat dit inderdaad het geval is.

Hallo Henry, Wat vervelend om dat te horen. Welke instellingen worden gebruikt voor de aangepaste scan en in welke scan fase blijft deze hangen (bijvoorbeeld: Scanning (3 of 4) Rootkits)? Gebeurt dit met de stabiele of beta versie van EAM? Als het eerste het geval is, ga dan naar Settings > Updates en switch naar beta updates. Dit zou het probleem op moeten lossen.

Hello, Emsisoft Emergency Kit is already portable. All you have to do is to copy the EEK folder to the USB drive and run it from there.

Yes, you are right. I checked them all, but (fortunately) none of the content reported did work (although I could see it had been there before).

Hello, We do block techsupport scams, however we do not use heuristics detection to do this as some other products do. The reason for this difference is that doing so would require us to actively filter/check all your browser activity. Not only is this a breach of your online privacy, it also brings security risks with it, which is why we opted not to do this. While I completely understand how annoying/scary such fake techsupport scams can be, they are harmless to your computer; the worst that can happen is that you have to close the browser via the taskmanager (you can do it also via Emsisoft's Protection/Behavior Blocker tab). I will check the data you provided and will add any undetected techsupport scams to our database.

Theoretically that is possible yes, but then something would need to be installed on disk. And that would count as suspicious behavior.

The hijacking aside, you need to have traffic back to the attacker, which would be detected in any case. And unless someone tricks you in installing something to capture your camera input to send it their way (which would be a legitimate program, which you clearly have to install manually and configure) the attack itself would be intercepted as well. Larger files may always not be scanned by the file guard, but they are monitored by the behavior blocker, so that is not an issue.

Hello, Thank you for contacting us about this issue. Please feel free to forward the email to [email protected] Most likely this is a malicious email. As for your questions: 1: Yes, you would be protected from that by EAM. 2: No, realtime protection would have blocked it, either via the file guard or behavior blocker. However you can always run a scan to doublecheck. 3: Yes. 4: No, you can just trash the mail or forward it to us (and then trash it).

Based on the file name I think this was a temporary installation file. It triggered an alert and EAM attempted to quarantine, but before this was completed the file was already gone, hence no actual file in quarantine.