Discover how two geeks invented a kick-ass technology that helps normal people protect themselves from government snoopers.
COMMUNITY CUBE is a technology that makes protecting your privacy easy. Thanks to a unique combination of open hardware and software, it’s both a server and a provider of free secure services. You can trust us, we are fully open.
C-Cube is a plug and play, open source, energy efficient server designed from the ground up with security and privacy in mind.
###Why do we need this technology?
The Internet is full of free services. Most are offered by large corporations that work for the common good. Right?
NOT TRUE!. They are giving you something for free because they want something in return - your personal data. By burying the details in their terms and conditions page, that almost nobody reads, they are in fact hiding their nefarious intentions.
Community Cube operates exactly the opposite, because we integrate into each C-Cube a carefully selected security audited services, you no longer need to depend on the good intentions of these big corporations.
Community Cube initiative work as a Peered Cooperativeness Project that intends to be the biggest world wide cooperative company allowing investment only to purchase of boxes and connecting them to the C-Cube network.
- A private society or corporation.
- Head managed.
- Difficult to use.
Some of C-Cube services has being provided by some time, but un-integrated and with some flaws, let's show you:
If you want more information about the software that we picked check here.
None of F2Friend-nets, darknets, private-nets, Libre-nets, peering-nets, deep-web are the first choice for any non-technical end users, they need a product to protect their-selves. Most of secured services work inside those pseudoF2Fnets that often don't offer a decentralized real world interconnection, and almost all don't offer a soft migration way for a those end users, often trained, for a commercial centralized product.
Bad people with bad intentions like:
- Sniffers: those that are checking your traffic
- Government spy/monitoring institutions passive actions: like passive bots collecting general data from worldwide, if they target anyone... that is another story.
- CommunityCube evil nodes: a box Owned for those bad people.
- Malicious internet nodes: better known as blackbones.
- Your internet provider (ISP): if they would trying anything with your data.
In technical words , to protect you, Community Cube does:
- Filtering virus, exploits malware, ads , bad IP-sources and bad content.
- Decentralizing the services (doing impossible to apply big data to you )
- Open authentication (dissolve legal relation between user and name-ip), Dark-nets (anonymisation of IP)
- Forcing encryption for all communications and data storage and in rest.
- Filtering the data that expose you, like scripts,cookies, browser info,etc.
In our decentralized system your valuable information is encrypted three times:
- Before it even leaves your computer, in the web browser
- In the collaboration tool before the data goes to the hard disk
- When backing up to the grid, the slices will also be encrypted.
You want more information, you can check here for more information or here for a lot more information.
Easy as fork us and send pull requests, but if you want to get in touch with us meet us in our web page CageOS.
This is on discussion yet, but the idea is to offer a solution that can be deployable on a public distribution with your own hardware, but as standalone we have this models:
- C-Cube has two presentations:
| Low-end model - Odroid C2 | High-end model - Odroid XU4 |
|---|---|
| Odroid C2 | Odroid XU4 |
| ssd 8gbc10 | ssd 8gbc10 |
| USB2ETH | HDD 2TB |
| 2xWLAN 1watt | SB2ETH |
| Batteries | 2xWLAN 1watt |
| CASE | CASE |
| RoboPeak Usb tft screen | RoboPeak Usb tft screen |
More information here.
There are 2 ways to join to CommunityCube network
Step 1: Checking requirements
Your Physical/Virtual machine need to meet the minimum requirements:
- 2 network interface
- 1 GB of Physical memory
- 16 GB of free space
If your machine is ok with requirement, then you can process to next step.
Step 2: Setup the network.
In this step you need to connect one interface of your machine to Internet, and other one to local network device.
Step 3. Executing scripts.
In this step you need to download and execute the following scripts on your machine with given order.
1. test.sh (Initialization script)
Script workflow
- Check User
- You need to run script as root user
- Check Platform
- Platform should be Debian 7/8, Ubuntu 12.04/14.04
- Check Hardware
- If you are running this script on odroid it should detect Intel processor
- Check Requirements
- Machine should match the requirements mentioned above
- Check Internet
- Check Internet connection.
- Prepare perositories
- Update repositories for necessary packages
- Download packages
- Download necessary packages
- Install packages
- Install necessary packages
You can find Initialization workflow here
2. app-installation-script.sh (Configuration script)
It aims to configure all the packages and services.
Step 1. Get an odroid and assemble it.
There are several seperate modules that need to be connected to odroid board.
You can find more information about necessary modules here.
Step 2. Executing scripts.
In this step you need to download and execute the following scripts on your machine with given order.
1. test.sh (Initialization script)
Script workflow
- Check User
- You need to run script as root user
- Check Platform
- Platform should be Debian 7/8, Ubuntu 12.04/14.04
- Check Hardware
- If you are running this script on odroid it should detect ARM processor
- Check If Assembled
- All neccessary modules should be connected to odroid board
- Configure Bridge Interfaces
- eth0 and wlan0 will be bridged into interface br0
- eth1 and wlan1 will be bridged into interface br1
- In ethernet network, br0 should be connected to Internet and br0 to local network
- In wireless network, bridge interdace with wore powerful wlan will be connected to Internet and other one to local network
- Check Internet
- Check Internet connection.
- Prepare perositories
- Apdate repositories for necessary packages
- Download packages
- Download necessary packages
- Install packages
- Install necessary packages
You can find Initialization workflow here
2. app-installation-script.sh (Configuration script)
It aims to configure all the packages and services.
You can check out the full license here
This project is licensed under the terms of the GNU GPL V2 license.