]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
silence a spurious dnssec-keygen warning in the dnssec system test
authorEvan Hunt <each@isc.org>
Sat, 15 Dec 2018 00:58:54 +0000 (16:58 -0800)
committerEvan Hunt <each@isc.org>
Thu, 31 Jan 2019 21:23:11 +0000 (13:23 -0800)
the occluded-key test creates both a KEY and a DNSKEY. the second
call to dnssec-keygen calls dns_dnssec_findmatchingkeys(), which causes
a spurious warning to be printed when it sees the type KEY record.
this should be fixed in dnssec.c, but the meantime this change silences
the warning by reversing the order in which the keys are created.

bin/tests/system/dnssec/ns3/sign.sh

index 7555c9fe047026c942ea870fbcb9954f960882fe..390dadb7d8974410be4e0f73570ef067f3bf6df5 100644 (file)
@@ -602,8 +602,8 @@ infile=occluded.example.db.in
 zonefile=occluded.example.db
 kskname=$("$KEYGEN" -q -a "$DEFAULT_ALGORITHM" -fk "$zone")
 zskname=$("$KEYGEN" -q -a "$DEFAULT_ALGORITHM" "$zone")
-keyname=$("$KEYGEN" -q -a RSASHA1 -n ENTITY -T KEY "delegation.$zone")
 dnskeyname=$("$KEYGEN" -q -a "$DEFAULT_ALGORITHM" -fk "delegation.$zone")
+keyname=$("$KEYGEN" -q -a DH -b 1024 -n HOST -T KEY "delegation.$zone")
 $DSFROMKEY "$dnskeyname.key" > "dsset-delegation.${zone}$TP"
 cat "$infile" "${kskname}.key" "${zskname}.key" "${keyname}.key" \
     "${dnskeyname}.key" "dsset-delegation.${zone}$TP" >"$zonefile"