Bugtraq Is Back
Bugtraq was founded in 1993 by Scott Chasin as a full‑disclosure mailing list for security researchers. After more than a decade of prominence, the list fell silent following a series of domain acquisitions. The new owner has revived Bugtraq on securityfocus.com, preserving its original mission and archives for future disclosure.
- ▪Scott Chasin created Bugtraq in 1993 as a mailing list for unrestricted vulnerability disclosure.
- ▪Bugtraq served as the central hub for vulnerability research for over ten years before becoming inactive due to domain changes.
- ▪The securityfocus.com domain and Bugtraq name have been acquired to restart the mailing list under the same address.
- ▪Archived messages will be preserved and made accessible separately from the revived list.
- ▪The revival emphasizes preserving cybersecurity history and supporting ongoing full‑disclosure practices in 2026.
Hacker News (Front Page) files mainly under programming. We currently carry 1,158 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 | Securityfocus |
| Canonical URL | https://lists.securityfocus.com/hyperkitty/list/[email protected]/thread/CHKLXLA7SJEWLDFHWXB3QU57ADOXGL2E/ |
| Publication time | Wed, 05 Aug 2026 00:05:49 +0000 |
| Retrieval time | 2026-08-05T00:45:47.127Z |
| Last seen | 2026-08-05T00:45:47.127Z |
| 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 | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| 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
In 1993, Scott Chasin created Bugtraq as a place for full disclosure - a mailing list where security researchers could publish vulnerabilities openly, without gatekeepers, without politics. For over a decade, it was the heartbeat of vulnerability research. If something mattered in security, it was on Bugtraq first. Then it went quiet. The domain changed hands through a chain of acquisitions, and somewhere along the way, Bugtraq stopped being Bugtraq. The archives went dark. The list went silent. A generation of researchers grew up without it. Today, we bring it back. I have acquired securityfocus.com and the Bugtraq name. Not to build a museum - to restart the conversation. The mission is unchanged: full disclosure, researcher-first, no corporate filter.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Securityfocus.
Discussion
0 commentsMore from Securityfocus
