Urgent.News

What's breaking now, across thousands of outlets.

Tech

The eMudhra issue was so bad, it delayed Fedora 45 until November at the earliest

Better safe than sorry, though.

The eMudhra issue was so bad, it delayed Fedora 45 until November at the earliest

The eMudhra security issue has caused significant delays for the Fedora 45 operating system release. This issue stems from eMudhra distributing private keys that are extremely vulnerable to cracking, with the number 4 being the most problematic. The Fedora community, recognizing the severity of this situation, has chosen to postpone the release of Fedora 45 until November at the earliest.

Four major concerns, known as blockers, have been identified, with the eMudhra problem being one of them. The community is actively working to resolve these blockers, including the eMudhra certificate issue, before proceeding with the release.

Written by urgent.news from XDA Developers's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at xda-developers.com →

More in Tech

Why free model tiers look dead when they aren't

Why free model tiers look dead when they aren't I keep a small probe script that walks a list of OpenAI-compatible endpoints and asks each one the same two questions: what do you have, and will you…

  • 200 status code only confirms authentication and catalog access, not model availability.
  • 410 status code indicates a retired model, not an outage.
  • 429 status code suggests a budget issue, not a system outage.

Read-Only Was Never Harmless: Identity Lessons from CVE-2026-114625

Read-Only Was Never Harmless: Identity Lessons from CVE-2026-114625 Security programmes routinely tier accounts by what they can change.

  • Read-only access in Arista VeloCloud Orchestrator can grant operator-level privileges.
  • Low-level credentials like Enterprise Read Only can be exploited by attackers.
  • Mitigation includes patching, account audits, and restricted administrative access.

Kubernetes Has Garbage Collection. Why Did We Build Another One?

This is article 2 of 10 in Beyond Kubernetes Defaults . Read article 1: When Kubernetes Primitives Aren’t Enough first. This article is cross-published from Zen Mesh .

  • Kubernetes has built-in resource lifecycle management features.
  • Zen Cleaner is a garbage collector for explicit cleanup policies.
  • Policy controller justified for unrelated resource kinds and different TTLs.

More from Friday 23 October →