[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <03e201cd18ee$1ac42e40$504c8ac0$@com>
Date: Thu, 12 Apr 2012 15:51:59 -0500
From: "Adam Behnke" <adam@...osecinstitute.com>
To: <full-disclosure@...ts.grok.org.uk>, <bugtraq@...urityfocus.com>
Subject: Erronous post concerning Backtrack 5 R2 0day
Yesterday I made a post concerning a 0day advisory in Backtrack 5 R2:
http://seclists.org/fulldisclosure/2012/Apr/123
The posting was incorrect, the vulnerability was NOT in Backtrack but in
wicd, no Backtrack contributed code is vulnerable. When we tweeted and
emailed to mailing lists the notifications of this vulnerability, we
incorrectly shortened the title and called it "Backtrack 5 R2 priv
escalation 0day ", which is misleading and could lead people to believe the
bug was actually in Backtrack. The bug has always resided in wicd and not in
any Backtrack team written code. We apologize for the confusion to the
Backtrack team and any other persons affected by this error. We feel the
Backtrack distro is a great piece of software and wish muts and the rest of
the team the best.
Powered by blists - more mailing lists