Jump to content

dbergst

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by dbergst

  1. 3 hours ago, timse201 said:

    Got the same issue.

    I restarted into safe mode. After that I deleted the entire folder "OPP" which was located under C:\ProgramData\ESET\ESET Security. In this folder you can find your Firefox profile that eset will use for banking protection. The profile will be recreated if banking protection is restarted.

     

    You cant delete this folder when you are logged in normaly. But I didnt test to delete the profile via about:profiles because the profile that it shows seems like my normal firefox profile. the path to profile did not match with esets path. But about:support shows the correct path. Would be nice if eset could make an button in settings to delete this profile or to clean it automatically sometimes.

    This worked for me.

  2. I just started running Thunderbird version 60 and ran into problems with sending and receiving emails.  Initially I reported these issues with the Thunderbird team but it was soon discovered that the problem might be antivirus or firewall related.  Sure enough, I tried disabling the IMAPS Scanner Setup in EIS and the email client started behaving correctly.  Any thoughts on what I can do to re-enable the IMAPS scanner?

  3. What get's interesting also is the fact that a bogus certificate for search.dnsadvantage.com was showing up at my end.   I traced this issue to the DNS settings on my router which were customized recently.  When I went back to the standard DNS servers my ISP (Verizon) uses, the certificate injections stopped and the web pages loaded normally.

    In regard to the site certificate for community.kde.org, that is a separate matter that should be addressed by the site owner.

  4. 1 minute ago, itman said:

    I can reach that domain in IE11 w/o any certificate errors. Might be a FireFox problem since they use their own certificates.

    Note this web site only uses TLS 1.2 with no downgrade capability.

    Thanks, itman.  I noticed the problem seemed to be resolved after retrying the site and subdomain.  Just to be sure I cleared out my browser cache in case the wrong certificate was still there.

  5. I have been following the procedures in the article posted at https://support.eset.com/kb3126/ and am still running into difficulty with certain web site certificates.  What happens is the real certificate is being replaced by an invalid expired certificate from a different website.   If protocol filtering is disabled, this does not occur, and the correct site certificate is used.

    In case anyone wants to try the site in question, it is https://community.kde.org

    Below is a copy of the error message I have been seeing:

    community.kde.org uses an invalid security certificate. The certificate is only valid for search.dnsadvantage.com. The certificate expired on Monday, September 18, 2017, 12:03:45 AM. The current time is August 3, 2018, 11:24 PM. Error code: SSL_ERROR_BAD_CERT_DOMAIN

×
×
  • Create New...