Network Obstacle

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

Project-APT-Repository Documentation Desktop Previous page: Project-APT-Repository Index page: Documentation Next page: Desktop Network Obstacle

Some users will experience "network obstacles" when using Kicksecure because some internet service providers (ISPs) in various countries block (censor, prevent) access to the public Tor network. In this instance, Bridges may or may not help in circumventing Tor censorship.

This page describes potential solutions for and the organizational background on network obstacles.

Introduction

Kicksecure is a research and implementation project that is based on thousands of freely available software packages. You can learn more about the organizational structure here.

The Kicksecure project does not maintain Tor. Further, the reliance of the Kicksecure platform on Tor does not imply developers are experts about the Tor software.

Network Obstacle Examples

Some users will experience "network obstacles" when using Kicksecure because some internet service providers (ISPs) in various countries block/prevent access to the public Tor network. In this instance, The usage of Bridges is required, For example in China the Great Firewall automatically blocks connections to Tor thus it is necessary to obtain a bridge that works:

1. Snowflake: uses ephemeral proxies to connect to the Tor network.
2. Private and unlisted obfs4 bridges: users will need to request a private bridge to frontdesk@torproject.org with the phrase "private bridge" in the subject of the email or, if they are tech-savvy, they can run their own obfs4 bridge. Bridges distributed by BridgeDB (HTTPS, email).
3. meek-azure: it looks like you are browsing a Microsoft website instead of using Tor. However, because it has a bandwidth limitation, this option will be quite slow.

Effect on Kicksecure

Kicksecure need a working Tor connection because of:

• Updates are torified by default.
• sdwdate
• Onionizing Repositories (optional configuration)

Not having a working Tor on your machine will lead to time/clock and update/upgrade failure.

Footnotes

Project-APT-Repository Documentation Desktop Previous page: Project-APT-Repository Index page: Documentation Next page: Desktop

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- 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!