Jump to content

mr_stealth

Members
  • Posts

    4
  • Joined

  • Last visited

About mr_stealth

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Not Telling
  • Location
    USA
  1. Thanks for the info, and nice job on the quick fix. Good to know it's just a FP. I've already stopped seeing the alerts for the pages that were showing it.
  2. I just started seeing this on quite a few pages, many being rather big sites like GreenManGaming.com, HumbleBundle.com, and Asus.com. It seems to be happening on a lot of sites with Facebook follow/like links on them. The Eset alerts actually stopped when I enabled the "Anti-Thirdparty social" filter list in uBlock Origin adblocker, which also points to the social links on these sites being the source of the detected malware. Looking up a couple of the IP addresses listed in the Eset log shows that they are indeed owned by Facebook. If anything is compromised, it seems that it's likely Facebook itself. I'd definitely like to know if that's the case, or if it's just a false positive.
  3. I managed to fix the issue I was having with SSL filtering. Though, I decided to keep the feature disabled anyway due to the general security concerns with SSL inspection. Even while the SSL filter was disabled, the Eset SSL Filter CA was still added to the Windows TRCA store. Removing it myself via certmgr.msc (while having the feature SSL filter disabled) allowed Eset to properly add or remove the CA. It now gets removed when the filter is disabled, and re-added any time the filter is toggled back on. And the filter works properly while enabled. I believe this likely happened as part of the update to Windows 10 1151/Threshold 2, because the update process involves automatically removing and reinstalling Eset while retaining settings. I had removed Eset prior to my 7-to-10 upgrade, but wasn't aware that the 1151/TH2 update behaved the same way until after I had installed it. Microsoft's removal process seems to not fully remove Eset, causing the CA to break, while also preventing Eset from replacing/removing it. The PC was stuck with the 'old' Eset CA from the previous install.
  4. SSL filtering is completely non-functional for me right now. Fairly sure this started after updating to Windows 10 1511. Chrome still has the Eset root certificate, and I have tried disabling/enabling SSL, as well as unchecking/rechecking the option to add the cert to all browsers. I've even done a complete reinstall of Eset 9. Everything else in Eset seems to be working. And I can confirm that protocol filtering does work for HTTP, just not HTTPS. I've also been unable to get the Eset cert added to Firefox on 3 separate PCs. This has been an ongoing issue since I moved to Eset in fall 2014. Happens with Windows Vista, 7, and 10. It has persisted through uninstalls and complete resets/profile deletions in Firefox. It's never been a real problem, as I rarely use Firefox. But I do keep the Eset option add the root cert to browsers unchecked to prevent it from throwing up an error message at every reboot.
×
×
  • Create New...