GNU Project has presented the release of the framework Gnunet 0.20, designed to build protected decentralized P2P networks.
The networks created using Gnunet do not have a single refusal point and are able to guarantee the inviolability of private information of users, including excluding possible abuse by special services and administrators who have access to the network nodes.
Gnunet supports the creation of P2P networks on top of TCP, UDP, HTTP/HTTPS, Bluetooth, and WLAN, and can operate in F2F (Friend-to-Friend) mode.
The framework supports NAT bypass, including using UPNP and ICMP.
To address data placement, a distributed hash table (DHT) can be used.
It also provides means for deploying MESH networks.
For selective provision and recall of access rights, a decentralized exchange of identification attributes called
reclaimid is used, along with the gnu name system (GNS) and attribute-based encryption.
The system is characterized by low resource consumption and the use of multiprocess architecture to ensure insulation between components.
It provides flexible means for conducting logs and accumulation of statistics.
Gnunet offers an API for the SI and Binding language for other programming languages to develop final applications.
Instead of using flows, it proposes using events processing cycles and processes to simplify development.
Additionally, a test library for automatic deployment of experimental networks is included, which covers tens of thousands of feasts.
Several ready-made applications are being developed based on the GNUNET technology, which include:
- Delivery system GNS (GNU Name System), which acts as a fully decentralized and censorship-resistant replacement for DNS.
GNS can be used alongside DNS and in traditional applications like web browsers.
Unlike DNS, GNS uses a directed graph instead of the tree hierarchy of servers.
The conversion of names is similar to DNS, but requests and answers are performed with the preservation of confidentiality.
The processing request node does not know who the answer is given, and transit nodes and third-party observers cannot decipher the requests and answers.
The integrity and immutability of records are ensured by the use of cryptographic mechanisms.
The DNS zone