Kali linux repository debian

The topic of repositories is always a large one, and comes up frequently. It is an item which people often get wrong and confused with. Please take the time to read the information below and any references which is linked to before acting on anything.

Default Network Repository Value

On a standard, clean install of Kali Linux, with network access, you should have the following entry present in /etc/apt/sources.list :

If the output doesn’t exactly match up to the above output, you may not be able to install any new additional packages or receive updates. This may happen for any number of reasons, such as:

You have switched your branch.
Using a different hardcoded mirror.

You will probably want to read the “switching branches” section to alter this.

Since Kali 2020.3, after Kali’s setup is complete, network repositories will be enabled by default, even if there was no network access during installation.

Switching Branches/Regular Repositories

Kali has various different branches to choose from (please take the time to read which one would be the best option for your setup), and you may be able to switch or include additional repositories.

kali-rolling (Default & frequently updated):

kali-last-snapshot (Point release so more “stable” & the “safest”):

kali-experimental (Packages which are under testing — often used with the rolling repository):

Sources.list Format

Archive is going to be deb (Regular Binary) or deb-src (Source), depending if you want a package or the source of the package.
Mirror should be http.kali.org/kali as this is our load balancer, which will direct you to best mirror.
Branch is what version of Kali you wish to use.
Component is what packages you wish to use, based on the Debian Free Software Guidelines (DFSG). Kali defaults to everything.

Default Offline Install Values

During the Kali setup process, if you don’t have access to a network connection to reach a repository, you will perform an offline installation of Kali Linux. You will be limited to the packages & the version which is on the medium you installed Kali from. This will then configure Kali to continue to use this medium to install packages from, even after Kali has been installed.

This means you will not get any updates to packages, or any new additional tools, which can be frustrating. You can see if you the offline media enabled if your values match up with whats below (or if you want to enable this option):

If your output matches whats above, please see the switching branch section, if you wish to receive updates.

However, if you do have network connection, which has access to network repositories, it will be enabled for you. You don’t need to do anything.

Non-Kali Repositories

If you want to install additional tools and software (such as signal) outside of what Kali has to offer, you may need to include an extra repository for this to happen. Please do not alter /etc/apt/sources.list , as this is used for the Kali Linux Operating System. Any extra tools and software needs to be placed into their own file in the directory /etc/apt/sources.list.d/ (such as /etc/apt/sources.list.d/repo-name.list , replacing repo-name with the mirror name). It is highly recommended that each mirror should be in its own file.

By adding Kali’s repository to a non-Kali OS (such as trying to add Kali to Ubuntu), this will highly increase the chance of your system not working. It may not happen straight away, but without any warning, it may break. We will not be able to offer support (and based on what we have seen over the years, most other OS will not help too).

Likewise, adding other operating system’s repositories into Kali (such as trying to put Ubuntu on Kali), will break your installation. This is the single most common reason why Kali Linux systems break.

If any guides are telling you to do anything else than the above, this is unofficial advice, and completely not supported by Kali Linux. More often than not, users in this case end up doing a reinstall after learning this lesson.

Mirrors

We have a list of official Kali Linux mirrors, as well as a guide on how to setup your own. This may be kept as a local repository which is only accessible on a LAN, or a remote private one, or if you have the ability to, you may wish to share back to the community and make it public allowing for anyone else in your geographical area to benefit from it.

Source Repositories

By using a deb in the repositories, it will allow for binary packages to be downloaded. However, should you require the source to a package (so you can compile the package yourself if you so wish, or look into debugging a problem with a package), you can add deb-src as a extra line in the repositories.

We used kali-rolling for the branch above, but you can select any value you wish.

Updated on: 2021-Sep-27
Author: g0tmi1k

Источник

Kali linux repository debian

A branch is an alternative version of some software, in this case of the Kali OS. Kali Linux has multiple branches which allows for users to decide how up-to-date their packages will be. Kali Linux is similar to Debian in many regards, one of which is the use of branches.

You may have multiple branches enabled at once. However, switching branches may introduce problems, as packages may be at different versions, and unavailable or unstable in certain cases.

Please see the network sources page for how to switch branches. For an example of how to use multiple branches, please see our NVIDIA GPU Drivers guide.

Kali Branches

First are the main branches, which are the most frequently used, and the most stable. These are often seen as “safe”.

kali-rolling is the main default branch that most should be using. It is being continuously updated, as it pulls from kali-dev after ensuring questionable packages are stable and combining them with packages from kali-rolling-only . From time to time, a package bug may slip into here, due to bugs in debian-testing .
kali-last-snapshot is a branch of Kali that can be used if users want a more standard feeling of software control. For every new release, we freeze the code and merge kali-rolling into kali-last-snapshot , at which point users will get all of the updates between versioned releases (i.e. 2020.3 -> 2020.4). This often is more stable, as packages are not updated (until the next release as it’s a “Point Release”) and go thought our release testing. This is the “safest” option.

Next are those that you will likely not need except in very special cases:

kali-experimental is a staging area for work-in-progress packages.
kali-bleeding-edge contains packages that are automatically updated from the upstream git repositories. This branch has the potential to be very unstable.

Development

kali-dev is the development version of Kali Linux. It is created by combining three other branches: kali-dev-only , kali-debian-picks and debian-testing . Its mainly used for merging Debian’s updates with the changes maintained by Kali Linux.
kali-dev-only is the development distribution with Kali-specific packages. This branch is auto-merged into kali-dev .
kali-rolling-only is a repository for packages that need to quickly reach kali-rolling .

Branches Used to Assist With Other Branches

