Services

These services comprise a backbone of core services for peer-to-peer applications to use.

• ATS — Automatic transport selection
• CADET — Confidential Ad-hoc Decentralized End-to-end Transport
• CORE — GNUnet link layer
  • When is a peer "connected"?
  • The CORE Client-Service Protocol
    • Setup2
    • Notifications
    • Sending
  • The CORE Peer-to-Peer Protocol
    • Creating the EphemeralKeyMessage
    • Establishing a connection
    • Encryption and Decryption
    • Type maps
• DHT — Distributed Hash Table
  • Block library and plugins
    • What is a Block?
    • The API of libgnunetblock
    • Queries
    • Sample Code
    • Conclusion2
    • GET
    • PUT
    • MONITOR
    • DHT Routing Options
  • The DHT Client-Service Protocol
    • PUTting data into the DHT
    • GETting data from the DHT
    • Monitoring the DHT
  • The DHT Peer-to-Peer Protocol
    • Routing GETs or PUTs
    • PUTting data into the DHT
    • GETting data from the DHT
• FS — File sharing over GNUnet
  • Namespace Advertisements
  • KSBlocks
    • File-sharing persistence directory structure
• GNS and GNS Support
  • GNS — the GNU Name System
    • Looking up records
    • Accessing the records
    • Creating records
    • Future work
      • libgnunetgnsrecord
    • Value handling
    • Type handling
      • GNS plugins
      • The GNS Client-Service Protocol
      • Hijacking the DNS-Traffic using gnunet-service-dns
    • Network Setup Details
      • Importing DNS Zones into GNS
    • Conversions between DNS and GNS
    • DNS Zone Size
    • Performance
      • Registering names using the FCFS daemon
    • Obtaining information from the daemon
    • Submitting data to the daemon
    • Customizing the HTML output
  • NAMECACHE — DHT caching of GNS results
    • The NAMECACHE Client-Service Protocol
      • Lookup
      • Store
    • The NAMECACHE Plugin API
      • Lookup2
      • Store2
  • NAMESTORE — Storage of local GNS zones
    • Editing Zone Information
    • Transactional operations
    • Iterating Zone Information
    • Monitoring Zone Information
• HOSTLIST — HELLO bootstrapping and gossip
  • HELLOs
  • Overview for the HOSTLIST subsystem
    • Features
    • HOSTLIST - Limitations
  • Interacting with the HOSTLIST daemon
  • Hostlist security address validation
    • The HTTP Server
    • Advertising the URL
  • The HOSTLIST client
    • Bootstrapping
  • Usage
• IDENTITY — Ego management
  • Connecting to the service
  • Operations on Egos
  • The anonymous Ego
  • Convenience API to lookup a single ego
  • Associating egos with service functions
    • The IDENTITY Client-Service Protocol
• MESSENGER — Room-based end-to-end messaging
  • MERGE-message
  • INVITE-message
  • TEXT-message
  • FILE-message
  • DELETE-message
    • Member sessions
• NSE — Network size estimation
  • Motivation
    • Example
    • Algorithm
    • Target value
    • Timing
    • Controlled Flooding
    • Calculating the estimate
    • Results
    • Examples
  • The NSE Client-Service Protocol
  • The NSE Peer-to-Peer Protocol
• PEERINFO — Persistent HELLO storage
  • PEERINFO - Features
  • PEERINFO - Limitations
  • DeveloperPeer Information
  • Startup
  • Managing Information
  • Obtaining Information
  • The PEERINFO Client-Service Protocol
    • Connecting to the PEERINFO Service
    • Adding Information to the PEERINFO Service
    • Obtaining Information from the PEERINFO Service
• PEERSTORE — Extensible local persistent data storage
  • Functionality
  • Architecture
• REGEX — Service discovery using regular expressions
  • How to run the regex profiler
• REST — RESTful GNUnet Web APIs
  • Namespace considerations
  • Endpoint documentation
• REVOCATION — Ego key revocation
  • Dissemination
  • Revocation Message Design Requirements
    • Querying for revoked keys
    • Preparing revocations
    • Issuing revocations
  • The REVOCATION Client-Service Protocol
  • The REVOCATION Peer-to-Peer Protocol
• RPS — Random peer sampling
  • Brahms
• Peer-to-Peer Set Operations
  • SET — Peer to peer set operations (Deprecated)
    • Local Sets
    • Set Modifications
    • Set Operations
    • Result Elements
      • Sets
      • Listeners
      • Operations
      • Supplying a Set
      • The Result Callback
    • The SET Client-Service Protocol
      • Creating Sets
      • Listeners
      • Initiating Operations
      • Modifying Sets
      • Results and Operation Status
      • Iterating Sets
    • The SET Intersection Peer-to-Peer Protocol
      • The Bloom filter exchange
      • Salt
    • The SET Union Peer-to-Peer Protocol
  • SETI — Peer to peer set intersections
    • Intersection Sets
    • Set Intersection Modifications
    • Set Intersection Operations
    • Intersection Result Elements
      • Intersection Set API
      • Intersection Listeners
      • Intersection Operations
      • Supplying a Set for Intersection
      • The Intersection Result Callback
    • The SETI Client-Service Protocol
      • Creating Intersection Sets
      • Listeners for Intersection
      • Initiating Intersection Operations
      • Modifying Intersection Sets
      • Intersection Results and Operation Status
    • The SETI Intersection Peer-to-Peer Protocol
      • The Bloom filter exchange in SETI
      • Intersection Salt
  • SETU — Peer to peer set unions
    • Union Sets
    • Set Union Modifications
    • Set Union Operations
    • Union Result Elements
      • Union Set API
      • Union Listeners
      • Union Operations
      • Supplying a Set for Union
      • The Union Result Callback
    • The SETU Client-Service Protocol
      • Creating Union Sets
      • Listeners for Union
      • Initiating Union Operations
      • Modifying Union Sets
      • Union Results and Operation Status
        • The SETU Union Peer-to-Peer Protocol
• STATISTICS — Runtime statistics publication
  • Statistics retrieval
  • Setting statistics and updating them
  • Watches
    • The STATISTICS Client-Service Protocol
  • Statistics retrieval
  • Setting and updating statistics
  • Watching for updates
• TRANSPORT-NG — Next-generation transport management
  • Design goals of TNG
  • HELLO-NG
  • Priorities and preferences
  • Communicators
    • UDP communicator
    • TCP communicator
    • QUIC communicator
• TRANSPORT — Overlay transport management
  • Address validation protocol
  • NAT library
  • Distance-Vector plugin
  • SMTP plugin
  • Why use SMTP for a peer-to-peer transport?
  • How does it work?
  • How do I configure my peer?
  • How do I test if it works?
  • How fast is it?
  • Bluetooth plugin
  • What do I need to use the Bluetooth plugin transport?
  • How does it work2?
  • What possible errors should I be aware of?
  • How do I configure my peer2?
  • How can I test it?
  • The implementation of the Bluetooth transport plugin
    • Linux functionality
    • THE INITIALIZATION
    • THE LOOP
    • Details about the broadcast implementation
    • Pending features
  • WLAN plugin
• VPN and VPN Support