You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eight eMudhra (emSign) intermediate CAs were issued with private keys that can be recovered. Anyone can use them to mint a TLS certificate for any domain, and it chains to roots most trust stores carry. They were revoked on 2026-10-18, but Python clients do not check revocation, so the only fix is to stop trusting them on the client side.
ca-certificates=20250419 certifi=2026.07.22
system g3=CONNECTED aaa=CONNECTED github=CONNECTED
certifi g3=CONNECTED aaa=TLS-REJECT(unable to get local issuer certificate) github=CONNECTED
Fix
The image upgrades the system ca-certificates to 20250419+deb13u1 from trixie-security, which distrusts them (the base image still ships 20250419), and uv.lock moves certifi to 2026.10.19, the first release that drops them. The image installs with pip, which already resolves the newest certifi. Released as 0.7.2: version files, changelog, then the v0.7.2 tag after merge.
Built from this branch on geiserback, both test sites fail with a certificate error and github.com still connects:
ca-certificates=20250419+deb13u1 certifi=2026.10.19
system g3=TLS-REJECT(unable to get local issuer certificate) aaa=TLS-REJECT(unable to get local issuer certificate) github=CONNECTED
certifi g3=TLS-REJECT(unable to get local issuer certificate) aaa=TLS-REJECT(unable to get local issuer certificate) github=CONNECTED
Reviewing files that changed from the base of the PR and between 4b77579 and 53aff62.
⛔ Files ignored due to path filters: 1
uv.lock is excluded by !**/*.lock
📒 Files selected for processing: 8
CHANGELOG.md
Dockerfile
README.md
config.example.yaml
docs/ROADMAP.md
docs/getting-started.md
pyproject.toml
src/audio_transcode_watcher/__init__.py
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
📝 Walkthrough
The 0.7.2 release updates system certificates in the Docker build and changes the project version across package metadata, examples, documentation, and release notes.
Changes: 0.7.2 release
Layer / File(s)
Summary
System certificate update Dockerfile, CHANGELOG.md
The Docker build upgrades ca-certificates. The changelog records distrust updates for eight leaked eMudhra intermediates and certifi and system certificate versions.
Version 0.7.2 references pyproject.toml, src/audio_transcode_watcher/__init__.py, README.md, docs/getting-started.md, config.example.yaml, docs/ROADMAP.md, CHANGELOG.md
Project and package version values change to 0.7.2. Docker examples, configuration comments, the roadmap, and the release link also reference 0.7.2.
The 0.7.2 image picks up the updated Debian security ca-certificates and the latest certifi, which stop trusting the leaked eMudhra intermediates. The rest of the release is version-reference updates. No outstanding issue blocks merging; pinning the certificate versions would be optional hardening for reproducible builds.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly and concisely describes the main change: stopping trust in compromised eMudhra intermediates for release 0.7.2.
Docstring Coverage
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (7 skipped: 7 unsupported.)
✨ Finishing Touches
📝 Generate docstrings
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Eight eMudhra (emSign) intermediate CAs were issued with private keys that can be recovered. Anyone can use them to mint a TLS certificate for any domain, and it chains to roots most trust stores carry. They were revoked on 2026-10-18, but Python clients do not check revocation, so the only fix is to stop trusting them on the client side.
The published image trusts them today. On geiserback, Python inside
drumsergio/audio-transcoder:0.7.1connects cleanly through the system store to two test sites served through the compromised chains, g3 = https://dv-g3b-emudhra.we-have-a-problem.com/ and aaa = https://dv-g3b-aaa-emudhra.we-have-a-problem.com/ (github.com is the control that must keep working):Fix
The image upgrades the system
ca-certificatesto 20250419+deb13u1 from trixie-security, which distrusts them (the base image still ships 20250419), anduv.lockmoves certifi to 2026.10.19, the first release that drops them. The image installs with pip, which already resolves the newest certifi. Released as 0.7.2: version files, changelog, then thev0.7.2tag after merge.Built from this branch on geiserback, both test sites fail with a certificate error and github.com still connects:
Background: https://emudhra.we-have-a-problem.com/
Summary by CodeRabbit
Security
Release
Documentation