Re: DNSSEC vs netbsd-8/sparc?

[Sad Clouds <cryintothebluesky%gmail.com@localhost>]

On Tue, 21 Apr 2020 08:25:47 -0400
Greg Troxel <gdt%lexort.com@localhost> wrote:

> Sad Clouds <cryintothebluesky%gmail.com@localhost> writes:
> 
> > On Tue, 21 Apr 2020 09:47:45 +0200 (CEST)
> > Havard Eidnes <he%NetBSD.org@localhost> wrote:
> >
> >> So now I'm a bit confused where this error comes from.  Its root
> >> cause does not seem to be the in-tree compiler (the "standalone"
> >> BIND releases I've built are built with "-g -O2"), and it's not
> >> the original BIND code either by the looks of it, as this is the
> >> same code which is in netbsd-8.
> >
> > I don't fully understand DNSSEC and how the hash is generated, but
> > could it be due to bit rot, i.e. when you created install image,
> > some bytes of code/data somewhere could have been corrupted. Maybe
> > even source files are corrupted somewhere when you downloaded them?
> > Have you tried fresh checkout and rebuilding the same code again,
> > and if yes, do you reliably get the same hash mismatch? 
> 
> Does anybody think that the bind bits in netbsd-8 are ok, even before
> we talk about compilation?

Well the original poster mentioned he had this issue with BIND-9.10.5-P1
on NetBSD-8 sparc. He then got the same version of BIND from ISC and
built it on the same machine, this time checksum was correct and the
issue went away.

Not sure if BIND in NetBSD differs in any way from ISC version. If no
difference and different people can reproduce the issue, then something
somewhere got corrupted, either source code or binary images.