From owner-freebsd-ports Tue Jun 6 9: 3:10 2000 Delivered-To: freebsd-ports@freebsd.org Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 221C237B974 for ; Tue, 6 Jun 2000 09:03:07 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from almanac.yi.org (pm001-028.dialup.bignet.net [64.79.80.28]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id MAA16623; Tue, 6 Jun 2000 12:03:01 -0400 Received: by almanac.yi.org (Postfix, from userid 1000) id 5CCE1195D; Tue, 6 Jun 2000 12:02:07 -0400 (EDT) Date: Tue, 6 Jun 2000 12:02:07 -0400 From: Will Andrews To: Christophe Prevotaux Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Hylafax Port Message-ID: <20000606120207.A7792@argon.gryphonsoft.com> References: <200006061554.RAA05017@proton.hexanet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200006061554.RAA05017@proton.hexanet.fr>; from chris@hexanet.fr on Tue, Jun 06, 2000 at 05:54:49PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jun 06, 2000 at 05:54:49PM +0200, Christophe Prevotaux wrote: > Does anyone knows when the Hylafax Port will be fixed ? Only the hylafax developers, who apparently don't care about serious security holes in their software. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message