• Why We Need to Move to SHA-2

    Part 5 of 9 in the Series — SHA-2 Migration
    Previously, we advised that the SSL industry must move to the SHA-2 hashing algorithm for certificate signatures. We thought it would be helpful to provide the reasoning behind the position. In the context of SSL, the purpose of a hashing algorithm is to reduce a message (e.g., a certificate) to a reasonable size for use with a digital signature algorithm.

        in Public Key Infrastructure, SSL, SSL Deployment
  • SHA-1 Deprecation, On to SHA-2

    Part 6 of 9 in the Series — SHA-2 Migration
    We have previously reviewed implementation of SHA-2, but with Bruce Schneier stating the need to migrate away from SHA-1 and the SHA-1 deprecation policy from Microsoft, the industry must start to make some progress in 2014. Web server administrators will have to make plans to move from SSL and code signing certificates signed with the SHA-1 hashing algorithm to certificates

        in SSL, SSL Deployment
  • SHA-3

    On October 2, 2012, the National Institute of Standards and Technology (NIST) announced that the winner of the new SHA-3 hash function competition was Keccak. The plan is SHA-3 will eventually replace SHA-1 and the SHA-2 hash families. To support digital certificates, the hashing function is used by the certification authority (CA) to put its signature on the certificates and

        in Secure Browsing, SSL, Technical