Echt Dezentrales Netz/en: Unterschied zwischen den Versionen

Aus C3D2
Zur Navigation springen Zur Suche springen
Keine Bearbeitungszusammenfassung
Zeile 140: Zeile 140:
# '''Testing the implementation''' as a '''proof of concept'''
# '''Testing the implementation''' as a '''proof of concept'''
# '''Distribution''' of software and hardware, where needed
# '''Distribution''' of software and hardware, where needed
== Federation Network ==
http://www.federation.network


== Contact ==
== Contact ==

Version vom 28. Mai 2015, 16:34 Uhr

Deutsch

In times of growing surveillance we unite
to give an adequate technical answer and create by ourselves
what we have been waiting for.

Welcome

This is the official wiki of the research and software project EDN (Echt Dezentrales Netz - real decentralized network).

We verify the applicability of existing technologies (see Recherche) and aim to integrate them into a comprehensive product.

An encrypted Wireless Community Network, with several anonymised services.

For that purpose we will deploy a testing network and help projects EDN will depend on.

News

Background

Today's communication infrastructure is predominantly centralized.

However, this makes surveillance and manipulation of arbitrary digital communications easier.

These means can be abused - and were abused - not only by dictatorships but also by democratic countries and international companies.

There are indeed solutions like Tor or PGP which can partially patch the shortcomings of the infrastructure, but each user has to take care of that it for herself. Anonymisation and encryption are not in the standard configuration.

A penal action against these secret processes is nearly impossible, starting with the problem that they are not even detected by the affected parties. This status quo endangers our democracy. However, it can be countered in different ways. The following is a technical approach: To repurpose and to extend existing digital communications infrastructure to make surveillance more cumbersome, especially through decentralisation.

Goal

The communication potential in densely inhabited regions can be guessed watching these pictures:

Our goal is to use the existing resources to form a difficult-to-monitor cellphone/router/computer network. There are plenty of software solutions (Recherche) with the goal of protecting the privacy of its users. Preexisting structures are to be evaluated and combined into such a network. The communication should run, first and foremost, on top of a combination of WiFi, copper and fibre optics, but we also consider Bluetooth, Ultra Wideband (UWB), red light, ukw and satelite uplinks - shortly all allowed frequencies and ways.

The following criteria should be met:

Primary Criteria

The communication is
decentralized
there is no server through which the main communication streams have to go through and which could collect data to de-anonymise other nodes. ISPs should be preferentially circumvented
encrypted end-to-end
standard, except for emergency calls
Using Perfect Forward Secrecy
session keys should be used. Even future Forward Secrecy shall be tested.
authenticated
The source is authenticated.
anonymised
where it is possible. The nodes know as little as possible about each other. Only neighbouring nodes know each other.

Secondary Criteria

  1. The network shall be as performant as it can be considering the grade of security for the specific services
  2. The infrastructure enables caching and intelligent distribution of public data.
    -> Knowledge representation and file sharing in P2P networks
  3. The solution is holistic, which means it encompasses all layers of the OSI model, i.e. from the strongly delay and packet loss tolerant physical layer through an automatically configured, encrypted and anonymising middle layer to services on the upper layer such as social networking, P2P transfer or generic data storage. However it can also be structured in a different way.
  4. The network is open: that means everyone can easily participate
  5. The code must be:
    • logically verified
    • efficient
    • well documented
    • well tested
    • made public/Open Source
  6. The network has to be resilient: stable, adaptable, fault-tolerant (e.g. against jamming)
  7. Robust against fluctuating node participation
  8. the user interface is intuitively usebable
  9. the user interface represents in an easy way the functionality that is laying beneath
  10. The nodes can be mobile
  11. The infrastructure supports also realtime communication
  12. It is possible to securely update system components
  13. The interface(s) of the software are accessible (to people with impairments/disabilities)
  14. The amount of bandwidth for private usage can be configured
  15. Routing in smartphones must be energy saving
  16. the network is open to connect for example a sneakernet(s)
  17. [to be continued]

Services

public personal/private
Text Chat of local (neighbouring) nodes To a single person: Chat, Email or SMS To multiple people: Chat or mailing list
Audio/Telephony/Video Call among locally restricted nodes normal call conference call
Other formats ? ? ?
  • crypto currency/ pay system
  • Internet
  • Searching in local and other reachable networks
  • filesharing (where location has to be discussed)
  • blogging (where location has to be discussed)
  • Private communication with embedded devices (?)

Contribute

Everyone can contribute according to his/her skills.

You can help

Developers of relevant projects are kindly invited to help out building EDN. You know your project best and which parts (maybe the hole) could be helpful and how.

Note: .onion adresses can be accessed via TOR Browser Bundle

short term

Building the EDN-testbed -> See contribute.

medium-term

Developing a concept of the overall system: contains the purposeful extension of existing approaches or also new developments, in order to fulfill all criteria -> done by discussion see contact.

long term

  1. specification: formal description of all components from the concept, as well as of the criteria (preferably all quantifiable criteria), where possible and sensible
  2. Evaluation: to evaluate the formal model of the specification, whether it fulfills the criteria (e.g. via theorem proof and probabilistic model checking)
  3. Implementation: Implementation of the specification for the different platforms
  4. Testing the implementation as a proof of concept
  5. Distribution of software and hardware, where needed

Federation Network

http://www.federation.network

Contact

Easy way to subscribe to the encrypted EDN-mailinglist

Longer, but privacy enhancing way:

(Every step may be overkill for non tech people. But you can consider to take certain steps described below and skip others)

  • make sure you have an emailadress that
    • is not connected to your name
    • never used your name or other identifiers in an unencrypted email
    • only accessed the mailbox via TOR
      • per webinterface: TOR Browser Bundle
      • per mailclient [plugin torbirdy]
      • or at least per proxy
  • possible email providers are:
  • ask the list for its public key in an empty unsigned message
  • get it and send your public key to the EDN-mailinglist

Why all this efford to stay anonymous? We want our helpers to be as save as possible against possible counter measures such as repression or zersetzung or just being targeted to be surveilled by possible enemies of easy privacy enhancing technology.

Links on the topic Surveillance and Democracy

Mostly German only: