“He who does not trust enough, Will not be trusted” ~ Lao Tzu Rememb er the little story we did a while back about the China Internet Network Information Centre (CNNIC) titled The Curious Case of the Google Certificate that Wasn’t. Well, it appears Mozilla » Continue Reading.
From deep in the heart of Texas (or rather it’s petroleum-blacked crust) it’s the Friday Security Roundup! SSL.com presents a quick trot through security issues that we’ve been following this week:
SSL.com is happy to provide a wide range of clients with state-of-the-art security SSL/TLS certificates and personal support. For our customers who need a large number of certificates (and would like significant discounts) we are happy to suggest the SSL.com Reseller Program.
SSL.com wants you to be able to manage your own security architecture whenever possible, and thus presents here a method for disabling a root certificate in Windows using Microsoft Management Console (or MMC). Note that you may need to run MMC with Administrator privileges to follow the instructions » Continue Reading.
Some users of Windows Server 2008 R2 may have noticed a problem with their certificates not being accepted by Android devices. This article will explain why this happens and what to do to fix it.
This article will show you how to set up Microsoft Exchange Server to use a Fully Qualified Domain Name (or FQDN). This may be required if your present network uses “internal names” – FQDNs will need to be introduced to replace or reassign these internal names » Continue Reading.
How to Stay Safe When Using Free WiFi at Starbucks Yes, having a nice cup of coffee at Starbucks while checking your email, Facebook or another website is nice, but are you really safe when using free WiFi in a coffee shop or other public » Continue Reading.
Remember the big celebrity photo hack in the summer of 2014? You may think it has nothing to do with you because you’re not a celebrity (or you don’t take racy photos of yourself) – but you might want to think again. The incident happened » Continue Reading.
We recently received a query from an SSL.com customer with an existing wildcard certificate: “We have a wildcard with you – *.mydomain.com. I need to use https://www.subdomain.mydomain.com or *.*.mydomain.com. Is there a way to do this? Do I have to purchase another wildcard?”
Proper functioning of a server certificate depends on the successful installation of intermediate and root certificates. The complete SSL.com certificate chain typically includes four files: Certificate Files Description AddTrustExternalCARoot.crt Root Certificate USERTrustRSAAddTrustCA.crt Intermediate Certificate 1 SSLcomDVCA_2.crt Intermediate Certificate 2 your_domain_here.crt Signed Server Certificate Sign » Continue Reading.