Ошибка репозитория kali linux - Не ошибается лишь тот, кто ничего не делает!

Luda_

Kali linux 2017.3 не могу обновить драйвер nvidia
apt-get update
apt-get dist-upgrade
apt-get install -y linux-headers-$(uname -r)
apt-get install nvidia-kernel-dkms
Выдаёт ошибку:

Bash:

root@Brut:~# apt-get update
Игн:1 cdrom://[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49] kali-rolling InRelease
Ошк:2 cdrom://[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49] kali-rolling Release
  Пожалуйста, используйте apt-cdrom, чтобы APT смог распознать данный CD. apt-get update не используется для добавления нового CD
Пол:3 http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease [30,5 kB]
Ошк:3 http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease
  Следующие подписи неверные: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
Чтение списков пакетов… Готово
E: Репозиторий «cdrom://[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49] kali-rolling Release» не содержит файла Release.
N: Обновление из этого репозитория нельзя выполнить безопасным способом, и поэтому по умолчанию он отключён.
N: Смотрите справочную страницу apt-secure(8) о создании репозитория и настройке пользователя.
W: Произошла ошибка при проверке подписи. Репозиторий не обновлён и будут использованы предыдущие индексные файлы. Ошибка GPG: http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease: Следующие подписи неверные: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>

Вот мой sources.list...
[CODE]deb cdrom:[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49]/ kali-rolling contrib main $
#deb cdrom:[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49]/ kali-rolling contrib main$

deb http://http.kali.org/kali kali-rolling main non-free contrib
# deb-src http://http.kali.org/kali kali-rolling main non-free contrib

r0hack

Bash:

root@Brut:~# apt-get update
Игн:1 cdrom://[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49] kali-rolling InRelease
Ошк:2 cdrom://[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49] kali-rolling Release
  Пожалуйста, используйте apt-cdrom, чтобы APT смог распознать данный CD. apt-get update не используется для добавления нового CD
Пол:3 http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease [30,5 kB]
Ошк:3 http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease
  Следующие подписи неверные: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
Чтение списков пакетов… Готово
E: Репозиторий «cdrom://[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49] kali-rolling Release» не содержит файла Release.
N: Обновление из этого репозитория нельзя выполнить безопасным способом, и поэтому по умолчанию он отключён.
N: Смотрите справочную страницу apt-secure(8) о создании репозитория и настройке пользователя.
W: Произошла ошибка при проверке подписи. Репозиторий не обновлён и будут использованы предыдущие индексные файлы. Ошибка GPG: http://kali.mirror.garr.it/mirrors/kali kali-rolling InRelease: Следующие подписи неверные: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>

Вот мой sources.list...
[CODE]deb cdrom:[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49]/ kali-rolling contrib main $
#deb cdrom:[Debian GNU/Linux 2017.3 _Kali-rolling_ - Official Snapshot amd64 LIVE/INSTALL Binary 20171109-13:49]/ kali-rolling contrib main$

deb http://http.kali.org/kali kali-rolling main non-free contrib
# deb-src http://http.kali.org/kali kali-rolling main non-free contrib

Оставь только эту репу и попробуй снова обновить: deb http://http.kali.org/kali kali-rolling main contrib non-free

Напиши это:

Код:

gpg --keyserver hkp://keys.gnupg.net --recv-key 7D8D0BF6
gpg -a --export ED444FF07D8D0BF6 | sudo apt-key add -

Luda_

Напиши это:

Код:

gpg --keyserver hkp://keys.gnupg.net --recv-key 7D8D0BF6
gpg -a --export ED444FF07D8D0BF6 | sudo apt-key add -

Благодарю,помогло)

—- Добавлено позже —-

Напиши это:

Код:

gpg --keyserver hkp://keys.gnupg.net --recv-key 7D8D0BF6
gpg -a --export ED444FF07D8D0BF6 | sudo apt-key add -

Можешь обьяснить что это и как это работает?

Последнее редактирование модератором: 04.02.2018

Напиши это:

Код:

gpg --keyserver hkp://keys.gnupg.net --recv-key 7D8D0BF6
gpg -a --export ED444FF07D8D0BF6 | sudo apt-key add -

Мне тоже помогло! Спасибо!

Можешь обьяснить что это и как это работает?

