it worked for long time, up till package version 1:9.18.1-1ubuntu1.3
but since upgrading to 1:9.18.12-0ubuntu0.22.04.1 , it stopped working with nsupdate giving out the following :
Creating key...
could not read key from /etc/bind/Khost.+157+35878.{private,key}: file not found
in strace printout, I see that nsupdate successfully opens .private key file but then checks existence of the same file name without suffix (as specified after nsupdate -k) and fails.
were there any changes in key parsing from 9.18.1 to 9.18.13 ?
reverting bind9-utils, bind9-dnsutils and bind9-libs back to 1:9.18.1-1ubuntu1.3 restored the desired behavior.
please advise if I should fix the key format after the upgrade, or if this is a regression to be fixed from your side.
I have a key with the following contents (key material replaced with ...) :
+ cat /etc/bind/ Khost.+ 157+35878. key
host. IN KEY 0 3 157 YSp... ...QsQ==
+ cat /etc/bind/ Khost.+ 157+35878. private
Private-key-format: v1.3
Algorithm: 157 (HMAC_MD5)
Key: YSp......QsQ==
Bits: AAA=
Created: 20180616045813
Publish: 20180616045813
Activate: 20180616045813
it worked for long time, up till package version 1:9.18.1-1ubuntu1.3 12-0ubuntu0. 22.04.1 , it stopped working with nsupdate giving out the following :
but since upgrading to 1:9.18.
Creating key... Khost.+ 157+35878. {private, key}: file not found
could not read key from /etc/bind/
in strace printout, I see that nsupdate successfully opens .private key file but then checks existence of the same file name without suffix (as specified after nsupdate -k) and fails.
were there any changes in key parsing from 9.18.1 to 9.18.13 ?
reverting bind9-utils, bind9-dnsutils and bind9-libs back to 1:9.18.1-1ubuntu1.3 restored the desired behavior.
please advise if I should fix the key format after the upgrade, or if this is a regression to be fixed from your side.