On Tue, Feb 25, 2014 at 08:57:08AM +1100, Mark Andrews wrote:
> SIGCHASE is a external contribution that is provide "as is" to dig.
> The reason that you have to explicitly define it is that ISC hasn't
> fully gone through the code to find bugs like this in it and it
> basically needs a full re-wri
=97
> Raymond Walker
> Software Systems Engineer StSp.
> ITS - Northern Arizona University
>
> From: Ray Walker mailto:ray.wal...@nau.edu>>
> Date: Friday, February 21, 2014 at 4:28 PM
> To: "bind-users@lists.isc.org<mailto:bind-users@lists.isc.org>&q
From: Ray Walker mailto:ray.wal...@nau.edu>>
Date: Friday, February 21, 2014 at 4:28 PM
To: "bind-users@lists.isc.org<mailto:bind-users@lists.isc.org>"
mailto:bind-users@lists.isc.org>>
Subject: dig +sigchase looping
I’m experiencing an interesting issue where sometimes
I’m experiencing an interesting issue where sometimes when performing a
sigchase on a valid signed zone the command loops indefinitely when an expired
RRSIG exists:
Live example:
dig +sigchase +trusted-key=./trusted.keys aa.nau.edu A
Notes:
There is currently a valid RRSIG for this zone.
dig co
4 matches
Mail list logo