Kevin Darbyshire-Bryant
2016-05-27 12:37:12 UTC
Hi Simon,
Please could you consider the attached patch. It solves a problem that
using dnssec-timestamp also effectively enabled dnssec-no-timecheck.
The result of which is that an unfortunately timed SIGHUP could
accidentally enable dnssec timestamp checking. In combination with
dnssec-check-unsigned that could prove 'challenging' :-)
The patch matches the behaviour is as documented in the manpage.
kind regards,
Kevin
Please could you consider the attached patch. It solves a problem that
using dnssec-timestamp also effectively enabled dnssec-no-timecheck.
The result of which is that an unfortunately timed SIGHUP could
accidentally enable dnssec timestamp checking. In combination with
dnssec-check-unsigned that could prove 'challenging' :-)
The patch matches the behaviour is as documented in the manpage.
kind regards,
Kevin