From owner-freebsd-stable Fri May 24 20:30:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pakastelohi.cypherpunks.to (pakastelohi.cypherpunks.to [213.130.163.34]) by hub.freebsd.org (Postfix) with ESMTP id 353AA37B406 for ; Fri, 24 May 2002 20:30:42 -0700 (PDT) Received: from LUCKYVAIO (adsl-208-201-244-240.sonic.net [208.201.244.240]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pakastelohi.cypherpunks.to (Postfix) with ESMTP id 048A436546 for ; Sat, 25 May 2002 05:30:39 +0200 (CEST) From: "Lucky Green" To: Subject: Re: IPv6 and SSL Date: Fri, 24 May 2002 20:29:49 -0700 Message-ID: <001901c2039c$6f4e2910$c33a080a@LUCKYVAIO> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David W. Chapman Jr wrote: ------ On Thu, May 23, 2002 at 11:27:49AM -0700, Vivek Khera wrote: > >>>>> "AG" == Aragon Gouveia writes: > > AG> There are some packages that I've tried compiling with IPv6 and > AG> SSL support. The Postfix port, for example, won't compile with > AG> both options checked. Other packages I've compiled manually > AG> compile and run, but ssl is broken. > > For the postfix port, the TLS/SSL support is from a patch to the > official postfix as is the IPv6 support. These two patch files > conflict (ie, try to patch some of the same things and both can't do > it). > > You're free to try and produce a combined IPv6+TLS patch and I'll be > happy to include it in the port. I'm not sure how much these conflict, but we'd have a better chance if both were context diffs, I'm not sure if either are now as it has been a while since I checked last. -------- AFAICT, the conflicts between the postfix TLS patch and IPv6 patch are not necessarily FreeBSD-specific, but are caused by a conflict between the generic postfix TLS patch and the IPv6 patch. This may be due in part to the fact that the postfix TLS patch itself is not part of the official postfix release. So we have a port on top of a patch on top of another patch on top of a base distribution. Anybody that finds a fix, or even figures out what the cause of the problem is, probably should notify the general postfix TLS patch maintainer at http://www.aet.tu-cottbus.de/personen/jaenicke/pfixtls/ --Lucky, who is very much looking forward to being able to use postfix with both TLS and IPv6, but who is wondering if this discussion even belongs in freebsd-stable, since postfix is part of the ports collection and (unfortunately ;) not part of the base FreeBSD release. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message