Это связано с тем, что у тебя устарели ключи верификации пакетов. Что-бы увидеть их срок годности — напиши: apt-key list. Зачем это нужно можно прочитать

Ссылка скрыта от гостей

Kali7

#1
Поиск и монтирования CD-ROM Ошибка чтение файла release вероятно компакт диск не содержит правильного файла release или эт от файл был неправильного прочитан. Что делать доступ есть только оболочке
Скачал на сайте

Ссылка скрыта от гостей

Установил вместе windows 7 через multiboot kali linux не могу переключатся(переходит) на windows 7
По этому доступ есть оболочке и системного bios компьютера

centr

Недавно столкнулся с таким явлением( захожу редко, бывает кали не запускается годами), решение выше мне не помогло.
Скачал по ссылке

Ссылка скрыта от гостей

, далее apt-key add /root/archive-key.asc и оп, всё заработало.

recon

Добавляем старые ключи:

Bash:

wget 'https://archive.kali.org/archive-key.asc'
apt-key add archive-key.asc

Источник

На чтение 2 мин Опубликовано 14.06.2017

Если вы попытаетесь сделать обновление, система возможно, обновит вам несколько приложений.

А при попытке установить новое приложение с 90% вероятностью, система выдаст сообщение вида:

# E: Unable to locate package regedit

Самый простой путь решения этого вопроса состоит в том, чтобы отредактировать файл /etc/apt/sources.list:

# leafpad /etc/apt/sources.list

удалите или прокомментируйте каждую-линию с # в начале строчки и добавьте следующие:

Для Kali Linux 1.x

# Regular repositories
deb http://http.kali.org/kali kali main non-free contrib
deb http://security.kali.org/kali-security kali/updates main contrib non-free
## Source repositories
deb-src http://http.kali.org/kali kali main non-free contrib
deb-src http://security.kali.org/kali-security kali/updates main contrib non-free

Для Kali Linux 2.0

# Regular repositories
deb http://http.kali.org/kali sana main non-free contrib
deb http://security.kali.org/kali-security sana/updates main contrib non-free
# Source repositories
deb-src http://http.kali.org/kali sana main non-free contrib
deb-src http://security.kali.org/kali-security sana/updates main contrib non-free

Для Kali Linux 2016

deb http://http.kali.org/kali kali-rolling main contrib non-free
# For source package access, uncomment the following line
# deb-src http://http.kali.org/kali kali-rolling main contrib non-free

Для Kali Linux 2017.1

deb http://repo.kali.org/kali kali-rolling main non-free contrib

Сохраняем файл /etc/apt/sources.list и закрываем.

Выполняем команды очистки и обновления и следуем по вопросам системы отвечая на [Y/n?]:

# apt-get clean && apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y

Так же, может возникнуть ошибка с недостаткой места:

E: You don’t have enough free space in /var/cache/apt/archives/

Решается эта проблема командой:

# apt-get clean

Пожалуйста, не спамьте и никого не оскорбляйте.

Это поле для комментариев, а не спамбокс.

Рекламные ссылки не индексируются!

Источник

I’m running Kali Linux in WSL2. It’s a new installation (using wsl --install) but when I try to apt-get update I get the following error:

W: An error occurred during the signature verification. The repository is not updated and the previous 
index files will be used. GPG error: http://mirrors.jevincanders.net/kali kali-rolling InRelease: The 
following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease  The following signatures 
were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
W: Some index files failed to download. They have been ignored, or old ones used instead.

Now I’ve seen other questions that suggest an apt-key command to fix this. However, this throws another error:

E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation

I can’t install gnupg because I haven’t run apt update yet. What am I supposed to do here?

asked Apr 25, 2021 at 22:51

Yes, there appears to be issues with Kali Linux WSL (not downloaded from Microsoft Store).

The Kali archive keys appear to be missing and cannot be installed using apt-add key since it relies on GnuPG, which cannot be installed using apt, since the signatures cannot be verified.

The best solution is the one submitted by Jim which installed the Kali archive keys from a Debian package. Once this is done apt update and apt upgrade will work.

Download the Debian package for the Kali archive keys wget -O kali-archive-keyring_2020.2_all.deb https://http.kali.org/kali/pool/main/k/kali-archive-keyring/kali-archive-keyring_2020.2_all.deb
Install the Kali archive key package sudo dpkg -i kali-archive-keyring_2020.2_all.deb
Update list of available packages from Kali repo sudo apt update
Upgrade the WSL system sudo apt full-upgrade

