The main practical difference is trusting all browsers and third-party systems, such as Android, iOS, or Windows.
Allows you to encrypt this restriction and suggested a solution that you can read on your website https://letsencrypt.org/certificates/
Our intermediate element is signed by ISRG Root X1
. However, since we are a very new certification authority, ISRG Root X1
is not yet trusted by most browsers . In order to gain trust immediately, our intermediate segment is also cross-signed by another certification authority, IdenTrust
, whose root directory is already trusted in all major browsers . In particular, IdenTrust has cross-signed our middleware using its DST Root CA X3.
In fact, their certificates are signed by a trusted "regular" CA. Therefore, in practice there is no difference
Take a look at letencrypt's own web certificate, it is signed by DST Root CA X3
(IdenTrust)
I checked if the CA is present in some kind of keystore:
- Chrome, IExplorer, Edge (using windows 10): OK
- Mozilla Firefox: OK
- Android (Nexus 5x -android 7): OK
Full list here: https://letsencrypt.org/docs/certificate-compatibility/
source share