as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
evutil_secure_rng_add_bytes became nop in r478104 on all FreeBSD
releases due to a bug in arc4random_addrandom ifdef. libevent 2.1.10
hidden it based on configure check. Looks like there were consumers.
PR: 238433
Reported by: yuri
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Port changes:
* Add USES=compiler:c11
* Add USE_CSTD=gnu99
Situation with MIPS isn't clear, Nathan <ndowens@yahoo.com> says that it works only after adding USES=autoreconf.
The Tor Project should resolve this discrepancy that autoreconf alters the outcome: https://trac.torproject.org/projects/tor/ticket/27901
PR: 231779
Submitted by: Piotr Kubaj <pkubaj@anongoth.pl> (initial version)
Backport of countermeasures to mitigate denial-of-service
attacks against the Tor network.
Changelog is in:
https://gitweb.torproject.org/tor.git/tree/ChangeLog
None of these fixes appear to be essential for clients, but relays
should upgrade.
Port changes:
* Changed the implementation of 'tor_setuid': now it is done through
the command line argument, instead of the torrc file.
Reported by: Nick Mathewson <nickm@torproject.org> (notification)
Approved by: tcberner (mentor, implicit)
This release contains many new features and many bugfixes.
Plesee see the complete list here:
https://blog.torproject.org/tor-0329-released-we-have-new-stable-series
Additionally, this update adds "#include <osreldate.h>" to qualm the
compiler warning that was caused by the previous fix.
Now security/tor and security/tor-devel are identical.
Submitted by: myself
Reported by: upstream notification
Approved by: adamw (mentor)
Differential Revision: https://reviews.freebsd.org/D13820
timingsafe_memcmp(3) has only been introduced in 12, therefore limiting its use to 12.
Reported by: Martin Gehlen <zitlo@zitlo.de> (bug reporter)
Approved by: adamw (mentor)
Differential Revision: https://reviews.freebsd.org/D13502
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
*The user should add tor_setuid=YES to /etc/rc.conf
to make tor do setuid in runtime after opening the
externally provided files.
PR: 218587
Submitted by: xmj
Approved by: Yuri Victorovich <yuri at rawbw.com> (maintainer)
Approved by: miwi (mentor)
Differential Revision: https://reviews.freebsd.org/D11223
- rc.d commands now accept optional instance argument
- `status` command output is no longer ambigous
before:
$ service tor status
tor is running as pid 22222.
tor is running as pid 33333.
tor is running as pid 11111.
after:
$ service tor status
tor instance inst1: tor is running as pid 22222.
tor instance inst2: tor is running as pid 33333.
tor main instance: tor is running as pid 11111.
$ service tor restart inst1
tor instance inst1: Stopping tor.
Waiting for PIDS: 22222.
Starting tor.
[...]
PR: 207129
Submitted by: Yuri Victorovich <yuri@rawbw.com> (maintainer)
