From owner-freebsd-stable@FreeBSD.ORG Mon Mar 23 12:40:40 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 733F7D31; Mon, 23 Mar 2015 12:40:40 +0000 (UTC) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2FB10353; Mon, 23 Mar 2015 12:40:39 +0000 (UTC) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3l9b0H2HvxzZrj; Mon, 23 Mar 2015 13:40:31 +0100 (CET) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id GDWTnnr3hXT5; Mon, 23 Mar 2015 13:40:28 +0100 (CET) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Mon, 23 Mar 2015 13:40:28 +0100 (CET) Message-ID: <551009BB.9020906@FreeBSD.org> Date: Mon, 23 Mar 2015 13:40:27 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Gerhard Schmidt , freebsd-stable@freebsd.org, FreeBSD Ports Subject: Re: Problems with openssl 1.0.2 update References: <550FEBE6.5090804@ze.tum.de> In-Reply-To: <550FEBE6.5090804@ze.tum.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 12:40:40 -0000 On 03/23/15 11:33, Gerhard Schmidt wrote: > Hi, > > we experiencing a problem after upgrading the openssl port to openssl > 1.0.2. > > /usr/bin/vi started to crash after some seconds with segfault. > /rescue/vi works just fine. Deleting the openssl 1.0.2 package > everything works just fine again. Installing the old openssl 1.0.1_18 > package it still works just fine. > > it seams that besides vi the bash also has this problem. Anybody > experiencing the same or is this something specific to my system. > > I'm running FreeBSD 10.1 updated tonight. I am seeing runtime problems with asterisk13 (which I maintain), caused by the OpenSSL update fallout. In this case, after some analysis, I concluded the problem is the libsrtp port requiring OpenSSL from ports(for a reason), causing asterisk to link to that too, which would be correct. Asterisk also uses the security/trousers port, which links to system OpenSSL. This ensues a conflict which now results in asterisk segfaulting and stopping to work. I'm investigating what can be done about this. As a local solution I can force the trousers port to link against OpenSSL from ports, but this will not fix the general problem. As a port maintaner I ony see modifying the trousers port to depend on ports OpenSSL as a solution, is this acceptable? -- Guido Falsi