Hi Sliim,
I thought I would point out that the gpg key in the 2017.2 images has expired.
Kali upstream updated their keys with a new expiry date, which has been pushed out (new version of kali-archive-keyring should be 2018.1). The problem is that you have to update your key manually if you didn't get the debian package on time. Meaning the system won't update at that point anymore.
Maybe you could publish a new version with the new keyring?
Manual workaround that worked for me:
gpg --list-keys --keyring /usr/share/keyrings/kali-archive-keyring.gpg # to verify key id
gpg --keyring /usr/share/keyrings/kali-archive-keyring.gpg --keyserver hkp://keys.gnupg.net --recv-keys 44C6513A8E4FB3D30875F758ED444FF07D8D0BF6
Hi Sliim, I thought I would point out that the gpg key in the 2017.2 images has expired.
Kali upstream updated their keys with a new expiry date, which has been pushed out (new version of kali-archive-keyring should be 2018.1). The problem is that you have to update your key manually if you didn't get the debian package on time. Meaning the system won't update at that point anymore.
Maybe you could publish a new version with the new keyring?
Manual workaround that worked for me: gpg --list-keys --keyring /usr/share/keyrings/kali-archive-keyring.gpg # to verify key id gpg --keyring /usr/share/keyrings/kali-archive-keyring.gpg --keyserver hkp://keys.gnupg.net --recv-keys 44C6513A8E4FB3D30875F758ED444FF07D8D0BF6
Cheers, octes