Package: knot / 2.7.6-2

Metadata

Package Version Patches format
knot 2.7.6-2 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
0001 avoid git version inclusion in debian packages.patch | (download)

m4/knot-version.m4 | 5 1 + 4 - 0 !
1 file changed, 1 insertion(+), 4 deletions(-)

 avoid git version inclusion in debian packages


0002 zonefile Verify mtime against full precision timesta.patch | (download)

src/knot/events/handlers/load.c | 6 4 + 2 - 0 !
src/knot/zone/zone.c | 2 1 + 1 - 0 !
src/knot/zone/zone.h | 2 1 + 1 - 0 !
src/knot/zone/zonedb-load.c | 6 4 + 2 - 0 !
src/knot/zone/zonefile.c | 4 2 + 2 - 0 !
src/knot/zone/zonefile.h | 2 1 + 1 - 0 !
6 files changed, 13 insertions(+), 9 deletions(-)

 zonefile: verify mtime against full-precision timestamp

We've just used 1-second granularity mtime to check if a file has
changed.

But if two updates happen within a calendar second, and knotd notices
the first one and reloads the file, it might never notice the second
change and continue serving the old file.  We can see this happening
in intermittent test suite failures in the debian continuous
integration servers:

    https://ci.debian.net/packages/k/knot/unstable/amd64

Using nanosecond-granularity timestamps should make these problems go
away.

Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

0003 correct kdig documentation about no crypto.patch | (download)

doc/man/kdig.1in | 2 1 + 1 - 0 !
doc/man_kdig.rst | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

 correct kdig documentation about +[no]crypto

kdig displays cryptographic signatures and keys in base64 encoding,
not in hexdump format.

Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>