Couldn't read key from Kdhcpkey.*.key: unexpected token #7

Closed
opened 2023-07-21 22:04:53 +02:00 by sf · 1 comment
Owner

After upgrade bind9 to 1:9.18.16-1~deb12u1 dnsvi can't use the keyfile in config or on command line.

root@s920:~# dnsvi fritz.box
Couldn't read key from /root/.dnsvi/default/Kdhcpkey.+157+00214.key: unexpected token
nothing changed
root@s920:~#

root@s920:/etc/bind# ls Kdhcpkey*
Kdhcpkey.+157+00214.key  Kdhcpkey.+157+00214.private

root@s920:/etc/bind# dnsvi -k Kdhcpkey.+157+00214.key fritz.box
Couldn't read key from Kdhcpkey.+157+00214.key: unexpected token

root@s920:/etc/bind# cat Kdhcpkey.+157+00214.key
dhcpkey. IN KEY 512 3 157 ESB....==

I'm not sure if the key format is obsolete.

After upgrade bind9 to 1:9.18.16-1~deb12u1 dnsvi can't use the keyfile in config or on command line. ``` root@s920:~# dnsvi fritz.box Couldn't read key from /root/.dnsvi/default/Kdhcpkey.+157+00214.key: unexpected token nothing changed root@s920:~# root@s920:/etc/bind# ls Kdhcpkey* Kdhcpkey.+157+00214.key Kdhcpkey.+157+00214.private root@s920:/etc/bind# dnsvi -k Kdhcpkey.+157+00214.key fritz.box Couldn't read key from Kdhcpkey.+157+00214.key: unexpected token root@s920:/etc/bind# cat Kdhcpkey.+157+00214.key dhcpkey. IN KEY 512 3 157 ESB....== ``` I'm not sure if the key format is obsolete.
Author
Owner
fixed by new key. see https://gitea.schlittermann.de/IUS/dnsvi/issues/5
sf closed this issue 2023-07-22 20:56:12 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
IUS/dnsvi#7
No description provided.