Date: Tue, 13 Dec 2016 19:51:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 215183] security/tor: Update to 0.2.8.11 Message-ID: <bug-215183-13-1io2yhtJTR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215183-13@https.bugs.freebsd.org/bugzilla/> References: <bug-215183-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215183 Kurt Jaeger <pi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pi@FreeBSD.org --- Comment #1 from Kurt Jaeger <pi@FreeBSD.org> --- The changelog says: Changes in version 0.2.8.11 - 2016-12-08 Tor 0.2.8.11 backports fixes for additional portability issues that could prevent Tor from building correctly on OSX Sierra, or with OpenSSL 1.1. Affected users should upgrade; others can safely stay with 0.2.8.10. o Minor bugfixes (portability): - Avoid compilation errors when building on OSX Sierra. Sierra began to support the getentropy() and clock_gettime() APIs, but created a few problems in doing so. Tor 0.2.9 has a more thorough set of workarounds; in 0.2.8, we are just using the /dev/urandom and mach monotonic time interfaces. Fixes bug 20865. Bugfix on 0.2.8.1-alpha. o Minor bugfixes (portability, backport from 0.2.9.5-alpha): - Fix compilation with OpenSSL 1.1 and less commonly-used CPU architectures. Closes ticket 20588. So this update is not really needed for FreeBSD right now, is it ? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215183-13-1io2yhtJTR>