answered May 25, 2021 at 3:25

kushkush

1862 bronze badges

if you encounter any 404 error messages when trying to download the keyring, please try the following:

Update 2022

for convenience reasons: the current keyring file changed, use the following commands:

# download
wget http://http.kali.org/kali/pool/main/k/kali-archive-keyring/kali-archive-keyring_2022.1_all.deb
# install
sudo dpkg -i kali-archive-keyring_2022.1_all.deb
# remove downloaded file again
rm kali-archive-keyring_2022.1_all.deb
# update
sudo apt-get update

answered Feb 16, 2022 at 10:49

kantholykantholy

3112 silver badges4 bronze badges

I did not alter /etc/apt/sources.list.

I solved the «An error occurred during the signature verification» with the following commands (run from root):

wget --no-check-certificate https://http.kali.org/kali/pool/main/k/kali-archive-keyring/kali-archive-keyring_2020.2_all.deb

dpkg -i kali-archive-keyring_2020.2_all.deb

apt update

answered Sep 30, 2021 at 16:56

Manually download and install the needed package to verify the signature:

wget https://http.kali.org/kali/pool/main/k/kali-archive-keyring/kali-archive-keyring_2020.2_all.deb
sudo dpkg -i kali-archive-keyring_2020.2_all.deb

Then apt update and apt upgrade should work as expected.

answered May 11, 2021 at 16:19

Adding a bit more to this as there is one extra step needed for me:
Windows 11 WSL kali-linux

wget --no-check-certificate https://http.kali.org/kali/pool/main/k/kali-archive-keyring/kali-archive-keyring_2020.2_all.deb

dpkg -i kali-archive-keyring_2020.2_all.deb

apt update
apt install libcrypt1
apt full-upgrade
apt autoremove

Without installing libcrypt1 first, an upgrade will lock you out of Kali.

answered Nov 15, 2021 at 22:51

Weird — the version of Kali downloaded by WSL with wsl --install is completely broken and is missing a lot of things. If you want to run Kali on WSL, download it from the Windows Store instead.

answered Apr 28, 2021 at 3:00

TheDoctor025TheDoctor025

1451 gold badge1 silver badge8 bronze badges

Windows 11 (x64)

#install wsl version 2
C:> wsl --set-default-version 2

#install kali-linux distribution
C:> wsl --install --distribution kali-linux

# get keyring 
# https will not work use http
@:~$ wget -O kali-archive-keyring_2020.2_all.deb http://http.kali.org/kali/pool/main/k/kali-archive-keyring/kali-archive-keyring_2020.2_all.deb

# use dpkg to install .deb
user@hostname:~$ sudo dpkg -i kali-archive-keyring_2020.2_all.deb

# apt update&upgrade
user@hostname:~$ sudo apt update && sudo apt upgrade

terminal screenshot

answered Feb 2, 2022 at 5:41

Here is the fix just run this

wget -q -O - https://archive.kali.org/archive-key.asc | sudo gpg --dearmor -o /usr/share/keyrings/kali-archive-keyring.gpg

Rohit Gupta

2,44713 gold badges23 silver badges32 bronze badges

answered Apr 29 at 5:22

To add the Key first we need to download it from the website of the package you are installing. For example, here we are downloading the key file to add repositories for on Kali-rolling.

Install wget if you don’t already have it using:

sudo apt install wget
After that use wget to download the key using:

wget "link-to download-the-key"
The command that worked for me was:

