From def7e9009c6ba1d41105cd6718a47bcc66ea4d43 Mon Sep 17 00:00:00 2001 From: Ming Di Leom <2809763-curben@users.noreply.gitlab.com> Date: Sat, 14 Feb 2026 05:51:37 +0000 Subject: [PATCH] micropost: 14 February 2026 --- source/_posts/2026-02-14.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 source/_posts/2026-02-14.md diff --git a/source/_posts/2026-02-14.md b/source/_posts/2026-02-14.md new file mode 100644 index 0000000..7ff0b97 --- /dev/null +++ b/source/_posts/2026-02-14.md @@ -0,0 +1,10 @@ +--- +title: Importing intermediate certificate into Chromium/Cromite +date: 2026-02-14 +--- + +Some websites [only serve](https://incomplete-chain.badssl.com/) leaf/server certificate instead of the usual certificate chain (leaf + intermediate). If a browser doesn't have the corresponding intermediate certificate (that signs the leaf certificate) cached beforehand, this can cause certificate error. + +To download the missing intermediate certificate, click on "Not secure" > "Certificate details" > Details tab > "Authority Information Access", there should be a link next to "CA Issuers". + +The easiest way is to import the downloaded certificate in Chromium/[Cromite](https://github.com/uazo/cromite) is to use the built-in Certificate Manager (`chrome://certificate-manager/localcerts/usercerts`). If you use [p11-kit]() (`trust anchor --store interCA.crt`) to import, Cromite may not necessarily trust it; in that case, in Certificate Manager (`chrome://certificate-manager/localcerts`), enable "Use imported local certificates...".