+1-888-690-2424
  • SHA-1 Deprecation Update – Not Chrome 41, but Chrome 42

    Chrome 41 was released on March 3, 2015. You may have noticed, Chrome 41 did not have a change to treat certificate chains using SHA-1 valid past January 1, 2017 to be affirmatively insecure.       The affirmatively insecure representation will now occur in Chrome 42. We expect Chrome 42 to be released about April 14, 2015. We continue

        in SSL, SSL Deployment
    0
  • Is Your SSL Server Vulnerable to a FREAK Attack?

    FREAK is a new man-in-the-middle (MITM) vulnerability discovered by a group of cryptographers at INRIA, Microsoft Research and IMDEA . FREAK stands for “Factoring RSA-EXPORT Keys.” As for the “A”, it may be a stand for Apple or Android to be discussed below. The vulnerability dates back to the 1990s, when the US government banned selling crypto software overseas, unless it used

        in Alerts, SSL, SSL Deployment
    0
  • Superfish Joins the MITM Club

    In the past, we have seen inadvertent errors which gave parties the chance to perform a man-in-the-middle (MITM) attack in an SSL secure connection. There were cases with Trustwave, TURKTRUST and ANSSI. In January, Gogo joined the MITM group. With Gogo, they broke the SSL connection to limit the bandwidth on their airline Wi-Fi service. Gogo apologized, but never gave

        in Secure Browsing, SSL, SSL Deployment
    0
  • SSL and 39 Months

    Public trusted SSL uses 39 months for two purposes: certificate validity and information validation. These purposes are specified in the CA/Browser Forum Baseline Requirements. Certificate Validity As of April 1, 2015, certification authorities (CAs) will no longer be able to issue SSL certificates for a lifetime of longer than 39 months. In many cases, this means that your maximum will

        in SSL, SSL Deployment
    0
  • Superfish Joins the MITM Club

    In the past, we have seen inadvertent errors which gave parties the chance to perform a man-in-the-middle (MITM) attack in an SSL secure connection. There were cases with Trustwave, TURKTRUST and ANSSI. In January, Gogo joined the MITM group. With Gogo, they broke the SSL connection to limit the bandwidth on their airline Wi-Fi service. Gogo apologized, but never gave

        in Secure Browsing, SSL, SSL Deployment
    0
  • SSL and 39 Months

    Public trusted SSL uses 39 months for two purposes: certificate validity and information validation. These purposes are specified in the CA/Browser Forum Baseline Requirements. Certificate Validity As of April 1, 2015, certification authorities (CAs) will no longer be able to issue SSL certificates for a lifetime of longer than 39 months. In many cases, this means that your maximum will

        in SSL, SSL Deployment
    0
Page 1 of 26123...5101520...»»