OPNsense Forum

Archive => 15.7 Legacy Series => Topic started by: Tikimotel on October 20, 2015, 05:40:54 pm

Title: Unbound updated already to 1.5.6
Post by: Tikimotel on October 20, 2015, 05:40:54 pm

I just updated to 15.7.17 today (20th of October)

And checked the release announcement info.
Unbound has already been updated again, to higher version than 1.5.5 to 1.5.6

Copy-past from unbound.net website:

Download: unbound-1.5.6.tar.gz
SHA1 checksum: b1e521669d6e5a3c1baf8b71dad070e38887162b
SHA256 checksum: ad3823f5895f59da9e408ea273fcf81d8a76914c18864fba256d7f140b83e404
PGP signature: unbound-1.5.6.tar.gz.asc
Date: 20 October, 2015

Default for ssl-port is port 853, the temporary port assignment for secure domain name system traffic. If you used to rely on the older default of port 443, you have to put a clause in unbound.conf for that. The new value is likely going to be the standardised port number for this traffic.
ANY responses include DNAME records if present, as per Evan Hunt's remark in dnsop.

Bug Fixes
Fix segfault in the dns64 module in the formaterror error path.
Fix manpage to suggest using SIGTERM to terminate the server.
iana portlist update.
Title: Re: Unbound updated already to 1.5.6
Post by: franco on October 20, 2015, 06:01:21 pm
Hi Tikimodel,

we usually wait for FreeBSD ports to cope, as of this writing, unbound is still at 1.5.5 for them. Should it not be updated in time for 15.7.18 next week we'll pick it up and try to get it upstream (but usually it won't be necessary given a few more days). :)