+1-888-690-2424
  • What Happened with Live.fi?

    Comodo issued an SSL certificate for live.fi. The issue is the certificate requester did not own or control the live.fi domain, which is owned by Microsoft. Was this Comodo’s fault? Let’s discuss. Since 2012, the certification authorities (CAs) which issue public trust SSL certificates must follow the domain verification methods in the CA/Browser Forum Baseline Requirements (BRs). The BRs provide

        in SSL
    0
  • 20 Years of PKI and Secure Transactions

    Part 1 of 6 in the Series — The Evolution of Public Key Infrastructure
    Almost 20 years ago, the first publicly trusted certification authorities (CAs) began generating their root keys and root certificates, which represented the public trust of the first Internet root CAs. Slowly, these root certificates were provided to operating system and browser vendors to be embedded in their software. Embedding indicated that the software vendor trusted the CA to issue publicly

        in PKI, SSL
    0
  • 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
  • Private Trust and Proxies

    With the news of Superfish, Komodia and PrivDog , there has been some interesting discussion on private trust and HTTPS proxies. Private Trust By private trust, I mean the use of private certification authorities (CAs). On the Internet, we use public trust CAs. These CAs are created in accordance with browser certificate policies, are highly secured and are audited on

        in Alerts, PKI, SSL
    0
  • 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
  • Private Trust and Proxies

    With the news of Superfish, Komodia and PrivDog , there has been some interesting discussion on private trust and HTTPS proxies. Private Trust By private trust, I mean the use of private certification authorities (CAs). On the Internet, we use public trust CAs. These CAs are created in accordance with browser certificate policies, are highly secured and are audited on

        in Alerts, PKI, SSL
    0
Page 2 of 44123...5101520...»»