wget -q -O - https://archive.kali.org/archive-key.asc
The output from this should look like this:

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBE9U1CgBEAChen9+cvBS8ioHoCU6wBbL9jaIk5P7ZkPpjDsovMvimqZaozS8
fEAZM23gJlFratc+rRllV9hPZmGqhtT50RLDzC3yFOvFnJqAPvpVDO2ipQCVnJDX
0eWDhT62RDwk+FhjksEDwP7Yc4CgohdGDYQu1zTBSLL5qen3rckCnHF2OnSiKnYM
8YCIKAYMt4VRArAvivjOMspN+1xy2S8GYXX2felsu3Ir1DXvUIE7b/9sdK6MzBcq
joDH34OqX6isqAW0+K93lmVN+U4yFMzfEB74UMQNWKg39mCB0K/VfQ89ih4zvF9a
zENbFzfF0O0h09oHF4ZTaUFeI8JImp/x9FC+LveUyJot9t/xv0HVUd08Y4PgO48C
iXOTqqqm/DPF0AbHJGpTuonOsKy3/dYhk7Fvsfn02DMds+RKsukBEzypTIIIzMBF
Uwiq/GaaNRWw6lnOyE4wMmpwRa11QVDDWkMpuOr1tPV7M+EMAhZY7cyHDmRTOFL3
H0CxYnInis+k1NQikqtLxNrzWdxsXU25BMbEsAQq7aRTs7wpOnUK+yY+qTG/V5nl
J6II+/CtWJthIef22r8EYX1BQOXRggamy0nxViC3S6kjuU2Lb1qnDb/c7T9hB723
4T9yrRHJbygTvQD8BJBADgRy7+XInCp01V4nAJZSu20qopEg082SdWK9FwARAQAB
tCZLYWxpIExpbnV4IFJlcG9zaXRvcnkgPGRldmVsQGthbGkub3JnPokCVQQTAQoA
PwIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AWIQRExlE6jk+z0wh191jtRE/w
fY0L9gUCYe/xTgUJGD63pgAKCRDtRE/wfY0L9ofUD/9zichMeQ5+XxHnpHTSmUNR
9eCcis6NGIbW+hTfSxSttfCQBrxKGfYXwVcqGRIiSDp9FcfqH5UsgPOzgJzmLBLV
i0HfMRDpcCWJzk8VfWde/5Hv0P0XSx/Y+VR7PMJVOzWkF7o0kM4bITx3M5BYY08s
leoZMNZo9sSR0GdzbXoIXkuBwMG+nw0qjfsyI8Qcsi52Uk8YhdCkgaAb8vYyxMwO
qKJ6SIIENT6ycyZw4ueFZXZY/RYPJFvWZEYB0cFOMbNwlrXFUZyr4fDdPruaPlZW
zBIU8jwEE372frdRuXilJ2Q+Me9jhSxvnJegJsHDdgeLU6IDeAiaAaTzvufr3KmA
YifZ1Q20xDzdN5RZ5x3vNV9cihVb3qizSUe0y6LfpPeIPoa+ENzT4WqhP6rfMMhF
2KcwhNFP+faB+qs79YqIWnChrJNiE5HQDDgP6DY1ETmjj6Bo+DC9RyasWT5pSJYA
8rOVJ+1bE4sxlqtvDVlAdR1LwIpHeskz4o/lAMPHSNTX2WBDJdYvhT28xTC3cYlA
kcdpvBbjj7C4VqgMvsPLg13lfR/A28ADO6AxY323+OpPv6crsDbYOcIBpwBgHb96
AYyottiEfNnLBCysR/m34TdlYvFW0KDYsbMYLCJH/uzJK3l8TCdVBfkzDMMctSFV
nFY/xHhDFweArXNHru2CJLkCDQRPVNQoARAAoMOCt6yDngNUawaFLqFzzkQ2UDt1
LyWMM5qRusYmVW7DbMqRgl816AhW3qGXlpET2QDK/C7np8kiwkx22cWkK2W7e877
bKGX1jH0k8jIZWxE15pBCBkTk+zb6elC263qiw36jxAlEnwd4eP0OAY6SxD9xi5H
fJ7zXO+2hF4bVgofRGNmr5IA9SPL0yRJo+dNm3Sh+MhdNMpvJpOdk0PWqq1ZP9LC
1XCYNtjlImsemugLloKIrdpwAcHJ6XqhyI5IujftmUfN6hL33MAl34Auy/4ElUFU
9DjvWI7lu+R7P8jdDQB3C10/epbmRu7vqtRNUMf7q+MERZQCPqn75qO8P4zGGHdD
hVRQjAlefx6ULvhRlLfCkjrSrpnHFGcYLzPXQuxuhSLvZyCnJrG1XmgLB5SAFPxI
K1oBydqZOYPsPGKZSvMHpBPv9yR2tM6yBjBzBV3/wQCaHD9Yp3sZD9RxSWtAvk3e
zRjQon81W4S0J6dUZL2mog7gWzDj9v42cIV890ezS077dpeL2fSZOUr3fMrM1ZPf
JKue8SrvlVVV1wySA6VxBss71iWZNEHC5gD/geC863FaOxXKFZXWxD+MeM/hrUef
mj67fQ4rjzTgKFRtivmSKzggA3FeOeUCg0gadG9sGH/gfxToA61T/xxEWEyuwJiO
2SVS/iBjQnfcjDMAEQEAAYkCPAQYAQoAJgIbDBYhBETGUTqOT7PTCHX3WO1ET/B9
jQv2BQJh7/JiBQkYPri6AAoJEO1ET/B9jQv2cjYQAJIsOLkH0jl09uVIY84TOYru
4+SMChH6AJklY/600EX8zTBIb0641dsSWk2XyXF+exrlhp/v5ctPb+TbYTDUsQA4
o2lTJ/rLpUIGJU04tIfA0VMCCyCJAOO1OVpEGU1QwRCQ+NnLDHKdNjvJgF9Y3dpY
LL388O6BY0tBPF+/DTsoeJLkb6dohJmyk6ls5zi7ZvY2ab1AmwVXBEfYolisla69
OcGbNrabtpMdd/zdCVxyoHuXaYEuqdMLGbYTDoPI9I2gSBOxIHIJ7z/rHFCDaSSB
iDDE/+mLZLcbj9pSuQn40ZWEPWELUz1YyjI4bSWYQ/gr5UQhOcNmH1KVULm/s6Sx
1MBUvWLXFxqb+T7PqWeUAIMTZTjfBiMqJjPzZ61zBBeQDKvciEy/UnunvX+e1cNQ
1aDzeqaQ3OqJaoFbjmzE218SelQvWCCWQ24ixgQZp8/xd3ae5oQNwqdC0Z6azyMu
l5dzA+1VxXqlTVZ5gH1/74PZP1YeKPgmSx3LrP3gpOP7Rp99wTZ77b9layR9ZyEP
IdcIJF0QNSIrKXHjdh5pTqvLhnw58WjGFOhfyA0/YGsV2wbByGuSOAoGEZMg+hs4
4P3CudqoHQeHZOcflpRwRqheyZc+n2AGxN+RFpvaRV9cs8CiuHyvGHTgq7eear53
ktZPxNR6/WtX7iCfqkg4
=3Lxm

