Welcome to GNUnet
What is GNUnet?
GNUnet is peer-to-peer framework providing a network abstractions and
applications focusing on security and privacy. So far, we have
created applications for anonymous file-sharing, decentralized naming
and identity management, decentralized and confidential telephony and
tunneling IP traffic over GNUnet. GNUnet is currently developed by a
worldwide group of independent free software developers. GNUnet is a
GNU package (http://www.gnu.org/).
This is an ALPHA release. There are known and significant bugs as
well as many missing features in this release.
GNUnet is free software released under the GNU Affero General Public
License (v3 or later). For details see the COPYING file in this
directory. If you fork this software, you MUST adjust GNUNET_AGPL_URL
in src/include/gnunet_util_lib.h to point to the source code of your
Additional documentation about GNUnet can be found at
https://gnunet.org/ and in the 'doc/' folder.
These are the direct dependencies for running GNUnet:
- libmicrohttpd >= 0.9.42
- libgcrypt >= 1.6
- libgnurl >= 7.35.0 (recommended, available from https://gnunet.org/gnurl)
- libcurl >= 7.35.0 (alternative to libgnurl)
- libunistring >= 0.9.2
- gnutls >= 3.2.12 (highly recommended a gnutls linked against libunbound)
- libidn2 (prefered)
- libidn >= 1.0
- libextractor >= 0.6.1 (highly recommended)
- openssl >= 1.0 (binary, used to generate X.509 certificate)
- libltdl >= 2.2 (part of GNU libtool)
- sqlite >= 3.8 (default database, required)
- mysql >= 5.1 (alternative to sqlite)
- postgres >= 9.5 (alternative to sqlite)
- Texinfo >= 5.2 [*1]
- which (for the bootstrap script)
These are the dependencies for GNUnet's testsuite:
- Bash (optional (?), for some tests)
- python >= 2.7 (optional, only python 2.7 is supported)
- python-future >= 2.7 (optional, only python 2.7 is supported)
These are the optional dependencies:
- libopus >= 1.0.1 (optional, for experimental conversation tool)
- libpulse >= 2.0 (optional, for experimental conversation tool)
- libogg >= 1.3.0 (optional, for experimental conversation tool)
- libnss (optional, certtool binary (for convenient installation of GNS proxy))
- python-future (optional, for some testcases and utilities)
- python-zbar >= 0.10 (optional, for gnunet-qr)
- TeX Live >= 2012 (optional, for gnunet-bcd[*])
- texi2mdoc (optional, for automatic mdoc generation [*2])
- libglpk >= 4.45 (optional, for experimental code)
- perl5 (optional, for some utilities)
- python >= 2.7 (optional, for gnunet-qr, only python 2.7 is supported)
- bluez (optional, for bluetooth support)
- libpbc >= 0.5.14 (optional, for Attribute-Based Encryption and Identity Provider functionality)
- libgabe (optional, for Attribute-Based Encryption and Identity Provider functionality,
Recommended autotools for compiling the Git version are:
- autoconf >= 2.59
- automake >= 1.11.1
- libtool >= 2.2
[*] Mandatory for compiling the info output of the documentation,
a limited subset ('texlive-tiny' in Guix) is enough.
[*1] The default configuration is to build the info output of the
documentation, and therefore require texinfo. You can pass
'--disable-documentation' to the configure script to change this.
[*2] If you still prefer to have documentation, you can pass
'--with-section7' to build mdoc documentation (experimental
stages in gnunet). If this proves to be reliable, we will
include the mdoc output in the release tarballs.
Contrary to the name, texi2mdoc does not require texinfo,
It is a standalone ISO C utility.
GNUnet's directed acyclic graph (DAG) will require around 0.74 GiB
Diskspace, with GNUNet itself taking around 9.2 MiB reported by the
build on GNU Guix.
How to install?
We recommend to use binary packages provided by your Operating System's
package manager. GNUnet is reportedly available for at least:
GNU Guix, Nix, Debian, ALT Linux, Archlinux, Deepin, Devuan, Hyperbola,
Kali Linux, LEDE/OpenWRT, Manjaro, Parabola, Pardus, Parrot, PureOS,
Raspbian, Rosa, Trisquel, and Ubuntu.
If GNUnet is available for your Operating System and it is missing,
send us feedback so that we can add it to this list. Furthermore, if
you are interested in packaging GNUnet for your Operating System,
get in touch with us at email@example.com if you require
help with this job.
If you were using an Operating System with the apt package manager,
GNUnet could be installed as simple as:
$ apt-get install gnunet
Generic installation instructions are in the INSTALL file in this
Scope of Operating System support
We actively support GNUnet on a broad range of Free Software Operating
For proprietary Operating Systems, like for example Microsoft Windows
or Apple OS X, we accept patches if they don't break anything for
other Operating Systems.
If you are implementing support for a proprietary Operating System,
you should be aware that progress in our codebase could break
functionality on your OS and cause unpredicted behavior we can
not test. However, we do not break support on Operating Systems
with malicious intent.
Regressions which do occur on these Operating Systems are 3rd
class issues and we expect users and developers of these
Operating Systems to send proposed patches to fix regressions.
For more information about our stand on some of the motivating
points here, read the 'Philosophy' Chapter of our handbook.
Building GNUnet from source
IMPORTANT: You can read further notes about compilation from source in
the 'doc/FILENAME' document, which includes notes about specific
requirements for operating systems aswell. If you are a package
mantainer for an Operating System we invite you to add your notes if
you feel it is necessary and can not be covered in your Operating
If you are building GNUnet from source you are either interested
in furthering its development (we have further notes for developer
builds in our 'GNUnet Developer Handbook') or you don't trust other
people's binaries or your Operating System doesn't provide any
binary package (at the moment).
If you're on Gentoo you can build GNUnet using the recipes provided
in the 'youbroketheinternet' overlay. Other Operating Systems may
unintentionally require you to build GNUnet from source.
Two prominent examples which currently lack cross-compilation
support in GNUnet (and native binaries) are MS Windows and Apple macOS.
For macOS we recommend you to do the build process via Homebrew and a
recent XCode installation. We don't recommend using GNUnet with any
recent MS Windows system as it officially spies on its users (according
to its T&C), defying some of the purposes of GNUnet.
Note that some functions of GNUnet require "root" access. GNUnet will
install (tiny) SUID binaries for those functions is you run "make
install" as root. If you do not, GNUnet will still work, but some
functionality will not be available (including certain forms of NAT
GNUnet requires the GNU MP library (https://www.gnu.org/software/gmp/)
and libgcrypt (https://www.gnupg.org/). You can specify the path to
libgcrypt by passing "--with-gcrypt=PATH" to configure. You will also
need either sqlite (http://www.sqlite.org/), MySQL
(http://www.mysql.org/) or PostGres (http://www.postgres.org/).
If you install from source, you need to install GNU libextractor first
(download from https://www.gnu.org/software/libextractor/). We also
recommend installing GNU libmicrohttpd (download from
https://www.gnu.org/software/libmicrohttpd/). Furthermore we recommend
libgnurl (from https://gnunet.org/gnurl).
Then you can start the actual GNUnet compilation process with:
$ export GNUNET_PREFIX=/usr/local/lib # or other directory of your choice
# addgroup gnunetdns
# adduser --system --home "/var/lib/gnunet" --group gnunet --shell /bin/sh
# ./configure --prefix=$GNUNET_PREFIX/.. --with-extractor=$LE_PREFIX
And finally install GNUnet with:
# make install
Complete the process by either adjusting one of our example service files
in 'contrib/services' or by running:
# sudo -u gnunet gnunet-arm -s
Note that running the 'configure' and 'make install' steps as
root (or with sudo) is required as some parts of the installation
require the creation of SUID binaries. The installation will
work if you do not run these steps as root, but some components
may not be installed in the perfect place or with the right
permissions and thus won't work.
This will create the users and groups needed for running GNUnet
securely and then compile and install GNUnet to $GNUNET_PREFIX/../bin/,
$GNUNET_PREFIX/ and $GNUNET_PREFIX/../share/ and start the system
with the default configuration. It is strongly recommended that you
add a user "gnunet" to run "gnunet-arm". You can then still run the
end-user applications as another user.
If you create a system user "gnunet", it is recommended that you edit
the configuration file slightly so that data can be stored in the
system user home directory at "/var/lib/gnunet". Depending on what
the $HOME-directory of your "gnunet" user is, you might need to set
the SERVICEHOME option in section "[PATHS]" to "/var/lib/gnunet" to
do this. Depending on your personal preferences, you may also want to
use "/etc/gnunet.conf" for the location of the configuration file in
this case (instead of ~gnunet/.config/gnunet.conf"). In this case,
you need to start GNUnet using "gnunet-arm -s -c /etc/gnunet.conf" or
You can avoid running 'make install' as root if you run configure
with the "--with-sudo=yes" option and have extensive sudo rights
(can run "chmod +s" and "chown" via 'sudo'). If you run 'make install'
as a normal user without sudo rights (or the configure option),
certain binaries that require additional priviledges will not be
installed properly (and autonomous NAT traversal, WLAN, DNS/GNS and
the VPN will then not work).
If you run 'configure' and 'make install' as root or use the '--with-sudo'
option, GNUnet's build system will install "libnss_gns*" libraries to
"/lib/" regardless (!) of the $GNUNET_PREFIX you might have specified,
as those libraries must be in "/lib/". If you are packaging GNUnet
for binary distribution, this may cause your packaging script to miss
those plugins, so you might need to do some additional manual work to
include those libraries in your binary package(s). Similarly, if you
want to use the GNUnet naming system and did NOT run GNUnet's 'make
install' process with sudo rights, the libraries will be installed to
"$GNUNET_PREFIX" and you will have to move them to "/lib/"
Finally, if you are compiling the code from git, you have to
run "sh ./bootstrap" before running "./configure". If you receive an error during
the running of "sh ./bootstrap" that looks like "macro `AM_PATH_GTK'
not found in library", you may need to run aclocal by hand with the -I
option, pointing to your aclocal m4 macros, i.e.
$ aclocal -I /usr/local/share/aclocal
Note that additional, per-user configuration files can be created by
each user. However, this is usually not necessary as there are few
per-user options that normal users would want to modify. The defaults
that are shipped with the installation are usually just fine.
The gnunet-setup tool is particularly useful to generate the master
configuration for the peer. gnunet-setup can be used to configure and
test (!) the network settings, choose which applications should be run
and configure databases. Other options you might want to control
include system limitations (such as disk space consumption, bandwidth,
etc). The resulting configuration files are human-readable and can
theoretically be created or edited by hand.
gnunet-setup is a separate download and requires somewhat recent
versions of GTK+ and Glade. You can also create the configuration file
by hand, but this is not recommended. For more general information
about the GNU build process read the INSTALL file.
GNUnet uses two types of configuration files, one that specifies the
system-wide defaults (typically located in
$GNUNET_PREFIX/../share/gnunet/config.d/) and a second one that overrides
default values with user-specific preferences. The user-specific
configuration file should be located in "~/.config/gnunet.conf" or its
location can be specified by giving the "-c" option to the respective
For more information about the configuration (as well as usage) refer
to the 'GNUnet User Handbook' chapter of the documentation, included
in this software distribution.
For detailed usage notes, instructions and examples, refer to the
included 'GNUnet User Handbook'.
First, you must obtain an initial list of GNUnet hosts. Knowing a
single peer is sufficient since after that GNUnet propagates
information about other peers. Note that the default configuration
contains URLs from where GNUnet downloads an initial hostlist
whenever it is started. If you want to create an alternative URL for
others to use, the file can be generated on any machine running
GNUnet by periodically executing
$ cat $SERVICEHOME/data/hosts/* > the_file
and offering 'the_file' via your web server. Alternatively, you can
run the build-in web server by adding '-p' to the OPTIONS value
in the "hostlist" section of gnunet.conf and opening the respective
HTTPPORT to the public.
If the solution with the hostlist URL is not feasible for your
situation, you can also add hosts manually. Simply copy the hostkeys
to "$SERVICEHOME/data/hosts/" (where $SERVICEHOME is the directory
specified in the gnunet.conf configuration file). You can also use
"gnunet-peerinfo -g" to GET a URI for a peer and "gnunet-peerinfo -p
URI" to add a URI from another peer. Finally, GNUnet peers that use
UDP or WLAN will discover each other automatically (if they are in the
vicinity of each other) using broadcasts (IPv4/WLAN) or multicasts
The local node is started using "gnunet-arm -s". We recommend to run
GNUnet 24/7 if you want to maximize your anonymity, as this makes
partitioning attacks harder.
Once your peer is running, you should then be able to access GNUnet
using the shell:
$ gnunet-search KEYWORD
This will display a list of results to the console. You can abort
the command using "CTRL-C". Then use
$ gnunet-download -o FILENAME GNUNET_URI
to retrieve a file. The GNUNET_URI is printed by gnunet-search
together with a description. To publish files on GNUnet, use the
The GTK+ (or: Gimp Toolkit) user interface is shipped separately.
After installing gnunet-gtk, you can invoke the setup tool and
the file-sharing GUI with:
For further documentation, see our webpage or the 'GNUnet User Handbook',
included in this software distribution.
Contributions are welcome. Please submit bugs you find to
Please make sure to run the script "contrib/scripts/gnunet-bugreport"
and include the output with your bug reports. More about how to
report bugs can be found in the GNUnet FAQ on the webpage. Submit
patches via E-Mail to firstname.lastname@example.org, formated with
In order to run the unit tests by hand (instead of using "make check"),
you need to set the environment variable "GNUNET_PREFIX" to the
directory where GNUnet's libraries are installed.
Before running any testcases, you must complete the installation.
$ ./configure --prefix=$SOMEWHERE
$ make install
$ export $GNUNET_PREFIX=$SOMEWHERE
$ make check
Some of the testcases require python >= 2.7, and the python modules
"python-future" (http://python-future.org/) and "pexpect" to be installed.
If any testcases fail to pass on your system, run
"contrib/scripts/gnunet-bugreport" (in the repository) or "gnunet-bugreport"
when you already have GNUnet installed and report its output together with
information about the failing testcase(s) to the Mantis bugtracking
system at https://gnunet.org/bugs/.
Running HTTP on port 80 and HTTPS on port 443
In order to hide GNUnet's HTTP/HTTPS traffic perfectly, you might
consider running GNUnet's HTTP/HTTPS transport on port 80/443.
However, we do not recommend running GNUnet as root. Instead, forward
port 80 to say 1080 with this command (as root, in your startup
# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 1080
or for HTTPS
# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 4433
Then set in the HTTP section of gnunet.conf the "ADVERTISED_PORT" to
"80" and "PORT" to 1080 and similarly in the HTTPS section the
"ADVERTISED_PORT" to "443" and "PORT" to 4433.
You can do the same trick for the TCP and UDP transports if you want
to map them to a priviledged port (from the point of view of the
network). However, we are not aware of this providing any advantages
at this point.
If you are already running an HTTP or HTTPS server on port 80 (or 443),
you may be able to configure it as a "ReverseProxy". Here, you tell
GNUnet that the externally visible URI is some sub-page on your website,
and GNUnet can then tunnel its traffic via your existing HTTP server.
This is particularly powerful if your existing server uses HTTPS, as
it makes it harder for an adversary to distinguish normal traffic to
your server from GNUnet traffic. Finally, even if you just use HTTP,
you might benefit (!) from ISP's traffic shaping as opposed to being
throttled by ISPs that dislike P2P. Details for configuring the
reverse proxy are documented on our website.
A HTML version of the new GNUnet manual is deployed at
which currently displays just GNUnet documentation. Until 2019
we will add more reading material.
* Academia / papers
In almost 20 years various people in our community have written and
collected a good number of papers which have been implemented in
GNUnet or projects around GNUnet.
There are currently 2 ways to get them:
* Using git:
git clone https://gnunet.org/git/bibliography.git
* Using Drupal:
The Drupal access will be replaced by a new interface to our
bibliography in 2019.