Google's new web browser, Chrome, has sparked a lot of discussion and interest in many of its new features. Though still in beta, it handles many things much better than all other current browsers. But how does it handle SSL certificates? Does it give the appropriate error messages and user interface notifications? That is what we are going to investigate.
There has been plenty of debate lately about how Firefox handles self-signed SSL Certificates. Instead of just whining about it, some researchers at Carnegie Mellon have released a Firefox extension that changes how it handles SSL Certificates.
Tired of reading? Learn more about SSL and the Extended Validation SSL certificates using one of these seminars or podcasts.
Tim Callan from VeriSign has posted about several fallacies that he encounters when discussing EV SSL Certificates.
Google recently enabled a feature that allows all traffic (including session cookies) to be transmitted securely.
Though it has been talked about many times before, several sites, including Slashdot, continue to discuss whether Firefox 3 handles invalid SSL certificates in the right way.
The Google Security Team has developed and released an open source cryptographic toolkit that makes it easier and safer for developers to use cryptography in their applications.
VeriSign has posted about a statistic that means good news for EV certificates and consumers in general: Over 50% of browsers can now use EV SSL Certificates
Johnathan Nightingale, a user interface developer for Firefox, has responded to the criticisms of the way that self-signed certificates are handled in Firefox 3.
The recent news about a DNS flaw discovered by Dan Kaminsky has been highly publicized and the details of the flaw have even been released. How does this new flaw open up phishing attacks using Domain Validated SSL Certificates?