ChaosVPN is a system to connect Hackers.
Design principals include that it should be without Single Point of Failure, make usage of full encryption, use RFC1918 ip ranges, scales well on >100 connected networks and is being able to run on a embedded hardware you will find in our todays router.
It should be designed that noone sees other peoples traffic.
It should be mainly autoconfig as in that besides the joining node no administrator of the network should be in the need to acutally do something when a node joins or leaves.
If you want to find a solution for a Network without Single Point of failure, has - due to Voice over IP - low latency and that noone will see other peoples traffic you end up pretty quick with a full mesh based network.
Therefore we came up with the tinc solution. tinc does a fully meshed peer to peer network and it defines endpoints and not tunnels.
ChaosVPN connects hacker wherever they are. We connect roadwarriors with their notebook. Servers, even virtual ones in Datacenters, Hackerhouses and hackerspaces. To sum it up we connect networks - maybe down to a small /32.
So there we are. ChaosVPN is working and it seems the usage increases, more nodes join in and more sevices pop up.
For now, an overview picture of the currently connected nodes: http://vpnhub1-intern.hamburg.ccc.de/chaosvpn.png (from inside ChaosVPN; updated once per hour) There is also a ChaosVPN internal wiki available at http://172.31.0.24/ (unfortunately down at the moment)
Howto join ChaosVPN?
You want to join ChaosVPN and experience the awesomeness of it?
IP Ranges and Participants:
Please see IPRanges for more Infos.
Asterisk servers allowing incoming and outgoing calls to POTS in Hannover and Hamburg hackerspaces. Ask the admins for more information.
During Chaos Communication Camp 2011, participants of the ChaosVPN workshop suggested various applications:
- Mirrors of interesting public FTP/WWW sites
- Bittorrent trackers
- Email (either transparently route email from public domains via ChaosVPN, or have .hack email addresses)
- Censorship detection: service to request a public webpage from proxies at several nodes at once, compare the differences
- GeoIP avoidance?
- Social networking things
- Varnish cache
- LDAP (maybe to allow authenticating hackers against their own hackerspace's LDAP server, like Eduroam)
- Multicast services (limited support in tinc, not automatically forwarded to the LANs)
- TOR entry nodes in ChaosVPN
- NNTP (already available on dn42)
- More games!
- Distributed computing (BOINC, GRID stuff)
clients don't have to authentificate themself - everybody can see the config.config is encrypted now if admins are lazy and don't rebuild the config file properly we will have old routes in the network that don't dissapear (at least until the tinc is reconfigured and restarted)(not a problem anymore with a current .git snapshot, the problem will only affect the non-updating participant with it which should be 0 now
tinc does have some problems. That is the reason why we want to replace that in the forseable future. That will be ChaosVPN 3.0
* Participants can fake network ranges my intention or mistake. (control informations inside tinc are not proper authentificated) (not true anymore with latest chaosvpn.git where we do not import infos from the tinc-network anymore (TunnelServer=yes))