ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode
Organization

gpg.fail

2 mentions in 7 days · 2 in 30 days · 2 total · first seen · last

Search everything

Timeline

Re: Retrospective by 'gpg.fail' authors

oss-security thread on the gpg.fail retrospective discusses legacy code removal and flaws surfaced by frontier AI models in open-source projects.

In a reply to Soatok Dreamseeker's gpg.fail retrospective thread on the oss-security mailing list, cryptographer Peter Gutmann argues it is often unclear which legacy code is obsolete or can be safely removed. He recounts a discussion with another well-known open-source project developer estimating, unscientifically, that around half of issues in such projects were found by frontier AI models. The exchange reflects on lessons from documenting weaknesses in GnuPG/OpenPGP implementations.

oss-security · 6h agoResearch 9 sources

Re: Retrospective by 'gpg.fail' authors

GnuPG maintainer Werner Koch responds on oss-security to a gpg.fail retrospective covering 2003-era GnuPG code.

On oss-security, GnuPG lead developer Werner Koch replied to a retrospective published by the gpg.fail authors, citing a December 2003 commit in GnuPG's gettime.c affecting asctimestamp and printf format attributes in util.h. The excerpt contains no new CVE identifiers or exploitation evidence, and appears to revisit long-standing historical GnuPG code paths discussed by the retrospective's authors.

oss-securityupdated · 6h agofirst · 18h agoResearch 9 sources

Appears with

vendor GnuPG 1
Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.