Signing Is for the Bad Days
The article discusses the importance of implementing signature verification in software supply chains to prevent security incidents. It highlights the limitations of relying solely on hash-based verification methods, which cannot confirm the integrity of the original files. The author emphasizes the need for robust tools like TUF and Sigstore to enhance security against potential compromises in build systems.
- ▪The article argues that signatures provide essential security assurances that hashes alone cannot offer.
- ▪It introduces Santiago Torres-Arias, a key figure in developing tools like TUF and Sigstore for supply chain security.
- ▪The author explains how TUF mitigates risks by separating signing roles and keys to protect against compromised infrastructure.
2 outlets in our directory ran this story, first to last over 21 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ How bad are robocalls these days? — Reddit
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
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 | Andrew Nesbitt |
| Canonical URL | https://nesbitt.io/2026/05/24/signing-is-for-the-bad-days.html |
| Publication time | Sun, 24 May 2026 10:48:06 +0000 |
| Retrieval time | 2026-05-24T11:07:32.394Z |
| Last seen | 2026-05-24T11:07:32.394Z |
| 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 | 5gjZw7C6VpZC · 2 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
Signing is for the bad dayssupply-chainsecuritypackage-managers May 24, 2026 I have had roughly the same conversation four or five times in the last month. I’m explaining why a registry should adopt Sigstore, or why a build pipeline should emit in-toto attestations, and the person across the table says some version of: we already use TLS to the registry, the registry already hashes the tarballs, the lockfile already pins the hash, what does a signature add? And on a Tuesday afternoon when nothing has gone wrong, the honest answer is that it adds a bit of CPU on publish and a bit of YAML in the workflow and not much else you can see.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Andrew Nesbitt.
Discussion
0 commentsMore from Andrew Nesbitt
