News 2020

We are pleased to announce the release of GNUnet 0.14.0. This is a new major release. It breaks protocol compatibility with the 0.13.x versions. Please be aware that Git master is thus henceforth INCOMPATIBLE with the 0.13.x GNUnet network, and interactions between old and new peers will result in issues. 0.13.x peers will be able to communicate with Git master or 0.13.x peers, but some services - in particular GNS - will not be compatible. 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 and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.14.0 release is still only suitable for early adopters with some reasonable pain tolerance.
[read more]

We are happy to announce the completion of the fourth and last milestone for the GNS Specification. The fourth milestone consists of involving a broader community for feedback and improvements:
[read more]

Continuing to "release early / release often", we present GNUnet 0.13.3. This is a bugfix release for gnunet 0.13.2. It fixes some build issues and contains major changes to the re:claimID API.
[read more]

This is a bugfix release for gnunet 0.13.1. It fixes some build issues and contains changes to the REST API implmementation (no change in the API itself) as well as OpenID Connect related fixes to re:claimID.
[read more]

This is a bugfix release for gnunet and gnunet-gtk specifically. For gnunet, no changes to the source have been made. However, the default configuration had to be modified to support the changes made in 0.13.0. For gnunet-gtk, this fixes a more serious issue where the 0.13.0 tarball failed to build.
[read more]

We are pleased to announce the release of GNUnet 0.13.0. This is a new major release. It breaks protocol compatibility with the 0.12.x versions. Please be aware that Git master is thus henceforth INCOMPATIBLE with the 0.12.x GNUnet network, and interactions between old and new peers will result in signature verification failures. 0.12.x peers will NOT be able to communicate with Git master or 0.13.x peers. 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 and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.13.0 release is still only suitable for early adopters with some reasonable pain tolerance.
[read more]

We are happy to announce the completion of the third milestone for the GNS Specification. The third milestone consists of documenting the GNS zone revocation process. As part of this, we have reworked the proof-of-work algorithms in GNUnet also used for GNS revocations. The (protocol breaking) changes will be released as part of GNUnet 0.13.0. The specification document LSD001 can be found at:
[read more]

We are happy to announce that we will have a GNUnet Hacker Meeting from 17-21 of June 2020 taking place online. For more information see here.
[read more]

We are pleased to announce the release of GNUnet 0.12.2. This is a new bugfix release. 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 and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.12.2 release is still only suitable for early adopters with some reasonable pain tolerance.
[read more]

We are happy to announce the completion of the second milestone for the GNS Specification. The second milestone consists of documenting the GNS name resolution process and record handling. With the release of GNUnet 0.12.x, the currently specified protocol is implemented according to the specification. As before, the draft specification LSD001 can be found at:
[read more]