From owner-freebsd-current@FreeBSD.ORG Sun May 20 11:45:26 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 B483916A400 for ; Sun, 20 May 2007 11:45:26 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.101.21]) by mx1.freebsd.org (Postfix) with ESMTP id 9460F13C447 for ; Sun, 20 May 2007 11:45:26 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from hexahedron.daemonology.net (cperciva@fraser.sfu.ca [142.58.101.25]) by rm-rstar.sfu.ca (8.13.6/8.13.4/SFU-5.0H) with SMTP id l4KBjOgi018241 for ; Sun, 20 May 2007 04:45:25 -0700 (PDT) X-Spam-Level: Spam-Level Received: (qmail 4199 invoked from network); 20 May 2007 11:45:19 -0000 Received: from unknown (HELO hexahedron.daemonology.net) (127.0.0.1) by localhost with SMTP; 20 May 2007 11:45:19 -0000 Message-ID: <465034CE.4060802@freebsd.org> Date: Sun, 20 May 2007 07:45:18 -0400 From: Colin Percival User-Agent: Thunderbird 2.0.0.0 (X11/20070511) MIME-Version: 1.0 To: FreeBSD Current References: <20070520022722.1f5a0cda@kan.dnsalias.net> In-Reply-To: <20070520022722.1f5a0cda@kan.dnsalias.net> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by antibody.sfu.ca running antivirus scanner Cc: 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: Sun, 20 May 2007 11:45:26 -0000 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. > ... For the record (since I know several people were asking at BSDCan), this is a great example of why it makes sense to have libmd as well as libcrypto: A minimal hashing library which we maintain ourselves is far less likely to randomly break than a bloated^W more feature-complete library which is maintained outside of FreeBSD and occasionally imported onto a vendor branch. Colin Percival