Date: Fri, 8 Feb 2013 16:52:35 -0500 From: Jerry <jerry@seibercom.net> To: freebsd-ports@freebsd.org Subject: Re: openssl broken Message-ID: <20130208165235.0dc7ac68@scorpio> In-Reply-To: <kf3p6b$2hm6$1@de-l.enfer-du-nord.net> References: <20130208154912.0b880f68@scorpio> <kf3p6b$2hm6$1@de-l.enfer-du-nord.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Feb 2013 21:03:07 +0000 (UTC) Michael Grimm articulated: > Jerry <jerry@seibercom.net> wrote: > > > I updated openssl on my system and ran into this bug: > > > > As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is > > broken. You need to grab > > <http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=32cc247>; > > and apply it to the 1.0.1d source to fix it. > > > > Will this patch be applied to the port version? > > I'd like to second that. I ran into this issue as well, breaking > dovecot, postfix and nginx. Thanks to zfs snapshots I've been able > to recover within seconds ;-) I heard that the nice folks who brought us "1.0.1d" will be coming out with "1.0.1e" any day now. The key words being "any day" now. Sometimes I really wonder if anyone actually tests this software before releasing it. Usually I never update any software to a new version until it has been in use for a while. However, since this was not a major update, but just a minor letter, I figured how badly could I get burnt. Once again, lady luck bit me in the ass. By the way, there is now a PR filed against it. Hopefully something will be done to correct the problem. I had to revert everything back to the old version. More time lost ... -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130208165235.0dc7ac68>