Kicksecure Documentation Introduction

From Kicksecure
Revision as of 17:52, 19 January 2022 by Nurmagoz (talk | contribs)
Jump to navigation Jump to search

Overview

Info Anonymity is not a program, setup, or final destination -- it is actually a continual process, influenced by new knowledge that is constantly gathered. [1]

Using Kicksecure with its default settings provides more security than Tor alone. Anonymity is a complex problem and there is no easy solution to the many complicated challenges that all users face. The more you know, the safer and more anonymous you can be. Kicksecure provides extensive documentation for those interested in learning more.

The goal of this documentation is to describe The Kicksecure Anonymous Operating System in an easy-to-understand and reasonably thorough manner. It is hoped readers will be exposed to a range of new and improved concepts/applications regarding anonymity and security on the Internet.

Note that all the applications included in Kicksecure are not fully documented. Usually an overview is provided, with further details on Kicksecure-specific configurations that might be necessary. In general, use the documentation as a reference guide for only those features you intend to use. For instance, if a user is interested in I2P over Tor, the introductory section on Other Anonymizing Networks should be read first, followed by the I2P chapter.

Kicksecure Footnotes and References

Small text and footnotes like 1 are not that crucial. They contain clarifications, information sources, extra notes for people with higher security needs, additional details to dispel doubts (in the case of controversial issues), proof of something, references, links, and so on. Generally speaking, it is unnecessary to read all of the footnote links (particularly for beginners), but it is encouraged.

For further clarification, footnotes are typically used in the following circumstances:

  • Developer notepad: Sometimes links are added when references such as related source code are difficult to find (on search engines or otherwise).
  • Supporting evidence: Footnotes often provide additional references to support statements in the main documentation, particularly if factual statements are not obvious. This preempts possible future questions from the Kicksecure population and provides greater clarification at the outset.
  • Comments for auditors: In various sections footnotes are added to answer potential auditor questions around specific Kicksecure recommendations, chosen security configurations, why alternatives were not implemented, and so on.
  • Reducing duplication: To avoid duplicate tickets and discussions, footnotes often link to existing (usability) issues, as well as identical or related discussions to raise the reader's awareness.
  • Reducing confusion: Footnotes will sometimes link to additional information sources in an effort to reduce user confusion. For example, a common use case is when a major Kicksecure configuration has changed; legacy users might be confused why a change was implemented if this issue was not referenced. In general this reduces the likelihood of support requests.
  • Troubleshooting: Most software is expected to be fully functional with available instructions. However, in corner cases footnotes can provide possible troubleshooting tips and known workarounds.
  • Advanced users: To be more user-friendly, documentation is generally focused on the needs of "everyday" users who do not require specialist configurations or functionality. However, footnotes sometimes provide links or instructions for advanced users to undertake more complicated activities. Footnoting in this case reduces potential confusion for the larger Kicksecure population.
  • Other non-essential information: For simplicity, footnotes sometimes contain non-essential links, quotes, research articles and similar material for interested readers.

To remove all doubt, novice or intermediate users can generally ignore footnotes unless experiencing difficulties with the particular software, activity or configuration in question. Footnotes are more valuable for those exploring topics in further detail, undertaking advanced configurations, performing development, or seeking answers to specific questions.

Recommended Reading

The documentation is lengthy, so newcomers to the Kicksecure platform or those with limited time should first read these sections:

If users have more time available, it is suggested to read the Documentation widely, particularly the Basic Security Guide, Advanced Security Guide, and Computer Security Education sections.

Final Warning

The Kicksecure design is intended to offer a technological means to stay anonymous on the Internet. However, it should be emphasized that staying anonymous is not simply a technological problem – there is no tool, including Kicksecure and Tor, that magically provides Internet anonymity. It is necessary to change a host of behaviors as well.

It is certainly helpful to have a deep, technical understanding of Internet architecture, cryptologyarchive.org iconarchive.today icon, traffic analysisarchive.org iconarchive.today icon techniques, and the applications that are in use; mainly by knowing what not to do. However, users with basic knowledge who proceed cautiously (using common sense) are likely to protect themselves adequately in most cases.

License

Kicksecure Introduction wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Kicksecure Introduction wiki page Copyright (C) 2012 - 2021 ENCRYPTED SUPPORT LP <adrelanos@whonix.org>

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.

Footnotes

  1. This aligns with the axiom that "Security is a process, not a product."
Notification image

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!