From owner-freebsd-ports Thu Sep 14 18:37: 7 2000 Delivered-To: freebsd-ports@freebsd.org Received: from forrie.net (forrie.net [64.20.73.233]) by hub.freebsd.org (Postfix) with ESMTP id 4990B37B422; Thu, 14 Sep 2000 18:37:04 -0700 (PDT) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.147.129.124]) by forrie.net with id e8F1avH93682; Thu, 14 Sep 2000 21:36:57 -0400 (EDT) Message-Id: <4.3.2.7.2.20000914213155.00b5cb60@64.20.73.233> X-Sender: forrie@64.20.73.233 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 14 Sep 2000 21:33:44 -0400 To: Kris Kennaway From: Forrest Aldrich Subject: Re: FreeBSD Port: delegate-6.1.16 Cc: max@FreeBSD.org, ports@FreeBSD.org In-Reply-To: References: <4.3.2.7.2.20000913204231.00c774a0@64.20.73.233> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are these changes extensive, or would some patches suffice? (ie: has someone performed some groundwork mods). Apart from this, might you recommend another proxy solution that might suffice? I've attempted (and failed, due to odd documentation) to work with ipfw port forwarding. What I'm wanting to do is to pass POP3 (and perhaps IMAP, etc) access on to a hidden/internal server, from a bastion host. Thanks, _F At 06:30 PM 9/14/00 -0700, Kris Kennaway wrote: >On Wed, 13 Sep 2000, Forrest Aldrich wrote: > > > Have the security issues been addressed with this version? I noted your > > comments; however, this version has been out for a while, so I presume > > someone has looked into it. > >Unfortunately no..I sent the author some feedback a month or two ago about >the kinds of changes that need to be made to secure it. > >Kris > >-- >In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message