From owner-freebsd-python@FreeBSD.ORG  Mon Mar  3 07:47:39 2014
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 91C994E3
 for <freebsd-python@freebsd.org>; Mon,  3 Mar 2014 07:47:39 +0000 (UTC)
Received: from mail-ie0-x244.google.com (mail-ie0-x244.google.com
 [IPv6:2607:f8b0:4001:c03::244])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5DC5B677
 for <freebsd-python@freebsd.org>; Mon,  3 Mar 2014 07:47:39 +0000 (UTC)
Received: by mail-ie0-f196.google.com with SMTP id rd18so3050760iec.3
 for <freebsd-python@freebsd.org>; Sun, 02 Mar 2014 23:47:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=dzBZGZTxw0RRRtsrWuhiURfsQVbY0iW0Hd4eJ5EI20E=;
 b=RPq6ww2RprrbT7bz6T80fO0B/tThuNX6BFEVt9GlPaCZt2j/czB+1J+mVjtb4lIKyW
 TkgaAsEqLVYLO+nPewDu8T3QCqR4Bw2lyKM8qtqvlyFUyJ8xSB3IQ8qXIifSdqLc9CH7
 njvtpnnb2Zf7XhTOykGmdAitFuiniy68h5eItdhvBY3p8IYsSu6mcIbJP/5yXC4rTRI1
 kuBlijB0LlXABMyJwlL65iCZ/6EgMwSdRGV+p6UqIYstTPE3L/4lF704eRZM9ziqovdj
 q9Tv83b9J8HjIfsKeMDvK/hmOKpXdjvNtrVPBcutTfLQY5GGQbblfJtonMgN9kV+KgLR
 /BuA==
MIME-Version: 1.0
X-Received: by 10.50.115.102 with SMTP id jn6mr20209084igb.10.1393832858905;
 Sun, 02 Mar 2014 23:47:38 -0800 (PST)
Received: by 10.42.159.132 with HTTP; Sun, 2 Mar 2014 23:47:38 -0800 (PST)
Date: Mon, 3 Mar 2014 01:47:38 -0600
Message-ID: <CAPH9q1qyx=9p60XmU1_C1dC4V8Am9UJEeT2SpGzupPcF7J_6YQ@mail.gmail.com>
Subject: pyhon33 still listed as vulnerable
From: JEREMY COX <jeremy.m.cox@gmail.com>
To: freebsd-python@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.17
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 07:47:39 -0000

Sorry if I wasn't more clear, my ports tree was updated a few minutes
before I wrote the email, from March 3 @ 0700 UTC... and the patch for
CVE-2014-1912 was already in /usr/ports/lang/python33/files... otherwise I
never would have updated the port! I always verify changes with the FreeBSD
svn website first. Even after the ports tree was updated, and the port was
updated, pkg audit still lists python33-3.3.3_3 as vulnerable, when the CVE
lists the vulnerability applicable only to python33 <= 3.3.3_2.