GNUnet GNU’s decentralized anonymous and censorship-resistant P2P framework.*	*

• Witamy
• Kontakt
• Społeczność
• FAQ
• Download
• Dokumentacja
• Publikacje
• Linki

Protokoły

GNUnet uses protocols in three different contexts.*

1. The first and most important protocol family is the peer-to-peer protocol.* This protocol defines how nodes in the network exchange information with each other.* The peer-to-peer protocol defines messages for peer discovery, encryption, availability and other, application specific messages.* All peers in the network must support a certain core subset of the peer-to-peer messages.* The peer-to-peer messages are exchanged between gnunetd processes.* The mechanisms of exchange are encapsulated in the transport services.*
2. The second protocol family is the client-server protocol.* The client-server protocol is used between gnunetd and the GNUnet tools.* Since gnunetd is a deamon process that runs in the background, the user must be able to interact with gnunetd.* GNUnet uses a TCP connection, typically via loopback, to allow GNUnet clients to send requests to gnunetd.* For these clients, the GNUnet tools, gnunetd acts as a server, and not as a peer.* Note that GNUnet clients are ultimately trusted.* GNUnet does not encrypt the TCP traffic between client and server since this connection should only ever be allowed either via loopback or on a trusted LAN.* Which hosts are allowed to connect as clients to gnunetd is specified in the configuration file.*
3. The third family of GNUnet protocols is used in the transport layer.* The transport layer encapsulates the sending and receiving of peer-to-peer messages.* Every GNUnet peer must support at least one transport protocol.* Transport protocols differ in performance, system requirements and ease-of-use.* Each transport protocol also defines its own format for a host address.* Host addresses can be anything from a simple IP:PORT combination to an http URL or an E-mail address.* While a single peer can have as many addresses as transports, every peer is uniquely identified by its identity, which is the hash of its public key.*

Overview*

The protocols are described in the following sections:*

1. Peer-2-Peer (P2P)
   1. GNUnet core*
   2. GAP*
   3. RPC*
   4. DHT*
2. Klient-Server
   1. GNUnet core*
   2. getoption*
   3. stats*
   4. traffic*
   5. fs*
3. Transport Services*
   1. UDP
   2. TCP
   3. HTTP*
   4. SMTP

Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008 Christian Grothoff.
Verbatim copying and distribution of this entire article
is permitted in any medium, provided this notice is preserved.

Translation engine based on i18nHTML (C) 2003, 2004, 2005, 2006, 2007 Christian Grothoff.