rotate4all
-
Posts
6 -
Joined
-
Last visited
Posts posted by rotate4all
-
-
11 minutes ago, itman said:
Actually it does.
Well, tell that to someone who grew up learning all about Root CA certificates. It'll make perfect sense for them.
Whereas for we regular mortals speak plain ENGLISH and the phrase "MOZILLA DOES NOT RECOGNIZE THIS CERTIFICATE ISSUER" means just that, regarding what technical arguments you may have against it.
So I'm seeing this issue from layman's point of view, where my site's reputation is potentially being undermined by an antivirus software for no apparent reason.
In any case, we wouldn't be talking about these issues here if ESET would not replace our perfectly valid certificate with their own inside the user's browser.
-
Sorry but that's plain WRONG! And it's DISCRIMINATION to say the least. Why does it make a difference between two valid EV SSL certificates?
Additionally Firefox doesn't even recognize ESET's certificate:
So how do you think this affects my business and website's credibility? Makes me wonder why I paid the extra $$$ for an EV SSL certificate when an antivirus software comes along and decides UNILATERALLY which site is to be trusted and which isn't ?!
-
Hello,
Just noticed that my site's EV SSL certificate is being automatically replaced by ESET's certificate in all browsers for some unknown reason:
This is with ESET NOD32 antivirus using default settings.
However, for another site (which also uses an EV SSL certificate albeit issued by a different authority) interestingly ESET does NOT replace their certificate in any browser:
The only way that I could see the certificate actually installed on my site is through disabling ESET's default SSL/TLS filtering:
So why the discrimination? Very curious of ESET's arguments on this.
-
That doesn't seem to be the case as HTTP/2 works just fine on other websites with ESET SSL filtering enabled.
Here's just one example:
-
Hello,
I have noticed that for some reason ESET is downgrading my site's SSL connection from HTTP/2 to HTTP/1.1. I have found that I could prevent this behavior either by disabling HTTPS protocol checking altogether in the settings or by adding my site's SSL certificate to the list of Eset's known certificates and selecting the "Scan action -> ignore" setting.
Question is, why does ESET do this with my own website specifically? Other sites with HTTP/2 enabled do not get downgraded to HTTP/1.1 even with ESET default settings.
Could someone please shed some light on this matter?
My website is: https://www.rotate4all.com
I've attached a screenshot as well.
Thank you.
ESET replacing site EV SSL certificate with its own?!?
in ESET NOD32 Antivirus
Posted
Well you keep on laughing as it seems you clearly missed the point here.
My doubt here is why does ESET exclude some EV SSL secured sites from their SSL/TLS filtering system but not others/all? What are the criterias? In my opinion this is wrong and is discriminating because our EV SSL certificate is just as valid as any others'.