APT Signing Key Folders and Other Development Notes

Kicksecure ™

Download

On Computer USB Installation Intel / AMD64 ARM64 Raspberry Pi PPC64 Windows (VM) Mac Linux (VM) VirtualBox (VM) Qubes (VM) KVM (VM) Debian morph to Kicksecure More options Source Code

About

Overview Features Why Open Source? Project Activities Contributors Mission & Vision

Docs

Documentation FAQ Troubleshooting

Community

Forums Forum Best Practices Contribute

Support

Self Support First Policy Search Engines, Docs and AI Support (Limited) Reporting Bugs Contact (Restricted)

Tools Upload file Special pages Recent changes Print Version Page meta What links here Related changes Page information

Page Read Edit History Move Protection Unwatch Watch Delete Purge

User Preferences Watchlist Contributions Logout Create account Login

Donate

Dev/apt-revoker Design Dev/About Debian Packaging Previous page: Dev/apt-revoker Index page: Design Next page: Dev/About Debian Packaging APT Signing Key Folders and Other Development Notes

/etc/apt/trusted.gpg, /etc/apt/trusted.gpg.d, /usr/share/keyrings

APT Keyring Folders

APT by default considers only signing keys in:

• file /etc/apt/trusted.gpg
• folder /etc/apt/trusted.gpg.d

Signing keys in folder /usr/share/keyrings are ignored by default by APT, unless the signed-by keyword is used in APT sources files (i.e. in configuration file /etc/apt/sources.list or in configuration snippet drop-in folder /etc/apt/sources.list.d).

Example signed-by keyword use:

[signed-by=/usr/share/keyrings/derivative.asc]

Example of complete deb line with signed-by keyword.

deb [signed-by=/usr/share/keyrings/derivative.asc] https://deb.kicksecure.com bullseye main contrib non-free

Repository Migration

Which project and which version comes with which repositories enabled by default?

• Kicksecure builds earlier than version 16.0.5.0 come with: deb.whonix.org
• Kicksecure builds version 16.0.5.0 come with: deb.kicksecure.com
• Whonix builds earlier than version 16.0.5.0 come with: deb.whonix.org
• Whonix builds version 16.0.5.0 come with: deb.kicksecure.com + deb.whonix.org

Which repositories contain what packages?

• Legacy:
  • 16 and below: Mixing. Legacy. For migration purposes. Both, deb.kicksecure.com and deb.whonix.org contain all packages, i.e. contain both, all Kicksecure and all Whonix packages.
• Future:
  • 17 and above: Clean separation. deb.kicksecure.com will contain only all Kicksecure packages and no packages of other derivatives.
    • To accomplish that, in Kicksecure GitHub developer-meta-files repository subpath the only thing to be removed is for derivative_name_item in $derivative_name_list ; do (and done).

changed its 'Origin' value from 'whonix' to 'kicksecure'

Kicksecure GitHub derivative-maker repository subpath is still using old Origin and Label values. This is to avoid the following error during "sudo apt update".

E: Repository 'tor+https://deb.kicksecure.com bullseye InRelease' changed its 'Origin' value from 'whonix' to 'kicksecure'
E: Repository 'tor+https://deb.kicksecure.com bullseye InRelease' changed its 'Label' value from 'Whonix' to 'Kicksecure'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

• This is avoid users updates getting more complicated by seeing above error message and needing to use sudo apt update --allow-releaseinfo-change to resolve it.
• Origin and Label needs to be to be changed in Kicksecure 17 (actually 18) in above file once the Kicksecure repository for Debian bookworm based becomes available. This will be done during Release Upgrade.

Why does Kicksecure use Origin whonix?

• version 16 and below: For legacy compatibility.
  • Technical detail: For the longest time, for most users deb.kicksecure.com was a mirror of deb.whonix.org. Hence used Origin whonix. To keep the amount of user confusion lowest, fewest users being affected it was decided to keep it that way until the release upgrade for version 16 (Debian Origin based) becomes available. Unfortunately those users who upgraded fastest saw the `Origin`/`Label` change.
• version 17 above: No more legacy. Kicksecure will use Origin kicksecure.

Background on Debian APT Origin and Label

When Debian's APT sees for the first time a repository, it notes its Origin and Label fields. Should these change, Debian will show a warning/question and not proceed using any repository with a changed Origin or Label until the user accepts the change using sudo apt update --allow-releaseinfo-change.

Forum Discussion

https://forums.whonix.org/t/e-repository-tor-https-deb-kicksecure-com-bullseye-inrelease-changed-its-origin-value-from-kicksecure-to-whonix/13810

See Also

• Dev/APT Pinning
• Dev/APT Repository
• signed-by keyword forum discussion

Dev/apt-revoker Design Dev/About Debian Packaging Previous page: Dev/apt-revoker Index page: Design Next page: Dev/About Debian Packaging

Kicksecure A secure by default operating system with the latest security research in place.

Dark mode

Follow us on social media

Supported by Power Up Privacy

Kicksecure is proudly supported until 2026 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Kicksecure we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint 2012- 2025 ENCRYPTED SUPPORT LLC

Your support makes
all the difference!

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!