curben
/
blog
mirror of https://gitlab.com/curben/blog
1
0
Fork 0
Code Issues Releases Wiki Activity

micropost: 14 February 2026

This commit is contained in:
Ming Di Leom 2026-02-14 05:51:37 +00:00
parent 878a2a4ede
commit def7e9009c
No known key found for this signature in database
GPG Key ID: 32D3E28E96A695E8
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
source/_posts/2026-02-14.md Normal file
View File

@ -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](<https://wiki.archlinux.org/title/User:Grawity/Adding_a_trusted_CA_certificate#System-wide_%E2%80%93_Arch,_Fedora_(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...".