Next: , Up: Installing GNUnet   [Contents]

1.1 Obtaining a stable version

Download the tarball from ‘’.

Make sure to download the associated .sig file and to verify the authenticity of the tarball against it, like this:

$ wget
$ gpg --verify-files gnunet-0.11.8.tar.gz.sig

If this command fails because you do not have the required public key, then you need to run the following command to import it:

$ gpg --keyserver --recv-keys 48426C7E

and rerun the gpg --verify-files command.

Note: The pub key to sign the 0.10.1 release has been revoked. You will get an error message stating that there is no known public key or that it has been revoked. The next release of GNUnet will have a valid signature again. We are sorry for the inconvenience this causes. Another possible source you could use is our "gnunet" git repository which, since the change from SVN to git in 2016, has mandatory signed commits by every developer.

After verifying the signature you can extract the tarball. The resulting directory will be renamed to gnunet, which we will be using in the remainder of this document to refer to the root of the source directory.

$ tar xvzf gnunet-0.11.8.tar.gz
$ mv gnunet-0.11.8 gnunet

However, please note that stable versions can be very outdated. As a developer you are strongly encouraged to use the version from the git server.