ITF (Internet Engineering Task Force) Committee, responsible for the development of the protocols and architecture of the Internet, officially completed The formation of RFC for the new GNS domain name system (GNU Name System) developed by the GNUNET project. This system is fully decentralized and inaccessible to censorship an alternative to traditional DNS. GNS specification, published as rfc-9498, now has the status of the “proposed standard”.
A feature of gns is its ability to work in parallel with DNS, allowing it to use it in traditional applications, including web browsers. A distinctive feature of GNS compared to DNS is its structure: instead of the tree hierarchy of GNS servers, it uses a oriented graph, which enhances the confidentiality of data exchange. The converting of names into GNS is similar to DNS, but requests and answers are performed with the preservation of confidentiality.
Security issues in GNS are resolved using cryptography. To determine the DNS zone in GNS, ECDSA keys are used based on the elliptical curves Curve25519. This choice calls discussions among specialists, since curve25519 is usually used with the algorithm ED25519, which is considered more modern and safe than ECDSA. In addition, the size of a closed key of 32 bytes raises questions and the size of a closed key, which is less than the standard 64 bytes.
HIRARCHIC CLOCES OF HEARCH OF GNS, which allows you to use the root open key to extracting daughter open keys without access to closed root keys, recalls the method used in the Bitcoin system. Additionally, GNS uses cascading symmetrical encryption that combines AES and Twofish algorithms in CFB mode
The GNS implementation fully corresponded to the RFC is already included in the latest version of the Gnunet 0.20.0 platform and is available in the code base of the project gnunet- Go.