-----END PGP PUBLIC KEY BLOCK-----
After this you should now be able to use apt to update without error:

sudo apt-get update
This is the quickest and easiest way that I have found to fix this issue as apt-key add is deprecated. Everything else I have tried for several hours has returned the same error which is:

The following signatures couldn't be verified because the public key is not available:

NO_PUBKEY ED444FF07D8D0BF6

Reading package lists... Done

W: GPG error: https://kali.download/kali kali-rolling InRelease: The following signatures couldn't be verified because the public key is not available:

NO_PUBKEY ED444FF07D8D0BF6

E: The repository 'https://http.kali.org/kali kali-rolling InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

answered Feb 15, 2022 at 22:21

Источник

This is built in. If you already use Kali’s repos, you don’t need to get it from an external source:

$ sudo apt install kali-archive-keyring

I’m using a system that adds Kali to a Debian base, so I had to specify the release. You can check that as follows:

$ apt policy kali-archive-keyring
  Installed: 2015.2
  Candidate: 2015.2
  Version table:
     2018.1 1
          1 http://http.kali.org/kali kali-rolling/main amd64 Packages
          1 http://http.kali.org/kali kali-rolling/main i386 Packages
 *** 2015.2 100
        100 /var/lib/dpkg/status

$ sudo apt install kali-archive-keyring/kali-rolling

This way, you don’t have to blindly trust that you’re importing the right key in order to prevent a man-in-the-middle attack since the new key is signed by the old one within the repository.

Update: Here’s an /etc/apt/sources.list.d/kali.list and /etc/apt/preferences.d/kali-repos.pref, designed to be secondary to another distribution (like Debian), that’ll avoid this issue in the future.

If you don’t already have this repository and therefore can’t get this update, you have two choices:

1: Go to https://http.kali.org/kali/pool/main/k/kali-archive-keyring/, download the .deb file, and install it via dpkg -i kali-archive-keyring*.deb

