Seems to be Creative Solutions crap but from where did it land?
Anyone? I now have a hunch it came from HP?
Has Bitdefender TrafficLight extension already moved to one 100 % cloud support?
As I said earlier in another place here on the forums the Superfish, PrivDog, Komodia scandal is just the tip of an iceberg. It will take some time before trust will be re-established and it will take some time before the size of this scandal will be fully known. Where did the marketeering swindle begin and where will this manipulation end?
The user is slowly wakening up to this undesirable situation. All unreliable root certificates should be revoked and this should be a task for Microsoft to protect the very users of their OS against https certificate scam and manipulation by non-trusted third parties.
I found out by a simple Junkware Removal Tool scan, but how many of the users out there are still unaware victims?
Hi Polonus, just a question. Are you saying Bitdefender Trafficlight is breaking HTTPS certificate revocation in Firefox? In one of your links it seems to indicate that only the Bitdefender AV products are doing this. I use Trafficlight extension in Chrome, ran JRT and it picked up nothing. So would like your opinion, is it safe to run Trafficlight in Chrome? Thanks.
Not exactly sure where the Komodia comedy starts and ends and there are complicating factors.
Google Chrome might have seen this coming (just a far-fetched assumption on my part) so they stopped checking in their browser since 2012.
When we look at the certificate for ep-reverse.nimbus.bitdefender.net, we find “Certificate not valid for domain name”.
Secure HTTPS Connectivity
Secure Connection Successful
We were able to connect securely to your HTTPS server. This means that your HTTPS server is listening for and also responding to secure requests.
SHA-1 Certificate Expiring Before 1/1/2016
The certificate has a SHA-1 signature, but it expires before January 2016, and thus will not show any negative UI in Google Chrome. *
Name Mismatch
The server address which you provided does not match the server name on your SSL certificate. The server provided a certificate with a common name of nimbus.bitdefender.net.
Intermediates Not Installed
Your server is either providing no intermediates or does not have the Trustwave intermediates installed.
Extended Validation (EV) Not Installed
Your server is not providing an EV certificate to visitors when they visit your site. If you purchased an EV certificate then it is not installed on your server at this time.
Bitdefender TrafficLight via 148.251.76.152 seems supported by a secure protocol,
Bitdefender TrafficLight contact site certificate seems OK
Bitdefender TrafficLight checked here: https://certlogik.com/ssl-checker/
Has a weak key, but it is not on any blacklist, which is good.
ha1WithRSAEncryption (SHA-1 is being phased out)
Not listed; o (website: ep-reverse.nimbus.bitdefender.net is not listed in the certificate)
Issuer = CN = Thawte SSL CA,O = “Thawte, Inc.”,C = US
Validity: 9 Apr 2015, 11:59 p.m. check: http://svr-ov-aia.thawte.com/ThawteOV.cer
thawte Primairy Root CA Fingerprint D6:6A:92:1C:83:BF:A2:AE:6F:99:5B:44:E7:C2:AB:2A
N.B. A smaller SSL handshake means a faster connection.
Reducing the number & size of certificates in your chain, and reducing the size of the public key will reduce this.
This server is not vulnerable to the Heartbleed Bug.
Protocol Support
TLS 1.2, TLS 1.1, TLS 1.0, SSL 3.0
SSL 3.0 is an outdated protocol version with known vulnerabilities. This should be fixed.
SSL certificate
Common Name = -www.wdc1.vdc.bitdefender.net
Issuer = -www.wdc1.vdc.bitdefender.net
Serial Number = 2DD3
SHA1 Thumbprint = 7D24AD78188015088D7FDCD70E6C53BFE655D618
Key Length = 1024 bit
Signature algorithm = SHA1 + RSA (good)
Secure Renegotiation: Supported
This certificate does not use a vulnerable Debian key (this is good)
SSL Certificate has not been revoked
OCSP Staple: Not Enabled
OCSP Origin: Not Enabled
CRL Status: Not Enabled
SSL Certificate is expired.
The certificate was valid from 04/01/2012 through 04/01/2013.
Certificate Name matches -www.wdc1.vdc.bitdefender.net
Subject -www.wdc1.vdc.bitdefender.net
Valid from 01/Apr/2012 to 01/Apr/2013
Issuer -www.wdc1.vdc.bitdefender.net
SSL Certificate is not trusted
The certificate is not signed by a trusted authority (checking against Mozilla’s root store). If you bought the certificate from a trusted authority, you probably just need to install one or more Intermediate certificates. Contact your certificate provider for assistance doing this for your server platform.