From owner-freebsd-questions@FreeBSD.ORG Mon Aug 8 02:37:32 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDA6416A41F for ; Mon, 8 Aug 2005 02:37:32 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C84F43D45 for ; Mon, 8 Aug 2005 02:37:32 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.101] (adsl-66-137-150-253.dsl.rcsntx.swbell.net [66.137.150.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 9806C3FC37; Sun, 7 Aug 2005 21:37:25 -0500 (CDT) Date: Sun, 07 Aug 2005 21:37:02 -0500 From: Paul Schmehl To: =?UTF-8?Q?K=C3=B6vesd=C3=A1n_G=C3=A1bor?= , Bill Schoolcraft Message-ID: <877BD358067156EA7BFB74C7@Paul-Schmehls-Computer.local> In-Reply-To: <42F6B222.1030604@t-hosting.hu> References: <20050808004123.94325.qmail@web52513.mail.yahoo.com> <42F6B222.1030604@t-hosting.hu> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: FreeBSD Subject: Re: gaim or aim on 5.4 amd64 ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2005 02:37:33 -0000 --On August 8, 2005 3:15:14 AM +0200 K=C3=B6vesd=C3=A1n G=C3=A1bor=20 wrote: >> > It isn't a compiling error. There is a tool called portaudit, which > checks the ports against security vulnerabilities, and gaim 1.2.1 has > some security issues, thus portaudit prevents You from installing it. Is > your ports tree up-to-date? I don't think so. Gaim 1.2.1 is pretty old. > Upgrade yout ports tree via cvsup and try again. If the new version has > security issues, too, You could decide to configure portaudit to ignore > this problem. > Portaudit merely reports on security vulnerabilities in the ports.=20 Portaudit will not prevent the install of a vulnerable port. The port=20 itself does that, by being marked as FORBIDDEN in the Makefile, because it=20 has a vulnerability. You can configure portaudit to ignore the vulnerability in that port, but=20 that won't solve the problem of trying to install the port. To install the = port you must either update the port (if it's out of date) or install it=20 using DISABLE_VULNERABILITIES=3Dyes when you make the port. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/