TTL bounds: improve the logic
- apply to first (uncached) answer already - don't extend over signature validity Nit: the tests were using too high TTL (RFCs disallow the "sign bit"). It was working because (manual) cache-insertion was applying bounds, but now the bounds don't get applied anymore, so it would fail.
Showing
- daemon/cache.test/insert_ns.test.integr/kresd_config.j2 1 addition, 1 deletiondaemon/cache.test/insert_ns.test.integr/kresd_config.j2
- lib/cache/api.c 1 addition, 4 deletionslib/cache/api.c
- lib/cache/api.h 1 addition, 1 deletionlib/cache/api.h
- lib/dnssec.c 16 additions, 8 deletionslib/dnssec.c
- lib/dnssec.h 1 addition, 0 deletionslib/dnssec.h
- lib/layer/iterate.c 20 additions, 2 deletionslib/layer/iterate.c
- lib/layer/validate.c 2 additions, 0 deletionslib/layer/validate.c
- modules/policy/policy.rpz.test.lua 1 addition, 1 deletionmodules/policy/policy.rpz.test.lua
Please register or sign in to comment