Tool to prepare a list of void zones that can be readily fed into Unbound.
Void zones are the most straightforward way of blocking ad, tracking and other
malware domains.
===> The following configuration options are available for void-zones-tools-1.0.2.18_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
To download the host lists and convert them to void zones,
run the following script:
/usr/local/bin/void-zones-update.sh
To add your own white list/black list entries, to add over override
the bundled listings, edit /usr/local/etc/void-zones/my_void_hosts.txt.
Use the IP address 1.1.1.1 for whitelisting, and 0.0.0.0 for blacklisting.
Add the following line to your unbound.conf, prior to any forwarder directives:
include: /var/unbound/local-void.zones
Then restart Unbound.
For future updates, run void-zones-update.sh and restart Unbound.
For more information, see /usr/local/share/doc/void-zones-tools/README.md
or https://github.com/cyclaero/void-zones-tools
dns/void-zones-tools: Fix build with WITH_PIE=YES
Patch CFLAGS from being overridden and remove -fno-pic to facilitate
building with WITH_PIE=yes
PR: 275039
Reported by: Marek Zarychta
dns/void-zones-tools: fix unbound-killing bug
void-zones-tools downloads a set of pre-defined lists of undesirable
domains and creates "voided" dns zones for Unbound, blocking access to
these domains via dns.
One of the default lists is no longer maintained, and was removed from
the upstream code. However, there hasn't been released a new version
after the change was made, thus the port has not been updated.
This has not been a problem up until now because the update script has
been downloading an empty file, essentially a no-op in the zone
creation/loading, but at some point today it started serving a domain
parking page, and the HTML of that page is being dumped into the dns
zone file resulting in parse errors and Unbound cannot start.
While waiting for upstream to tag a new version, I changed the port to
track the latest GitHub commit. This fixes the issue for now.
PR: 274027
Upstream issue: https://github.com/cyclaero/void-zones-tools/issues/12
Reported by: Robert William Vesterman <bob@vesterman.com>
MFH: 2023Q3
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISION for ports depending on the canonical version of GCC
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
Bump PORTREVISION for ports depending on the canonical version of GCC
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
dns/void-zones-tools: Respect CFLAGS and avoid using -march=native
It currently compiles with -march=native which breaks on some
machines
cc -march=native -mssse3 -ffast-math -std=c11 -g0 -Ofast -fstrict-aliasing
-Wno-parentheses binutils.c -c -o binutils.o
error: unknown target CPU 'k6-3'
Given that the build is currently targeting the build host CPU,
existing binary packages on pkg.FreeBSD.org (or elsewhere) might
be broken on many machines too, so bump PORTREVISION to trigger a
rebuild.
PR: 230899
Submitted by: tobik
Reported by: Marco Beishuizen <mbeis@xs4all.nl>
Approved by: Vidar Karlsen <vidar@karlsen.tech> (maintainer)
MFH: 2018Q3
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
Bump PORTREVISION for ports depending on the canonical version of GCC
(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
dns/void-zones-tools: Update to 1.0.2
- Use Github release
- Remove `files/patch-Makefile`, not necessary anymore.
- Fixes for building on ARM and i386 architectures
- WindowsSpyBlocker is the new upstream for the Windows
telemetry hosts files
PR: 217054
Submitted by: Vidar Karlsen <vidar@karlsen.tech> (maintainer)
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
