Updated GPG Key for Signing Firefox and Thunderbird Releases
Our review of available audit records found no evidence that the key was accessed by an unauthorized party while it was present in the repository. Access to the repository was limited to a small group within Mozilla, all of whom already had authorized access to the key through other means. We have revoked the previous signing key and added safeguards to prevent similar issues in the future.
- ▪Our review of available audit records found no evidence that the key was accessed by an unauthorized party while it was present in the repository.
- ▪Access to the repository was limited to a small group within Mozilla, all of whom already had authorized access to the key through other means.
- ▪We have revoked the previous signing key and added safeguards to prevent similar issues in the future.
Hacker News (Front Page) files mainly under programming. We currently carry 1,399 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Mozilla Security Blog |
| Canonical URL | https://blog.mozilla.org/security/2026/08/10/updated-gpg-key-for-signing-firefox-and-thunderbird-releases/ |
| Publication time | Tue, 11 Aug 2026 04:04:36 +0000 |
| Retrieval time | 2026-08-11T04:30:45.211Z |
| Last seen | 2026-08-11T04:30:45.211Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ORc7nVC97o5P · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Categories: Security Updated GPG key for signing Firefox and Thunderbird Releases Ben Hearsum August 10, 2026 Today, we moved to a new GPG signing subkey used to sign certain Firefox and Thunderbird artifacts (namely Linux tarballs, RPM packages, checksums files) after an unencrypted copy of the previous subkey was inadvertently committed to a private GitHub repository. Our review of available audit records found no evidence that the key was accessed by an unauthorized party while it was present in the repository. Access to the repository was limited to a small group within Mozilla, all of whom already had authorized access to the key through other means. We have revoked the previous signing key and added safeguards to prevent similar issues in the future.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Mozilla Security Blog.
Discussion
0 commentsMore from Mozilla Security Blog
