Update Not Working

[Flika]

I just installed KL on my USB drive with persistence. However, I used an old version ISO I had on my laptop, because the hard drive on that laptop is incredibly slow and I didn't want to spend an hour and a half downloading the latest ISO. So I used the old one, version 2017.3, thinking I could just update it when I got it up and running. I get on and try to use the apt-get update commands, and get the following output:

Get:1 http://archive.linux.duke.edu/kalilinux/kali kali-rolling InRelease [30.5 kB]
Err:1 http://archive.linux.duke.edu/kalilinux/kali kali-rolling InRelease
  The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <[email protected]>
Fetched 30.5 kB in 0s (44.8 kB/s)
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://archive.linux.duke.edu/kalilinux/kali kali-rolling InRelease: The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <[email protected]>
W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease  The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.

I updated the sources.list file with the "regular repositories" link on the official site: https://docs.kali.org/general-use/ka...t-repositories But still got the error. I don't know what is causing it, and need some help getting it resolved. Thanks!

[bigbiz]

I just installed KL on my USB drive with persistence. However, I used an old version ISO I had on my laptop, because the hard drive on that laptop is incredibly slow and I didn't want to spend an hour and a half downloading the latest ISO. So I used the old one, version 2017.3, thinking I could just update it when I got it up and running. I get on and try to use the apt-get update commands, and get the following output:

Get:1 http://archive.linux.duke.edu/kalilinux/kali kali-rolling InRelease [30.5 kB]
Err:1 http://archive.linux.duke.edu/kalilinux/kali kali-rolling InRelease
  The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <[email protected]>
Fetched 30.5 kB in 0s (44.8 kB/s)
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://archive.linux.duke.edu/kalilinux/kali kali-rolling InRelease: The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <[email protected]>
W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease  The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.

I updated the sources.list file with the "regular repositories" link on the official site: https://docs.kali.org/general-use/ka...t-repositories But still got the error. I don't know what is causing it, and need some help getting it resolved. Thanks!

I think what your looking for gos like this

apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6

If it still not work

apt-key list

Then try all the expired ones, sometimes the order you try to update them is essential.

[Flika]

I think what your looking for gos like this

apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6

If it still not work

apt-key list

Then try all the expired ones, sometimes the order you try to update them is essential.

Thanks! This worked!

[Flika]

I think what your looking for gos like this

apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6

If it still not work

apt-key list

Then try all the expired ones, sometimes the order you try to update them is essential.

How do I get the key IDs form the list? i don't see any listed ID, and everything I try comes back with invalid key

(I installed it on another USB and am having the same issue, but it the first command didn't fix it)