Talk:Intermediate certificate authority

"...may not be implicitly trusted by most web browsers."
I call shenanigans. The cheap $15-20 intermediate/"chained" certs achieve "making the lock show up" which is what most small-time webmasters researching the issue *want*. And 95+% of browsers will do just that.
 * &mdash;67.88.123.2 (talk) 16:51, 8 July 2008 (UTC)

"...Summary: 1. a private key is generated on the big-ip and kept in the filestore (will be used later in your clientssl profile as 'key')"
While this summary is useful in explaining the process anyone can go through to create a certificate, in this case, I feel it is far too specific to a particular product by a company f5 called a "BIG-IP" I believe this article would benefit from having the summary explained in more generic terms, however I did not want to just start editing out the article without first having some discussion on the subject. --Guyonphone (talk) 07:22, 6 January 2015 (UTC)


 * agreed, appears to have been copy-pasted from: https://devcentral.f5.com/questions/difference-between-root-cert-intermediate-cert-and-ssl-cert Jm3 (talk) 22:34, 31 August 2015 (UTC)


 * agreed, more generic terms would be appreciated for anyone not using F5s. Rsaxvc (talk) 23:20, 13 November 2015 (UTC)

Article title
Should this be moved to the singular title Intermediate certificate authority? --SoledadKabocha (talk) 02:58, 18 December 2013 (UTC)

Security Reasons for Intermediate CAs
GlobalSign has a good overview of why CAs use intermediate certificate authorities at https://support.globalsign.com/customer/portal/articles/1217450-overview---intermediate-certificates — Preceding unsigned comment added by Shaunco (talk • contribs) 21:01, 13 October 2015 (UTC)