mirror of
https://git.eworm.de/cgit/routeros-scripts
synced 2025-06-30 05:04:26 +02:00
d1693a241b
In the beginning of Let's Encrypt their root certificate ISRG Root X1 was not widely trusted, at least some older and/or mobile platforms were missing that certificate in their root certificate store. At that time Let's Encrypt was using an alternative chain of trust, where a certificate was cross-signed with DST Root CA X3. To make sure a valid chain of trust is available under all circumstances a set of all certificates had to be supplied: both root vertificates ISRG Root X1 & DST Root CA X3, and an intermediate certificate. This was still true after DST Root CA X3 expired, as it could still be used as a root anchor and was shipped by Let's Encrypt when requested. 🤪 This time is finally over, and we have a clean chain for trust ending in ISRG Root X1 (or ISRG Root X2). Well, actually it is the other way round... Let's Encrypt signs with different tantamount intermediate certificates. There is not only E5, but also E6 - and we can not know beforehand which one is used on renew. So let's jetzt drop the intermediate certificates now, and rely on root certificates only. We are perfectly fine with this these days. Follow-up commits will do the same for *all* certificates. The certificate is downloaded with: curl -d '["ISRG Root X2"]' https://mkcert.org/generate/ | grep -v '^$' > certs/ISRG-Root-X2.pem |
||
|---|---|---|
| .. | ||
| 01-download-certs.avif | ||
| 02-import-certs.avif | ||
| 03-check-certs.avif | ||
| 04-import-scripts.avif | ||
| 05-run-and-schedule-scripts.avif | ||
| 06-schedule-update.avif | ||
| 07-edit-global-config-overlay.avif | ||
| 08-apply-configuration.avif | ||
| 09-update-scripts.avif | ||
| 10-install-scripts.avif | ||
| 11-schedule-script.avif | ||
| 12-setup-lease-script.avif | ||
| 13-install-custom-script.avif | ||
| 14-remove-script.avif | ||
| hello-world.rsc | ||
| notification-news-and-changes.avif | ||
| telegram-group.avif | ||
| upstream.png | ||