2: Add it via the repository anyway (it’s «insecure» until you add it, though you’re at least protected by the HTTPS download in the prior step):

$ sudo apt update -oAcquire::AllowInsecureRepositories=true
$ sudo apt install kali-archive-keyring
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  kali-archive-keyring
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,008 B of archives.
After this operation, 17.4 kB of additional space will be used.
Do you want to continue? [Y/n] 
WARNING: The following packages cannot be authenticated!
  kali-archive-keyring
Install these packages without verification? [y/N] y
…

You’re now synced with the first part of this answer. Consider using the kali.list and kali-repos.pref I linked there so you don’t repeat this problem.

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

AliGhahraei opened this issue

Mar 16, 2021

· 5 comments

Labels

external

Issue exists outside of WSL components

Comments

Environment

Windows build number: Microsoft Windows [Version 10.0.21332.1010]
Your Distribution version: Kali GNU/Linux Rolling 2019.2 (recently installed).
Whether the issue is on WSL 2 and/or WSL 1: Linux version 5.4.72-microsoft-standard-WSL2 (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Oct 28 23:40:43 UTC 2020

Steps to reproduce

Install Kali Linux using a preview build for the Windows Insiders Program:
wsl --install -d kali-linux
Launch Kali Linux and try to update:
sudo apt update

WSL logs: https://aka.ms/AAbk1ly

Expected behavior

The system downloads package information.

Actual behavior

The update fails with the following error:

Get:1 http://kali.download/kali kali-rolling InRelease [30.5 kB]
Err:1 http://kali.download/kali kali-rolling InRelease
  The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
Fetched 30.5 kB in 1s (32.3 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://kali.download/kali kali-rolling InRelease: The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease  The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org>
W: Some index files failed to download. They have been ignored, or old ones used instead.

Additional information

The Kali Linux team suggested a solution in their Twitter account, however that doesn’t work for the subsystem because it requires GnuPG and that package is not installed by default. However, it can be fixed by running:

wget https://archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-key.asc

As far as I know, this issue can be solved by updating the default installation keys.

Was able to reproduce. External the distro, which is not maintained by MSFT. Work-around seems to take.

For anyone running

wget https://archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-key.asc

And getting the following error:

--2021-11-03 10:03:43-- https://archive.kali.org/archive-key.asc Resolving archive.kali.org (archive.kali.org)... 192.99.45.140 Connecting to archive.kali.org (archive.kali.org)|192.99.45.140|:443... connected. ERROR: The certificate of ‘archive.kali.org’ is not trusted. ERROR: The certificate of ‘archive.kali.org’ has expired.

This gets fixed by using http instead of https…

credit: https://gist.github.com/MooreDerek/23686fc29a22d4e1e88e3dd9055fbb07

After that run sudo dpkg -i kali-archive-keyring_2020.2_all.deb

Then you can run sudo apt update

*edit: getting sudo «is your account locked?» errors after apt upgrade… This Kali installation on Win11 seems to be broken on so many sides…

installing kali linux from the Microsoft store instead of wsl --install -d kali-linux fixed all of this…

Works for me this:
wget http://archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-key.asc

don’t use https. USE HTTP.
Then run the command, run apt update and done!

For anyone running

wget https://archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-key.asc

And getting the following error:

--2021-11-03 10:03:43-- https://archive.kali.org/archive-key.asc Resolving archive.kali.org (archive.kali.org)... 192.99.45.140 Connecting to archive.kali.org (archive.kali.org)|192.99.45.140|:443... connected. ERROR: The certificate of ‘archive.kali.org’ is not trusted. ERROR: The certificate of ‘archive.kali.org’ has expired.

This gets fixed by using http instead of https…

credit: https://gist.github.com/MooreDerek/23686fc29a22d4e1e88e3dd9055fbb07

After that run sudo dpkg -i kali-archive-keyring_2020.2_all.deb

Then you can run sudo apt update

*edit: getting sudo «is your account locked?» errors after apt upgrade… This Kali installation on Win11 seems to be broken on so many sides…

installing kali linux from the Microsoft store instead of wsl --install -d kali-linux fixed all of this…

Thanks you so much!! Seriously 👍

You can also get rid of the certification error in wget by running it with a flag:
sudo wget --no-check-certificate https://archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-key.asc

Labels

external

Issue exists outside of WSL components

Источник