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. Regards Estartu -- ---------------------------------------------------------- Gerhard Schmidt | E-Mail: schmidt at ze.tum.de Technische Universit?t M?nchen | Jabber: estartu at ze.tum.de WWW & Online Services | Tel: +49 89 289-25270 | PGP-PublicKey Fax: +49 89 289-25257 | on request
Hi!> we experiencing a problem after upgrading the openssl port to openssl > 1.0.2.I have 1.0.2 installed on my testbox. vi works fine.> /usr/bin/vi started to crash after some seconds with segfault.Do you have a coredump ? -- pi at opsec.eu +49 171 3101372 5 years to go !
On Mar 23 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. >There is definitely something not right. See this too https://forums.freebsd.org/threads/postfix-does-not-start-build-anymore-since-upgrade-to-openssl-1-0-2.50959/ I haven't had a chance yet to test it again in more detail, but someone reported that postfix was broken, and I had PHP-FPM racing and taking up 50+ load average on my box which I guess was probably nginx hitting it with tons of requests. Mine is 10.1-STABLE amd64. -- Matt
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 <madpilot at FreeBSD.org>
On 3/23/2015 6:33 AM, 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.Is you vi linked to openssl ? /usr/bin/vi: libutil.so.9 => /lib/libutil.so.9 (0x800883000) libncursesw.so.8 => /lib/libncursesw.so.8 (0x800a95000) libc.so.7 => /lib/libc.so.7 (0x800cea000) -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike at sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/