Trust the system certificate store for registries (corporate root CA, UnknownIssuer)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- networking
Research direction
Start with crates/kiri-image/src/registry.rs and inspect how ureq and rustls configure trusted roots; then trace the update check and Kiri Share clients to see where the same verifier is used. Compare the proposed system verifier and additional CA file options, and check existing tests for registry TLS behavior. Done means corporate roots are trusted for registry pulls and login, with the intended behavior verified for the update check and Kiri Share.
Written by the indexing model from the issue text.
Description
What you're trying to do
In a company network the image registry (Artifactory) has a certificate issued by the company's own root CA. macOS trusts that root (it's in the System keychain), so browsers, curl and Podman work. With Kiri 0.2.1 (macOS 27.0.1, Apple silicon):
$ docker --context kiri pull registry.corp.example/postgres:17
network error: io: invalid peer certificate: UnknownIssuer
docker login to the same registry fails the same way, and so does Kiri's own update check (update check failed error="io: invalid peer certificate: UnknownIssuer").
The registry client is ureq + rustls with roots from webpki-roots (crates/kiri-image/src/registry.rs); Cargo.lock has no rustls-native-certs or rustls-platform-verifier. There's no setting or file for an extra CA, and the standard variables are ignored:
$ SSL_CERT_FILE=corp-root.pem SSL_CERT_DIR=. kiri raw pull registry.corp.example/postgres:17
kiri: network error: io: invalid peer certificate: UnknownIssuer
Putting the CA into the VM doesn't help, because pulls are made by kiri daemon on the Mac. Today the only way is podman pull … && podman save … | docker --context kiri load.
What you'd like Kiri to do
Any of these would cover it:
- Verify with
rustls-platform-verifier(macOS keychain, Windows store, /etc/ssl on Linux), keepingwebpki-rootsas a fallback. - Load extra roots from a file Kiri owns, e.g.
~/.kiri/certs/*.pem, and fromSSL_CERT_FILE. - A Settings → Network toggle: "Trust certificates from the system".
The same verifier would help the update check and Kiri Share too.
Would you like to build it?
No, just suggesting it
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 329
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 105
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libracoder/kiri
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#289 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 47/100
libracoder/kiri#365 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libracoder/kiri#362 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 47/100
libracoder/kiri#359 ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day