kali-debian-picks contains packages cherry-picked from debian-experimental and debian-unstable . It is auto-merged into kali-dev .
debian-testing is a mirror of Debian’s testing distribution. This is used to build kali-dev .
debian-experimental and debian-unstable are partial mirrors for specific packages that we want to cherry-pick.

Mapping

Below is a diagram showing the relationship between the branches.

Debian’s Relation

Debian has three main options:

Stable is the “safe” Debian branch. Around every two months, it is updated with a “Point Release”, which is often just security updates. Packages don’t generally get a version upgrade during this time, due to potential incompatibility and thus instability. This is the Debian equivalent of kali-last-snapshot.

Testing is the closest thing there is to a Debian “rolling” distribution, where “rolling” means that as soon as a package update is available, it’s pushed out. Kali has used this branch as a starter for kali-rolling since January 2016.

Unstable is just after Debian’s package development happens. The packages have been created, but not fully tested. Kali doesn’t have an equivalent, as it is a rolling distribution.

For more information about how Kali relates to Debian, please see our policy page on the matter.

The kali-rolling Repository

Contrary to kali-dev, kali-rolling is expected to be of better quality because it’s managed by a tool that ensures installability of all the package it contains. That tool picks updated packages from kali-dev and copies them to kali-rolling only when they have been verified to be installable. Note however that those checks do not include any functional testing. It might still contain broken software due to other problems that are not covered by the package dependencies. Kali Rolling is the primary repository that most users should be using. They can also report any issue they have with Kali specific packages on bugs.kali.org. Make sure to select the “kali-dev” version in “Product version”.

Kali Rolling users are expected to have the following entries in their /etc/apt/sources.list:

The kali-dev Repository

WARNING: While kali-dev is publicly accessible to everybody on all Kali mirrors, this distribution should not be used by end-users as it will regularly break.

This repository is actually Debian’s Testing distribution with all the kali-specific packages (available in the kali-dev-only repository) force-injected. Kali packages take precedence over the Debian packages. Sometimes when Testing changes, some Kali packages must be updated and this will not happen immediately. During this time, kali-dev is likely to be broken. This repository is where Kali developers push updated packages and is the basis used to create kali-rolling.

Источник

Репозитории в kali

Здравствуйте! Недавно поставил новый kali linux. Не могу поставить ни один пакет через apt: все время пишет not found. Вот sources.list:

Ахтунг! Мамкины кулхацкеры!

А вообще, APT тебе выдал ошибку. Можешь запустить его с английской локалью, пусть напишет на английском проблему, которую ты можешь загуглить. LC_ALL=C apt update.

Любым удобным способом получаете файл по ссылке https://archive.kali.org/archive-key.asc
Затем вводите терминале:
«apt-key add» и путь к файлу archive.key-asc

Большое спасибо) Все работает.

Благодарность

Столкнулся с такой же проблемой как у топикстартера. Решение просто и лаконично. + в карму.

а мог и свинку подложить с левым репозиторием и ведь приняли бы

та же проблема, но предложенный способ не работает((

root@Xiaomi:/mnt/c/Users/tiuga# apt-key add archive.key-asc E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation

Для этого мне пришлось бы стать владельцем домена разработчиков Kali linux. Если бы домен был моим, кто-нибудь уже на форуме поднял бы тревогу.

gnupg отсутствует в системе. Я даже не могу представить, как это могло получиться, но это поправимо, если, конечно, из системы больше нечего другого не исчезло. Сейчас я пишу с телефона, так что дать подробные инструкции не могу. Самый простой вариант — скачать пакеты с gnupg и его зависимостями из репозитория вручную, а затем установить их с помощью команды «dpkg -i путь_к_deb_файлу» . Сами пакеты можно найти по адресу https://archive.kali.org/kali/pool/

Полагаю, нужные пакеты вы сможете найти самостоятельно по названиям. gnupg должен быть в категории main.

благодарю, а то установка через сеть не проходит, там очень много пакетов, мне все подряд ставить?

Если вы имеете в виду пакеты gnupg, то необходимо выбрать пакеты под вашу систему. Например, если вы используете обычный 64 битный дистрибутив (не для arm процессоров), то вас интересуют пакеты, название которых заканчивается на amd64. Возможно, в процессе установки вас попросят установить какие-нибудь другие пакеты, от которых зависит устанавливаемая программа — тогда придется сначала скачать и установить их.

требует пакет dpkg: dependency problems prevent configuration of gnupg1: gnupg1 depends on libcurl3-gnutls (>= 7.16.2); however: Package libcurl3-gnutls is not installed.

dpkg: error processing package gnupg1 (—install): dependency problems — leaving unconfigured Errors were encountered while processing: gnupg1

libcurl3-gnutls а я чет нигде не могу найти его

ответ

https://hackware.ru/?p=4692 выполнить две команды и будет вам счастье.

Столкнулся с такой же проблемой. Установка archive.key-asc помогла, спасибо. Но начались проблеммы я полагаю с репозиторием при установке privoxy. Помогите пожалуйста решить проблему.

# apt-get install tor privoxy

Reading package lists. Done Building dependency tree Reading state information. Done The following additional packages will be installed: doc-base libuuid-perl libyaml-tiny-perl libzstd1 tor-geoipdb torsocks Suggested packages: rarian-compat mixmaster torbrowser-launcher tor-arm apparmor-utils obfsproxy obfs4proxy The following NEW packages will be installed: doc-base libuuid-perl libyaml-tiny-perl libzstd1 privoxy tor tor-geoipdb torsocks 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. Need to get 3,513 kB/3,736 kB of archives. After this operation, 14.6 MB of additional disk space will be used. Do you want to continue? [Y/n]

Источник