Relationship With Upstream

Kicksecure ™

Download

On Computer USB Installation Debian morph to Kicksecure Windows (VM) Linux (VM) Mac (VM) VirtualBox (VM) KVM (VM) Qubes (VM) More options Source Code

About

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

Docs

Documentation FAQ Troubleshooting

Community

Forums 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

• Maintainability
• Relationship With Upstream
• Stable Version User Experience
• Privacy Goals and Non-Goals

Kicksecure Relationship with Upstream Projects.

Summary

For various reasons Kicksecure tries to diverge by the smallest possible amount from its upstream projects, and especially from Debian:

• wants to share his work with the rest of the Free Software community;
• more code review;
• values maintainability very much: believe users are best served if keep the amount of work needed to maintain Kicksecure the smallest possible;
• Dev/maintainability;
• Focus on low-effort maintainability

How

Debian specific

Derivatives Census

Kicksecure participates in the Derivatives Census.

Infrastructure

Debian Derivatives Guidelines recommends "We encourage derivative distributions to use Debian infrastructure and the software that powers Debian infrastructure where possible.".

Kicksecure makes heavy use of that. Only official Debian repositories are used. Kicksecure is very thankful, that Debian derivatives are allowed to do so. The Kicksecure project has neither the infrastructure, the founding nor the manpower to run its own repositories.

Debian packages

Neither binary nor source packages are modified.

Any configuration file modifications of any packages sourced from packages.debian.org which derivate from the default package configuration is implemented through Kicksecure packages.

Keyrings

Kicksecure does not modify keyrings.

Patrick's OpenPGP key is copied into Kicksecure virtual machines at build time. It is only used to ensure authenticity of Kicksecure APT repository.

Releases

See About Debian for reasons to choose stable.

Trademark

Kicksecure is and will never be called Debian. It must always be clear that Kicksecure is a Debian derivative or based on Debian.

Patrick Schleizer e-mailed trademark at debian.org and briefly explained Kicksecure. Debian Leader Stefano Zacchiroli said, there will be no trademark issues as long as Kicksecure will not claim to be Debian, which will of course never happen.

See also Kicksecure Trademark Policy.

De-/Re-branding

Not necessary. See Trademark above.

Bug reports

Reportbug is unchanged. No Debian packages are modified.

Popularity Contest

Not installed in Kicksecure. Reasons are in the Popularity Contest chapter.

General

Upstream software

When technical skills and time allows, changes are pushed upstream when we need to modify software shipped. Only package selection, configuration files and scripts are modified.

Upstream Bug tracking systems

All bugs found in Kicksecure, will be checked, if they also apply to upstream. If that is the case, the plan is to check if bug has already been reported. If there is something constructive to contribute, it will be done. In case there is not yet a bug report, one will be submitted.

The same goes for wishlist/enhancement requests.

Why this document?

The Debian Derivatives Guidelines encourages "derivative distributions to mention and define their relationship with Debian". Because this seems like a great idea, this statement that not only covers Kicksecure relationship with Debian, but also Kicksecure relationship with any one of its upstream projects.

Other Projects

• https://tails.net/contribute/relationship_with_upstream/

Unreliable Upstream

This is a definition of unreliable upstream. Things which make upstream unreliable can include, non-exhaustive list:

• non-responsive
• considering deprecation
• maintenance lapses
• difficult to work with
• unrelated personal attacks

License

Kicksecure Dev/Relationship With Upstream wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Kicksecure Dev/Relationship With Upstream wiki page Copyright (C) 2012 - 2024 ENCRYPTED SUPPORT LP <adrelanos(at)kicksecure.com (Replace (at) with @.)Please DO NOT use e-mail for one of the following reasons: Private Contact: Please avoid e-mail whenever possible. (Private Communications Policy) User Support Questions: No. (See Support.) Leaks Submissions: No. (No Leaks Policy) Sponsored posts: No. Paid links: No. SEO reviews: No. >

This program comes with ABSOLUTELY NO WARRANTY; for details see the wiki source code.
This is free software, and you are welcome to redistribute it under certain conditions; see the wiki source code for details.

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 2025 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- 2024 ENCRYPTED SUPPORT LP

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 12 year success story and maybe DONATE!