New Python security updates explicitly block the eMudhra certificates by SPKI
Comments on “New Python security updates explicitly block the eMudhra certificates by SPKI”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
Python's core developers released security updates that hard-code a block list of certificates by SPKI hash, rejecting certificates issued under eMudhra keys even if system or bundled root stores still trust them.
Why it ranked
No. 42 of 155 with a score of 0.64. The panel rated it highest on substantiated (0.78) and reader interest (0.72), lowest on new information (0.52). The judges disagreed most on new information (spread 0.55), so the story is marked contested.
- AI judgeJudge 2claude-haiku-5-5
- Security response to eMudhra CA key disclosure, shipped as Python patches with concrete code detail; covered in related stories, but the SPKI blocklist mechanism and sourced links are substantive.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported technical report on Python’s emergency SPKI distrust mechanism for eMudhra certificates, with implementation specifics and operational implications. It overlaps recent eMudhra coverage, so novelty is reduced, but remains actionable and broadly relevant.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.64total under rubric v2.2Contestedjudges differ by 0.55 on new information
- Significance0.59
- Reader interest0.72
- Audience breadth0.65
- Practical relevance0.64
- Substantiated0.78
- Technical depth0.69
- New information0.52
- Counts against: Promotional0.03
- Counts against: Overclaim0.12
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.67 | 0.40 | 0.70 | 0.59 | 0.30 | +0.24 | +0.141 |
| Reader interest | 0.69 | 0.60 | 0.88 | 0.72 | 0.28 | +0.26 | +0.188 |
| Audience breadth | 0.65 | 0.55 | 0.76 | 0.65 | 0.21 | +0.13 | +0.085 |
| Practical relevance | 0.62 | 0.50 | 0.80 | 0.64 | 0.30 | +0.22 | +0.141 |
| Substantiated | 0.64 | 0.80 | 0.90 | 0.78 | 0.26 | +0.05 | +0.039 |
| Technical depth | 0.76 | 0.60 | 0.72 | 0.69 | 0.16 | +0.05 | +0.035 |
| New information | 0.75 | 0.20 | 0.62 | 0.52 | 0.55 , above the contested threshold | +0.05 | +0.026 |
| Promotional | 0.06 | 0.03 | 0.01 | 0.03 | 0.05 | −0.19 | −0.006 |
| Overclaim | 0.23 | 0.10 | 0.03 | 0.12 | 0.20 | −0.11 | −0.013 |
| Sum of contributions | +0.635 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.635 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-28/42/"><img src="https://rubric.hrih.si/badge/2026-10-28/42.svg" alt="Ranked #42 on Rubric, 28 Oct 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.