Package: knot / 2.7.6-2
Patch seriesview the series file
|0001 avoid git version inclusion in debian packages.patch | (download)||
5 1 + 4 - 0 !
avoid git version inclusion in debian packages
|0002 zonefile Verify mtime against full precision timesta.patch | (download)||
6 4 + 2 - 0 !
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 <email@example.com>
|0003 correct kdig documentation about no crypto.patch | (download)||
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 <firstname.lastname@example.org>