Repository navigation
Emudhra our dependencies - #855
Merged
Merged
Conversation
The pylon 2.3.1 image ships certifi, uv and Debian ca-certificates that still trust the compromised eMudhra/emSign CAs. Pylon 2.3.4 is rebuilt with fixed versions; 2.3.2 and 2.3.3 only add bug fixes. The image is pinned by its index digest, like the third-party images. Impacts: validator-runner, miner-runner, facilitator
Pylon client 2.3.1 is the release made after the eMudhra CA compromise. Its code is the same as in 2.3.0: the package carries no CA certificates and uses the certifi installed next to it, so only the lockfiles change. Impacts: lib, validator, miner, executor, facilitator
nginx-rt v1.2.1 ships an Alpine CA bundle with the compromised emSign roots, which certbot trusts when it renews certificates. v1.4.0 is built on nginx 1.30.6 with the updated bundle. Since v1.2.1 the image also runs certbot renewals from crond and loads the OpenTelemetry module. The facilitator's `listen ... ssl http2` lines keep working on nginx 1.25+ and only log a deprecation warning. Impacts: validator-runner, miner-runner, facilitator
`latest` is a 2024 build whose pip, certifi and Debian ca-certificates trust the compromised eMudhra/emSign CAs. The runner never pulls and the service has no watchtower label, so a re-pushed `latest` would not reach running validators; an explicit tag does, because compose pulls a missing image when the runner restarts. The entrypoint and the wallet script are unchanged apart from moving the env var check into main(). Impacts: validator-runner
The Docker Hub `latest` image of bittensor-prometheus-proxy is a 2025 build whose certifi trusts the compromised eMudhra/emSign CAs, and it sends the validator's metrics to the central proxy over HTTPS. The fixed release, 1.0.2, is published only on ghcr. Since 1.0.0 the on-site proxy accepts remote writes on /prometheus/outbound, forwards them to /prometheus/inbound and needs BITTENSOR_NETUID for its signed headers. The central proxy at prometheus.bactensor.io has to run 1.0.0 or later before validators update; an older one has no /prometheus/inbound route, so the forwarded metrics are lost. Impacts: validator-runner
Commit message lint report
Status: ✅ No issues found. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.