From: tytso at mit.edu (Theodore Ts'o)
Subject: [COFF] termination and untermination of bugtraq mailing list
Date: Mon, 18 Jan 2021 22:57:23 -0500 [thread overview]
Message-ID: <YAZYo3vQlK2kJVck@mit.edu> (raw)
In-Reply-To: <20210117205818.GA12967@tau1.ceti.pl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
On Sun, Jan 17, 2021 at 09:58:18PM +0100, Tomasz Rola wrote:
> Howdy,
>
> Perhaps this is off topic for this list, if so, apologies in advance.
>
> Or perhaps this will be of interest to some who do not trace yet
> another mailing list out there :-).
>
> Two days ago I received a notice that bugtraq would be terminated...
>
> But what could possibly explain an almost year long gap? Their
> computers changed owners last year, and maybe someone switched the
> flip, were fired, nobody switched it on again? Or something else?
The explanation can be found here:
https://www.zdnet.com/article/iconic-bugtraq-security-mailing-list-shuts-down-after-27-years/
"... BugTraq itself also exchanged hands several times, from
Chasin to Brown University, then to SecurityFocus, which was
acquired by Symantec.
The portal's demise started in 2019 when Broadcom acquired
Symantec. Three months later, in February 2020, the site
stopped adding new content, remaining mostly an empty shell.
Today, the site's last maintainers confirmed the portal's
current state of affairs and formalized BugTraq's passing into
infosec lore."
An update: https://seclists.org/bugtraq/2021/Jan/1
"Bugtraq has been a valuable institution within the Cyber
Security community for almost 30 years. Many of our own people
entered the industry by subscribing to it and learning from
it. So, based on the feedback weâve received both from the
community-at-large and internally, weâve decided to keep the
Bugtraq list running. Weâll be working in the coming weeks to
ensure that it can remain a valuable asset to the community
for years to come. - Accenture Security"
- Ted
next prev parent reply other threads:[~2021-01-19 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 20:58 rtomek
2021-01-19 3:57 ` tytso [this message]
2021-01-23 17:12 ` rtomek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YAZYo3vQlK2kJVck@mit.edu \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).