From owner-freebsd-python@FreeBSD.ORG  Mon Mar  3 09:45:52 2014
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7F0E13FE;
 Mon,  3 Mar 2014 09:45:52 +0000 (UTC)
Received: from mail-ie0-x241.google.com (mail-ie0-x241.google.com
 [IPv6:2607:f8b0:4001:c03::241])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 44514FC2;
 Mon,  3 Mar 2014 09:45:52 +0000 (UTC)
Received: by mail-ie0-f193.google.com with SMTP id rl12so2255547iec.8
 for <multiple recipients>; Mon, 03 Mar 2014 01:45:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=pSZOMM+rGDUFngDwLOTw2eixTcBFWCjojGN0nlwKVu0=;
 b=L+LS/FQJAdeO49jTyKldS+VZPuyIV1YvpwFu47RaGzduu0AyqeWQxiosXQh3tQFOsE
 GWCJTfQJ9BPSgmw35VbZaZC8igNOS8XDlTT8m1GK7Y/2BA4+/CoTnBlydMIEsG6X+ayq
 9pYez/tx34ymg8k03lwxBbL4GS0wf5j0AIJdv2k48pkrTfLFDd9A0LbID8rYWT1Vs/gd
 rr+PpaMDPav/zkZj+XU2nrQXGMyEFGlMwD4f4/+8sRU0rJpaEnpuC3uFjWr7XC6LaYyX
 rlRE4N+UjJzFSltVFGsEVs1XyitxLA0WVV0gKFSHDXFQtL4ffcKmuvi/dI+oLmFYCpUY
 Ka/g==
MIME-Version: 1.0
X-Received: by 10.43.58.19 with SMTP id wi19mr10946050icb.53.1393839951728;
 Mon, 03 Mar 2014 01:45:51 -0800 (PST)
Received: by 10.42.159.132 with HTTP; Mon, 3 Mar 2014 01:45:51 -0800 (PST)
In-Reply-To: <53143F24.500@FreeBSD.org>
References: <CAPH9q1p0vzjzmhyeQKqMp=JWp22sMJPSa4vBywEcgAgYuKojqA@mail.gmail.com>
 <B09BA639-565A-40C6-A5E1-46555213BE8B@gmail.com>
 <53142DA3.9000604@gmail.com> <53143F24.500@FreeBSD.org>
Date: Mon, 3 Mar 2014 03:45:51 -0600
Message-ID: <CAPH9q1pv5YnSVLjDZwYsH1LoQS-sHiVBiHiKL1LnEkEYa16Y3g@mail.gmail.com>
Subject: Re: pyhon33 still listed as vulnerable
From: JEREMY COX <jeremy.m.cox@gmail.com>
To: koobs@freebsd.org, 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 09:45:52 -0000

pkg audit -F was the correct solution. Thank you very much for the
assistance!

Regards,
Jeremy


On Mon, Mar 3, 2014 at 2:36 AM, Kubilay Kocak <koobs.freebsd@gmail.com>wrote:

> On 3/03/2014 6:22 PM, Andrew Berg wrote:
> > On 2014.03.03 01:20, Dmitry Sivachenko wrote:
> >> I already fixed that yesterday, update your ports tree.
> > I have this issue as well on a fresh ports tree.
>
> Does updating the vulnerability database help? Either via:
>
> pkg audit -F if using pkg, or portaudit -F if using portaudit
>
>
>