GNUnet 0.11.3 released

We are pleased to announce the release of GNUnet 0.11.3.
This is a bugfix release for 0.11.2, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.3 release is still only suitable for early adopters with some reasonable pain tolerance.

Download links

(gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.3.)

Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try

Note that GNUnet is now started using gnunet-arm -s. GNUnet should be stopped using gnunet-arm -e.

Noteworthy changes in 0.11.3 (since 0.11.2)

  • gnunet-zoneimport now handles -h correctly
  • iptables and other similar binaries are no longer hard-coded but detected at configure time (with hard-coded fallback locations).
  • make uninstall now properly uninstalls all files
  • Passing the no longer available --with-nssdir configuration option now results in a hard error.
  • GNUNET_memcmp() and GNUNET_is_zero() macros introduced for improved type safety (but not yet used consistently).

Known Issues

  • There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.
  • There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.
  • There are known moderate design issues in FS that also impact usability and performance.
  • There are minor implementation limitations in SET that create unnecessary attack surface for availability.
  • The RPS subsystem remains experimental.
  • Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.

In addition to this list, you may also want to consult our bug tracker at which lists about 190 more specific issues.


This release was the work of many people. The following people contributed code and were thus easily identified: ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius Bünger.