From owner-freebsd-current@FreeBSD.ORG Tue May 22 00:18:25 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF49F16A421 for ; Tue, 22 May 2007 00:18:25 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.freebsd.org (Postfix) with ESMTP id AF56713C447 for ; Tue, 22 May 2007 00:18:24 +0000 (UTC) (envelope-from null@pozo.com) Received: from T41p.pozo.com (t41p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.1/8.14.1) with ESMTP id l4LNx0QG057107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 May 2007 16:59:00 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <200705212359.l4LNx0QG057107@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 21 May 2007 16:58:58 -0700 To: "Simon L. Nielsen" , Alexander Kabaev From: Manfred Antar In-Reply-To: <20070521201817.GB1380@zaphod.nitro.dk> References: <20070520022722.1f5a0cda@kan.dnsalias.net> <20070521201817.GB1380@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Michiel Boland , freebsd-current@freebsd.org, Larry Rosenman Subject: Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 00:18:25 -0000 At 01:18 PM 5/21/2007, Simon L. Nielsen wrote: >On 2007.05.20 02:27:22 -0400, Alexander Kabaev wrote: > >> there were several reports of OpenSSL being broken when compiled with >> GCC 4.2. It turns out OpenSSL uses function casting feature that was >> aggressively de-supported by GCC 4.2 and GCC goes as far as inserting >> invalid instructions ON PURPOSE to discourage the practice. > >"Interesting" choice - oh well. > >> Consequently, OpenSSL need the patch similar to attached one to work. >> Just in case mailing list will eat the attachment, the patch can be >> found at >> >> http://people.freebsd.org/~kan/openssl-gcc42.diff >> >> Unfortunately, our OpenSSL maintainer(s) are currently en-route from >> BSDCan and cannot attend to the matters. Once we figure the best way to >> fix the code and to integrate the fix into OpenSSL, we will check the >> fix info CVS. People are advised to patch their sources locally until >> then. > >I had hoped to be able to test and commit today, but I'm too beat from >the trip from Canada to be able to do this until tomorrow (it's very >high in the priority list to get this done tomorrow but I don't know >how hard the jet lag will hit this time). > >I haven't seen enough reports of this patch working to be really >comfortable committing the patch without having had a chance to try it >myself. > >Other people who try this patch please report any success/failure. >Success can also just be reported in private mail. > >Oh, and in case people were wondering - I'm not a "vendor branch >purist" wrt. OpenSSL, so getting the patch commited once I'm sure it >is OK isn't a problem. > >Alexander, thanks a lot for looking at this! Patch works for me.Using ssl for sendmail with Sasl ,also had to apply the patch to the openssl port. ================================== || null@pozo.com || || Ph. (415) 681-6235 || ==================================