Just in case there was something botched in my local builds, I updated the sparc system from the latest nightly builds of netbsd-7 and netbsd-8.
The behavior is the same. Both netbsd-[78]/sparc produce a bad DNSSEC DS hash (the first line): . IN DS 20326 8 1 42CAD163F25D96B28A8413628A2EBEBC8341B1CD . IN DS 20326 8 2 E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D Some time in the 8.99.* period leading to netbsd-9, whatever the problem was on sparc seems to have been fixed and as of at least 8.99.34 (sources of 20190208093400Z) the DNSSEC DS hashes: . IN DS 20326 8 1 AE1EA5B974D4C858B740BD03E3CED7EBFCBD1724 . IN DS 20326 8 2 E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D agree with those produced by netbsd-[89]/amd64 and netbsd-9/sparc. This one sparc system is the only machine I still run netbsd-7 or -8 on. everything else has been updated to -9 or -current. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSD FreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
