Not the answer you're looking for? I suspect that your hosting provider might have multiple web servers on the back-end behind a load-balancing appliance, and the updated certificate might only be installed on one of those servers, while the old certificate. As soon as I installed the new version of the avast! I did look to see if there was anything in avast I could push. After thirty minutes had been spent, I finally started to go through the avast! Mail Shield, it is necessary that encryption is turned off in the mail client software. I recommend you to turn this off if you value internet privacy. There are a few enteries where host name is just an ip address.
If nothing else there should be clear documentation which tells users how to move system specific certificates to the firefox keystore. The benefit of having your email scanned probably outweighs the risk of your loopback traffic being sniffed. The hosting provider is responsible for replacing or removing one of them the expired one, I suppose? I can request them any important information. I even installed Chrome fresh just to be sure. From a general security standpoint, assuming Avast's proxy is well implemented you should be fine going with that. At least the Avast is not blocking the access so far and the ssllabs test is now showing only one valid certificate. If you protecting from the machine being infected well if my keystore is corrupt its to late anyway.
The Avast anti-virus application can scan both incoming and outgoing emails to help prevent your computer from receiving or sending malware. The implementation is certainly lacking. Hi everyone, I am the owner of the following website and I am facing a problem: every time when I access my website from a pc running Avast program, it shows up an alarm and blocks access to my website due to certificate has been revoked. Safari and Chrome both had no issue using the Avast certificate. Again this seems to be a issue with firefox and how it looks up certificates. If they are going to replace the certificate they should be validating the original certificate.
I would like to thank you and for your help. See the mail shield server settings within Avast! Any idea how I can figure out if they belong there or not? The top drop-down menu is the type of security encryption that is used for connecting to the Post Office Protocol 3 server that handles incoming emails, while the bottom one is the encryption protocol used by the Simple Mail Transfer Protocol server that relays outgoing messages. You can close the ticket. Hi , Thank you very much for your quick reply. I had the same issues installing the lastest firefox 43. But I also don't agree its implementation should be platform agnostic.
The second method is much easier and you do not have to make changes in different applications individually. I am monitoring the ssllabs test for a while and before the certificate expiration, the ssllabs test already showed theses two certificates as valid. I was lucky to be able to change the configuration form past experience with companies. When you authenticate with a mail server, that authentication information is sent when the connection is established. Whether this behavior presents additional security issues is debatable but I don't think it's something you need to be deeply concerned about - after all, your own antivirus software is doing the man-in-the-middling, not a malicious party.
System is the recommended location for installing custom certificates. I don't agree putting this burden on the user is useful. When you set up Avast! I am using Outlook 2010 and Avast anti-virus 7. I had switched recently because of all the annoying things chrome has been doing lately with plugin support. . It comes down to a risk-based evaluation.
Would you like to answer one of these instead? Firefox does not see them though it only appears to see certificates in the SystemRoot group. I will keep monitoring this scenery for more few days. I had the same issues installing the lastest firefox 43. Easier does not mean right. Overall I do like the browser, so that would be a shame. Some accounts I had added I needed to try to send a few test e-mails before I got things working and I think Avast created rules for each of the wrong settings so there's a lot of crap.
Any strange behavior, I will post here again. Your fix did the trick. And from a user perspective the 98% case would not even know it was doing it unless they hit a problem. I guess this is pretty unusual, right. This may allow an attacker to impersonate you and send email on your behalf.
If you use Avast's proxy, you must implicitly trust the local system actually, you must do this anyway. Firefox was acting buggy so I did a clean install and thats when the problem started. If I keep hitting these types of issues though I will probably move back to chrome. I appreciate any help you guys can give me. Why is one of them as not trusted? I have read several support articles about avast not working with firefox. They are legitimate in every way.