Kali update: The primary key is not live

Kali template update fails:

sudo apt-get update
Hit:1 https://deb.debian.org/debian bookworm InRelease
Hit:3 https://deb.qubes-os.org/r4.2/vm trixie InRelease             
Hit:4 https://deb.debian.org/debian-security bookworm-security InRelease
Get:2 http://ftp.belnet.be/pub/kali/kali kali-rolling InRelease [41.5 kB]
Err:2 http://ftp.belnet.be/pub/kali/kali kali-rolling InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 44C6513A8E4FB3D30875F758ED444FF07D8D0BF6 is bad:            The primary key is not live   because: Expired on 2025-01-24T12:47:10Z
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.belnet.be/pub/kali/kali kali-rolling InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 44C6513A8E4FB3D30875F758ED444FF07D8D0BF6 is bad:            The primary key is not live   because: Expired on 2025-01-24T12:47:10Z
E: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 44C6513A8E4FB3D30875F758ED444FF07D8D0BF6 is bad:            The primary key is not live   because: Expired on 2025-01-24T12:47:10Z
E: Some index files failed to download. They have been ignored, or old ones used instead.

any advice?

There is certainly a better fix, but given the key expired less than 1 week ago, you could try to set the qube’s date to the 23th of this month and update, it should get the new keys.

I think the template should be updated by the maintainer to get that new key because the workaround above will not work for long.

1 Like