From owner-freebsd-python@FreeBSD.ORG Mon Mar 3 11:21:53 2014 Return-Path: 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 391B7A33; Mon, 3 Mar 2014 11:21:53 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 05B25C1B; Mon, 3 Mar 2014 11:21:53 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id v10so1559564pde.1 for ; Mon, 03 Mar 2014 03:21:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=RfTzO8mPEYnu2GhTHL2OhL/c5jLKG30dvLVMcApQHFc=; b=yXrEOZWZWm3Nct+PlY4FCO93ARBitpG1Ep5ME5T3gBhDbwsOULHeQTdOf8VXF3fvyA uh4VpP/fN0ASIsn5KBEpIlQsDGkEnH7d8Pl2Cv0Hzak3OOK794JjC/7AAh5UyqjZunTo 1xDlvR3g4I5U3sddc/Q7Wuu1mIE/5LKpSz44NAgsfxmP570Gj+xd+8fGDjwRSBsD97Mt 8JA9LroGFdnY9TOW15Hffz+BOLtnQ4J7K7IRpGoYl6zed7hjxP4aRPvDyAoWtCHplHd3 xDKCE9x/n1mDH6m8sXLlp4dTcAFEIl0Fq77i+JdKBeV/M3IzLr5mY9/bi5lagthFhth0 cOhQ== X-Received: by 10.68.231.35 with SMTP id td3mr5158757pbc.137.1393845712714; Mon, 03 Mar 2014 03:21:52 -0800 (PST) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id vb7sm19019476pbc.13.2014.03.03.03.21.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Mar 2014 03:21:52 -0800 (PST) Message-ID: <531465CB.7080107@FreeBSD.org> Date: Mon, 03 Mar 2014 22:21:47 +1100 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Thunderbird/27.0 MIME-Version: 1.0 To: JEREMY COX , freebsd-python@freebsd.org Subject: Re: pyhon33 still listed as vulnerable References: <53142DA3.9000604@gmail.com> <53143F24.500@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: antoine@FreeBSD.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 11:21:53 -0000 On 3/03/2014 8:45 PM, JEREMY COX wrote: > 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 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 >> >> >> > My pleasure Jeremy, thank you for bringing it to our attention. Full credit to antoine@ for the hint -- koobs