Summary: | security/tor: Update to 0.2.8.11 | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Neel Chauhan <nc> | ||||
Component: | Individual Port(s) | Assignee: | Dmitry Marakasov <amdmi3> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Many People | CC: | pi, yuri | ||||
Priority: | --- | Flags: | yuri:
maintainer-feedback+
|
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
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 ? Btw, testbuilds on cur 11a 10i 93a all fine. Sorry, clicked the wrong "save" button A commit references this bug: Author: amdmi3 Date: Thu Dec 15 10:10:22 UTC 2016 New revision: 428609 URL: https://svnweb.freebsd.org/changeset/ports/428609 Log: - Update to 0.2.8.11 PR: 215183 Submitted by: neel@neelc.org Approved by: yuri@rawbw.com (maintainer) Changes: head/security/tor/Makefile head/security/tor/distinfo |
Created attachment 177834 [details] Patch to update security.tor to 0.2.8.11 This port builds on FreeBSD 11.0 amd64.