Ask HN: How are you stopping supply chain attacks via compromised dev keys?
The article discusses concerns regarding supply chain attacks facilitated by compromised developer keys on platforms like GitHub and GitLab. It highlights the lack of features such as organization-level allowlisting of signing keys and the inability to reject pushes based on signing keys. The author expresses frustration over the need for additional security measures and the inadequacy of existing protections.
- ▪GitHub and GitLab verify commits based on user account keys but do not allow specific key requirements.
- ▪Compromised developer accounts can still push malicious commits that appear verified.
- ▪The author is considering implementing hardware keys and custom verification processes due to security concerns.
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 →
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 | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=47945581 |
| Publication time | Wed, 29 Apr 2026 08:25:21 +0000 |
| Retrieval time | 2026-04-29T08:31:52.291Z |
| Last seen | 2026-04-29T08:31:52.291Z |
| 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 | Lql8bEsxpUiR |
| 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
GitHub and GitLab will verify that a commit is signed by some key on the user's account. They won't let you require that it be signed by a specific key, like a hardware-backed YubiKey your org issued. So if an attacker compromises a developer's laptop or GitHub account, they can add a new signing key, push commits signed with it, and pass every "Require signed commits" protection in place. The malicious commit lands in the repo with a "Verified" badge.As far as I can tell, neither platform offers:- An org-level allowlist of approved signing keys- A way to reject a push based on the signing key itself- A built-in way to audit who has accessed what (You have to stream and parse the audit logs yourself!)The workarounds I've seen, like re-verifying signatures in CI, blocking deployments on…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.