Kicksecure ™ APT Repository

From Kicksecure
Jump to navigation Jump to search

Kicksecure ™ Derivative Repository Tool

Kicksecure ™ APT Repository Overview[edit]

Kicksecure ™ currently provides four repository choices:

  • Kicksecure ™ stable APT repository: Recommended for most users. The production level packages focus on providing the most reliable Kicksecure ™ experience. [1]
  • Kicksecure ™ stable-proposed-updates APT repository: After testing by a wider audience, these packages migrate to the stable repository. [2]
  • Kicksecure ™ testers APT repository: Recommended for testers, since it is only briefly tested by Kicksecure ™ developers. It could break APT during an upgrade, requiring terminal commands to rectify the problem. [2]
  • Kicksecure ™ developers APT repository: As above, except it includes untested changes. These changes may eventually migrate to the testers repository there is reasonable certainty that these changes will not break the update system. It is not recommended, unless the user is in touch with the development team.

Due to the Kicksecure ™ design, a user's security is unlikely to be materially affected by preferring the "beta" (stable-proposed-updates) or "alpha" (testers) repositories over the default stable one. [3]

Change Kicksecure ™ APT Repository[edit]

It is easy for users to switch between Kicksecure ™ repositories.

Kicksecure ™ for Qubes[edit]

If you are using change link to Kicksecure ™ for Qubes , please press Expand on the right.

Qubes App Launcher (blue/grey "Q")Template: kicksecureRepository

Figure: Wizard Repository Selection

Whonix Repository Wizard select repo.png

Figure: Wizard Auto-update Configuration

Whonix Repository Wizard install updates.png

Kicksecure[edit]

If you are using Kicksecure ™, please press Expand on the right.

Start MenuSystemDerivative Repositorychoose either "stable", "stable-proposed-updates" , "Testers" or "Developers" repository

Figure: Start Menu

Whonixrepoxfce1.png

Figure: super user password

Whonixrepoxfce2.png

Afterwards, the following window will appear.

Figure: Auto-update Configuration

Whonixrepoxfce3.png

Figure: Repository Selection

Whonixrepoxfce4.png

Command Line Interface[edit]

If you are a terminal user, please press Expand on the right.

In Terminal, run.

sudo repository-dist

Figure: Launch Terminal

Whonixrepocli.png

Figure: Run repository-dist

Whonixrepocli2.png

Choose one of the following repositories based on personal preferences.

sudo repository-dist --enable --repository stable

sudo repository-dist --enable --repository stable-proposed-updates

sudo repository-dist--enable --repository testers

sudo repository-dist --enable --repository developers

To use the repository, follow the usual update instructions.

Disable Kicksecure ™ APT Repository[edit]

For Trust reasons some users may prefer not to use Kicksecure ™ APT Repository. In that case, it is necessary to update Debian packages in Kicksecure ™ from source code, which is inconvenient.

All Default-Download-Version Kicksecure ™ variants have the Kicksecure ™ APT repository enabled. It can be disabled via the GUI or in a terminal with the Derivative Repository Tool.

Table: Kicksecure ™ APT Repository Disabling

Platform / Method Instructions
Kicksecure ™ Built from Source Code If Kicksecure ™ is built from source code, Kicksecure ™ APT Repository is not added by default. The only exception is if users opt in using a build configuration. It is also possible to verify that it is already disabled.
Kicksecure ™ Default-Download-Version: GUI
  • Kicksecure ™ inside Qubes: Qubes App Launcher (blue/grey "Q")Template: kicksecureRepository"No, I will manually update from source code."
  • Kicksecure ™: Start MenuApplicationsSystemKicksecure Repository"No, I will manually update from source code."
Kicksecure ™ Default-Download-Version: Terminal To disable it in a terminal, run.

sudo repository-dist --disable

Users can optionally verify Kicksecure ™ APT repository is disabled after this procedure.

Verify Kicksecure ™ APT Repository is Disabled[edit]

To check the Kicksecure ™ APT repository was successfully disabled, run the following tests.

1. Use apt-key.

sudo apt-key finger

This test should not show any Kicksecure ™-specific keys, such as Patrick Schleizer's OpenPGP key.

2. Check if file /etc/apt/sources.list.d/derivative.list exists.

If it does not exist, the procedure was successful.

3. Optional: conduct additional tests as a precaution.

Examine the /etc/apt/sources.list file. It should not include the Kicksecure ™ APT Repository.

cat /etc/apt/sources.list

Next examine the /etc/apt/sources.list.d/ folder as well.

cat /etc/apt/sources.list.d/*

Further Reading[edit]

Footnotes[edit]

  1. If possible, users are requested to run a separate testers-only Kicksecure that has the testers repository enabled. If too few people test Kicksecure ™, undiscovered issues might migrate to the stable repository.
  2. 2.0 2.1 Users are recommended to make a VM clone for this repository just in case it breaks. That way changes can be rolled back if necessary.
  3. The terms alpha and beta are avoided because they have generally lost their meaning in the software field; many applications remain in alpha or beta status for years, even though they work perfectly well.


Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.