+1-888-690-2424
  • 2015 – Looking Back, Moving Forward

    This post was originally published on the CA Security Council blog. Looking Back at 2014 End of 1024-bit Security In 2014, the SSL industry moved to issuing a minimum security of 2048-bit RSA certificates. Keys smaller than 2048 are no longer allowed in server certificates. In addition, Microsoft and Mozilla started to remove 1024-bit roots from their certificate stores. Hopefully, the

        in SSL, SSL Deployment
    0
  • SSL Review: December 2014

    Part of 11 in the Series — SSL Review
    Entrust’s monthly SSL review covers SSL discussions — recaps news, trends and opinions from the industry. Entrust and CA Security Council Entrust Identity ON discussed: Moving Forward with Certificate Transparency CA Security Council discussed: POODLE for TLS Hot Topics & Opinions POODLE and POODLE II for TLS … Common Vulnerabilities and Exposures CVE-2014-8730 Adam Langley announces “The POODLE Bites Again”

        in SSL
    0
  • Moving Forward with Certificate Transparency

    As we move in 2015, you will start to see Certificate Transparency deployed on EV SSL certificates. Google has required that as of January 2015, all EV SSL certificates be publicly logged to retain their EV status. All current EV SSL certificates will be white listed for the Chrome browser. Google Chrome will be the only browser supporting Certificate Transparency.

        in EV SSL, SSL, SSL Deployment
    0
  • POODLE for TLS

    Part 3 of 3 in the Series — Poodle
    The POODLE attack on SSL 3.0 has now been extended to some implementations of TLS. POODLE for TLS can be tracked through CVE-2014-8730. Adam Langley states that “TLS’s padding is a subset of SSLv3’s padding so, technically, you could use an SSLv3 decoding function with TLS and it would still work fine. It wouldn’t check the padding bytes but that wouldn’t cause

        in Alerts, SSL
    0
  • Moving Forward with Certificate Transparency

    As we move in 2015, you will start to see Certificate Transparency deployed on EV SSL certificates. Google has required that as of January 2015, all EV SSL certificates be publicly logged to retain their EV status. All current EV SSL certificates will be white listed for the Chrome browser. Google Chrome will be the only browser supporting Certificate Transparency.

        in EV SSL, SSL, SSL Deployment
    0
  • POODLE for TLS

    Part 3 of 3 in the Series — Poodle
    The POODLE attack on SSL 3.0 has now been extended to some implementations of TLS. POODLE for TLS can be tracked through CVE-2014-8730. Adam Langley states that “TLS’s padding is a subset of SSLv3’s padding so, technically, you could use an SSLv3 decoding function with TLS and it would still work fine. It wouldn’t check the padding bytes but that wouldn’t cause

        in Alerts, SSL
    0
Page 1 of 43123...5101520...»»