Timeline for How long can X.509 certificate chains be?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 8:14 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Mar 11, 2016 at 23:24 | comment | added | Geremia | @Oasiscircle I did not know they did that. interesting | |
| Mar 11, 2016 at 23:24 | vote | accept | Geremia | ||
| Mar 11, 2016 at 18:37 | history | edited | Castaglia | CC BY-SA 3.0 |
More grammar fixes. Sigh.
|
| Mar 11, 2016 at 18:07 | history | edited | Castaglia | CC BY-SA 3.0 |
Fixed grammar.
|
| Mar 11, 2016 at 16:50 | comment | added | Thomas Pornin | Cross certification tends not to work well, because systems rebuild chains by following URL found in certificates (AIA extensions), so they won't do it for the cross CA unless the crossing was already in place when the certificates were emitted. Even so, some implementations (Microsoft...) will be content with the first URL for which a matching intermediate CA is found, and won't explore the other URL. | |
| Mar 11, 2016 at 16:48 | comment | added | sethmlarson | I'll note one significant instance of cross-certification that happened between LetsEncrypt X1 and IdenTrust DST X3 not too long ago to allow LetsEncrypt to appear in major browsers before it's actual root CA is deployed with browsers. | |
| Mar 11, 2016 at 16:40 | history | answered | Castaglia | CC BY-SA 3.0 |