Date: Fri, 22 Sep 2023 17:49:41 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 274027] dns/void-zones-tools: Now kills unbound. Needs to be updated from upstream. Message-ID: <bug-274027-7788-xYAlknmuYh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274027-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-274027-7788@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=3D274027 --- Comment #1 from Robert William Vesterman <bob@vesterman.com> --- For the benefit of anyone else who may run=20 into this problem, here's what I've done on my machine as a workaround until the port can be updated: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D (1) Deleted /usr/local/etc/void-zones-tools/mdl_void_hosts.txt, which is the problematic file that void-zones-tools retrieves from malwaredomainlist.com. The next time the update script is run, though, it would just recreate the file, so: (2) Copied the update script, /usr/local/bin/void-zones-update.sh, to /usr/local/bin/void-zones-update.bobmodtmp.sh. (3) Modified the new /usr/local/bin/void-zones-update.bobmodtmp.sh as follo= ws, getting rid of references to mdl_void_hosts.txt, so that the update script won't recreate the file: $ diff void-zones-update.sh void-zones-update.bobmodtmp.sh 64d63 < $FETCH -o "$ZONES_DIR/mdl_void_hosts.txt"=20=20=20=20=20 "http://www.malwaredomainlist.com/hostslist/hosts.txt" 83,86d81 < if [ ! -f "$ZONES_DIR/mdl_void_hosts.txt" ] ; then < echo "# No hosts from mdl." > "$ZONES_DIR/mdl_void_hosts.txt" < fi < 109d103 < "$ZONES_DIR/mdl_void_hosts.txt" \ $ (4) To get unbound to start up, modified /usr/local/etc/unbound.conf by commenting out the line that makes unbound pay attention to the void zones list: # include: /var/unbound/local-void.zones (5) Started up unbound. (6) Ran /usr/local/bin/void-zones-update.bobmodtmp.sh. (7) Backed out the change to /usr/local/etc/unbound.conf, so that it will go back to paying attention to the void zones list: include: /var/unbound/local-void.zones (8) Restarted unbound. (9) Changed my cron job that runs the void zones update script to run my new one instead: #37 07 * * * (/usr/local/bin/void-zones-update.sh; service unbound restart)= | mail -s "Void zones update" bob@vesterman.com 37 07 * * * (/usr/local/bin/void-zones-update.bobmodtmp.sh; service unbound restart) | mail -s "Void zones update (with bonus kludginess\!)" bob@vesterman.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D When the port is updated, you can just change your cron job back to use the normal /usr/local/bin/void-zones-update.sh script. At that point you could = also delete the modified one (/usr/local/bin/void-zones-update.bobmodtmp.sh), but doing so isn't really necessary. --=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-274027-7788-xYAlknmuYh>