Unbound 1.4.15 release

Unbound
1

Hi,

Unbound 1.4.15 is available:
http://unbound.net/downloads/unbound-1.4.15.tar.gz
sha1: bbda46664ea8391ca7986300ce98a79787c0e322
sha256: 729d427c00c160de4ee66945d762b3282677e957407450152088369216a30020

The release is about bugfixes, the memory leak fix and hash function
change are the most important.

- - Fix for memory leak (about 20 bytes when a tcp or udp send operation
towards authority servers failed, takes about 50.000 such failures to
leak one Mb, such failures are also usually logged), reported by Robert
Fleischmann.
- - Fix to randomize hash function, based on 28c3 congress, reported
by Peter van Dijk.
- - #425 unbound reports wrong TTL in reply, it reports a TTL
that would be permissible by the RFCs but it is not the TTL in the cache.
- - #429 add ub_version() call to libunbound. API version increase,
with (binary) backwards compatibility for the previous version.
- - Fix bug where canonical_compare of RRSIG did not downcase the
signer-name. This is mostly harmless because RRSIGs do not have
to be sorted in canonical order, usually.
- - uninitialised variable in reprobe for rtt blocked domains fixed.
- - iana portlist updated.

Best regards,
   Wouter

2

W.C.A. Wijngaards wrote:

- #429 add ub_version() call to libunbound. API version increase,
with (binary) backwards compatibility for the previous version.

i understand this to mean that the SONAME should not have changed on glibc
platforms:

    LIBUNBOUND_CURRENT=3
    LIBUNBOUND_REVISION=0
    LIBUNBOUND_AGE=1
    # 1.0.0 had 0:12:0
    [...13 lines...]
    # 1.4.1 had 2:1:0
    [...13 lines...]
    # 1.4.14 had 2:14:0

so, the SONAME should still be 'libunbound.so.2', since CURRENT minus
AGE is still 2. however, when i built unbound 1.4.15 the SONAME was
instead 'libunbound.so.3'.

i believe this is due to the use of libtool's "-version-number" (which
takes a major:minor:revision argument) vs "-version-info" (which takes a
current:revision:age argument).

the attached patch changes from -version-number to -version-info.
however, with -version-info 3:0:1, this results in the .so receiving a
filename of "libunbound.so.2.1.0", which is identical to the .so
filename generated by unbound 1.4.1 ("-version-number 2:1:0").

(attachments)

0001-Makefile.in-use-version-info-not-version-number.patch (2.72 KB)

3

Hi Robert,

4

Hi Paul,