Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Oct 2014 07:55:32 +0400
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: Who named shellshock?

On Mon, Oct 06, 2014 at 08:33:44PM -0700, Michal Zalewski wrote:
> This is the bit from Stephane:
> 
> http://www.openwall.com/lists/oss-security/2014/10/03/14
> 
> -- snip! --
> A release schedule with public disclosure on the 24th at
> 14:00 UTC and early notification to other unix and linux
> vendors on the 22nd and select infrastructure provider
> notification (such as CDNs including Microsoft) on the 23rd
> proposed on the 16th by Florian.
> 
> [...]
> 
> bashdoor.com was registered (not by me) with a creation date of
> 2014-09-24 13:59 UTC sometime before 2014-09-24 06:59:10Z
> according to whois. Florian also said here that someone brought
> the early notification sent to vendors/infrastructure to the
> press, so someone obviously intended to take it to the press. I
> don't know whom.
> -- snip! --

Thanks!

> The bashdoor.com thing sounds a bit damning (doesn't sound like
> something that would be in the notifications to CDNs & co?).

This certainly sounds bad, but what matters most is whether any info on
the bug got to an unintended party before 2014-09-24 14:00 UTC or not.
The name bashdoor.com itself does not leak any vulnerability details,
nor that there was in fact a bash vulnerability coming.  This does
suggest that someone wasn't 100% busy using the then non-public info for
its intended purpose, but it does not indicate they violated the trust
of whoever disclosed the info to them (except possibly by cybersquatting
the domain), nor put bash users at any additional risk.

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Powered by Openwall GNU/*/Linux - Powered by OpenVZ