{"id":23803997,"url":"https://github.com/thejackimonster/gnunet","last_synced_at":"2026-02-26T18:08:48.961Z","repository":{"id":217445250,"uuid":"743866779","full_name":"TheJackiMonster/gnunet","owner":"TheJackiMonster","description":"Mirror from https://git.gnunet.org/gnunet.git","archived":false,"fork":false,"pushed_at":"2025-03-14T16:19:13.000Z","size":101385,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-03-27T00:54:17.576Z","etag":null,"topics":["framework","gnunet","network"],"latest_commit_sha":null,"homepage":"https://www.gnunet.org","language":"C","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"agpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/TheJackiMonster.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-01-16T06:45:56.000Z","updated_at":"2025-03-14T16:19:24.000Z","dependencies_parsed_at":"2024-08-29T12:26:47.981Z","dependency_job_id":"058cb200-d808-4200-8bdd-4fdafe86f6fe","html_url":"https://github.com/TheJackiMonster/gnunet","commit_stats":null,"previous_names":["thejackimonster/gnunet"],"tags_count":78,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TheJackiMonster%2Fgnunet","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TheJackiMonster%2Fgnunet/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TheJackiMonster%2Fgnunet/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TheJackiMonster%2Fgnunet/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/TheJackiMonster","download_url":"https://codeload.github.com/TheJackiMonster/gnunet/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248688565,"owners_count":21145766,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["framework","gnunet","network"],"created_at":"2025-01-01T22:37:02.015Z","updated_at":"2026-02-26T18:08:48.946Z","avatar_url":"https://github.com/TheJackiMonster.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"                       Welcome to GNUnet\n\nToC\n===\n\n* ToC\n* What is GNUnet?\n* Joining GNU\n* Dependencies\n  o Build tools\n  o Dependencies of GNUnet\n  o Dependencies of optional components/functionality\n  o Test suite dependencies\n  o Recommended developer tools\n* Notes on setuid\n* Scope of Operating System support\n* How to install\n  o binary packages\n  o Building GNUnet from source\n  o Notes on compiling from Git\n* Configuration\n* Usage\n* Hacking GNUnet\n* Running HTTP on port 80 and HTTPS on port 443\n* Further Reading\n* Stay tuned\n\n\nWhat is GNUnet?\n===============\n\nGNUnet is peer-to-peer framework providing a network abstractions and\napplications focusing on security and privacy.  So far, we have\ncreated applications for anonymous file-sharing, decentralized naming\nand identity management, decentralized and confidential telephony and\ntunneling IP traffic over GNUnet.  GNUnet is currently developed by a\nworldwide group of independent free software developers.  GNUnet is a\nGNU package (http://www.gnu.org/).\n\nThis is an ALPHA release.  There are known and significant bugs as\nwell as many missing features in this release.\n\nGNUnet is free software released under the GNU Affero General Public\nLicense (v3 or later). For details see the COPYING file in this\ndirectory.  If you fork this software, you MUST adjust GNUNET_AGPL_URL\nin src/include/gnunet_util_lib.h to point to the source code of your\nfork!\n\nAdditional documentation about GNUnet can be found at\nhttps://gnunet.org/ and in the 'doc/' folder.\nOnline documentation is provided at\n'https://docs.gnunet.org' and 'https://tutorial.gnunet.org'.\n\n\nJoining GNU\n===========\n\nThis is a GNU program, developed by the GNU Project and part of the\nGNU Operating System. If you are the author of an awesome program and\nwant to join us in writing Free Software, please consider making it an\nofficial GNU program and become a GNU maintainer.  You can find\ninstructions on how to do so at http://www.gnu.org/help/evaluation.\nWe are looking forward to hacking with you!\n\n\nDependencies:\n=============\n\nThe dependencies for building GNUnet will require around 0.74 GiB\ndiskspace. GNUnet itself will require 8 - 9.2 MiB depending on\nconfiguration.\n\nBuild tools for compiling GNUnet from source:\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n- gcc or clang\n- meson              \u003e= 1.0.0\n- recutils           \u003e= 1.0         (building from git)\n- libtool            \u003e= 2.2\n- makeinfo           \u003e= 4.8\n- make[*3]\n- pkgconf or pkg-config\n- sphinx\n- sphinx-rtd-theme\n- sphinx-multiversion\n\nDirect dependencies of GNUnet:\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n- Bash                              (for some scripts)\n- gettext            \u003e= 0.21\n- libcurl            \u003e= 7.85.0      (ideally built against gnutls)\n- libgcrypt          \u003e= 1.6\n- libgmp             any            (is also an indirect dependency of gcrypt)\n- libunistring       \u003e= 0.9.2\n- libidn:\n  * libidn2 (preferred)\n  or\n  * libidn           \u003e= 1.0\n- libmicrohttpd      \u003e= 0.9.63\n- libjansson\n- nss                               (certutil binary, for\n                                     gnunet-gns-proxy-setup-ca)\n- openssl            \u003e= 1.0         (binary, used to generate\n                                     X.509 certificate\n                                     for gnunet-gns-proxy-setup-ca)\n- libltdl            \u003e= 2.2         (part of GNU libtool)\n- sqlite             \u003e= 3.35.0      (default database, required)\n- which                             (contrib/apparmor(?), gnunet-bugreport,\n                                     and possibly more)\n- zlib\n- libsodium          \u003e= 1.0.17      (for elliptic curve cryptography)\n- certtool (gnutls or openssl)      (certtool binary (for convenient\n                                     installation of GNS proxy))\n\nDependencies of optional components/functionality:\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n- Database plugins (alternatives to sqlite):\n  * postgres         \u003e= 9.5\n- Transport plugins:\n  * bluez (bluetooth transport)\n- Conversation service:\n  * libopus          \u003e= 1.0.1\n  * libpulse         \u003e= 2.0\n  * libogg           \u003e= 1.3.0\n- File-sharing metadata (highly recommended[*5]):\n  * libextractor     \u003e= 0.6.1\n- NAT uPnP support:\n  * miniupnpc\n- gnunet-qr (Read/write GNUnet URIs from/to QR codes):\n  * libzbar          \u003e= 0.10\n- gnunet-bcd (GNS business card generator):\n  * TeX Live         \u003e= 2012        (for gnunet-bcd[*])\n- gnunet-gns-proxy (Reverse SOCKS proxy for GNS lookups)\n  * gnutls           \u003e= 3.2.12      (highly recommended a gnutls\n                                       linked against libunbound)\n- PABC credential support\n  * libpabc          any            (for re:claimID zero-knowledge privacy\n                                      credentials)\n- re:claimID OpenID Connect plugin\n  * libjose          any            (for re:claimID OpenID Connect support)\n- gnunet-bcd:\n  * TeX Live         \u003e= 2012\n\nAdditional dependencies to run the GNUnet testsuite:\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n- Bash                              (for some tests[*4])\n- A Posix Shell                     (for some tests)\n- python             \u003e= 3.4         (3.4 and higher technically supported,\n                                     at least python 3.7 tested to work)\n- base tools\n  - mostly:\n    - bc,\n    - curl,\n    - sed,\n    - awk,\n    - which\n\n\nRecommended software for developer tools:\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n- awk                               (for linting tests)\n- Bash                              (for Docker and Vagrant)\n- grof                              (for linting of man pages)\n- mandoc                            (for linting of man pages, generation of\n                                     html output of man pages (not part of\n                                     the regular build))\n- perl5                             (for some utilities)\n\n\n[*] Mandatory for compiling the info output of the documentation,\n    a limited subset ('texlive-tiny' in Guix) is enough.\n\n[*1] The default configuration is to build the info output of the\n     documentation, and therefore require sphinx.  You can pass\n     '--disable-documentation' to the configure script to change this.\n\n[*3] GNU make introduced the != operator in version 4.0.\n     GNU make was released in october 2013, reasonable to\n     be widespread by now. If this is not working out for\n     you, open a bug so that we can get a more portable\n     fix in.\n\n[*4] We are committed  to portable tools and solutions\n     where possible. New scripts should be Posix sh\n     compatible, current and older scripts are\n     in the process of being rewritten to comply\n     with this requirement.\n\n[*5] While libextractor (\"LE\") is optional, it is recommended to\n     build gnunet against it. If you install it later,\n     you won't benefit from libextractor.\n     If you are a distributor, we recommend to split\n     LE into basis + plugins rather than making LE\n     an option as an afterthought by the user.\n     LE itself is very small, but its dependency chain\n     on first, second, third etc level can be big.\n     There is a small effect on privacy if your LE build\n     differs from one which includes all\n     plugins (plugins are build as shared objects):\n     if users publish a directory with a mixture of file\n     types (for example mpeg, jpeg, png, gif) the\n     configuration of LE could leak which plugins are\n     installed for which filetypes are not providing\n     more details.\n     However, this leak is just a minor concern.\n\nNotes on setuid\n===============\n\nFor a correct functionality depending on the host OS, you need\nto run the equivalent of these steps after installation.\nReplace $(DESTDIR)$(libexecdir) with the appropriate paths,\nfor example /usr/local/lib/gnunet/libexec/. Note that this\nobviously must be run as privileged user.\n\nchown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn\nchmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn\nchown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-transport-wlan\nchmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-transport-wlan\nchown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-transport-bluetooth\nchmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-transport-bluetooth\nchown root $(DESTDIR)$(libexecdir)/gnunet-helper-dns\nchgrp $(GNUNETDNS_GROUP) $(DESTDIR)$(libexecdir)/gnunet-helper-dns\nchmod 4750 $(DESTDIR)$(libexecdir)/gnunet-helper-dns\nchgrp $(GNUNETDNS_GROUP) $(DESTDIR)$(libexecdir)/gnunet-service-dns\nchown gnunet:$(GNUNETDNS_GROUP) $(DESTDIR)$(libexecdir)/gnunet-service-dns\nchmod 2750 $(DESTDIR)$(libexecdir)/gnunet-service-dns\nchown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-exit\nchmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-exit\nchown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-nat-server\nchown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-nat-client\nchmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-nat-server\nchmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-nat-client\n\n\nScope of Operating System support\n=================================\n\nWe actively support GNUnet on a broad range of Free Software Operating\nSystems.\n\nFor proprietary Operating Systems, like for example Microsoft Windows\nor Apple OS X, we accept patches if they don't break anything for\nother Operating Systems.\nIf you are implementing support for a proprietary Operating System,\nyou should be aware that progress in our codebase could break\nfunctionality on your OS and cause unpredicted behavior we can\nnot test. However, we do not break support on Operating Systems\nwith malicious intent.\nRegressions which do occur on these Operating Systems are 3rd\nclass issues and we expect users and developers of these\nOperating Systems to send proposed patches to fix regressions.\n\nFor more information about our stand on some of the motivating\npoints here, read the 'Philosophy' Chapter of our handbook.\n\n\nHow to install?\n===============\n\nbinary packages\n~~~~~~~~~~~~~~~\n\nWe recommend to use binary packages provided by the package manager integrated\nwithin your Operating System. GNUnet is reportedly available for at least:\n\nALT Linux, Archlinux, Debian, Deepin, Devuan, GNU Guix, Hyperbola,\nKali Linux, LEDE/OpenWRT, Manjaro, Nix, Parabola, Pardus, Parrot,\nPureOS, Raspbian, Rosa, Trisquel, and Ubuntu.\n\nIf GNUnet is available for your Operating System and it is missing,\nsend us feedback so that we can add it to this list. Furthermore, if\nyou are interested in packaging GNUnet for your Operating System,\nget in touch with us at gnunet-developers@gnu.org if you require\nhelp with this job.\n\nIf you were using an Operating System with the apt package manager,\nGNUnet could be installed as simple as:\n\n$ apt-get install gnunet\n\nGeneric installation instructions are in the INSTALL file in this\ndirectory.\n\nBuilding GNUnet from source\n~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nIMPORTANT: You can read further notes about compilation from source in\nthe handbook under doc/handbook/, which includes notes about specific\nrequirements for operating systems as well. If you are a package\nmaintainer for an Operating System we invite you to add your notes if\nyou feel it is necessary and can not be covered in your Operating\nSystem's documentation.\n\nTwo prominent examples which currently lack cross-compilation\nsupport in GNUnet (and native binaries) are MS Windows and Apple macOS.\nFor macOS we recommend you to do the build process via Homebrew and a\nrecent XCode installation. We don't recommend using GNUnet with any\nrecent MS Windows system as it officially spies on its users (according\nto its T\u0026C), defying some of the purposes of GNUnet.\n\nNote that some functions of GNUnet require \"root\" access.  GNUnet will\ninstall (tiny) SUID binaries for those functions is you install as root.\nIf you do not, GNUnet will still work, but some\nfunctionality will not be available (including certain forms of NAT\ntraversal).\n\nGNUnet requires the GNU MP library (https://www.gnu.org/software/gmp/)\nand libgcrypt (https://www.gnupg.org/).  You can specify the path to\nlibgcrypt by passing \"--with-gcrypt=PATH\" to configure.\n\nIf you install from source, you need to install GNU libextractor first\n(download from https://www.gnu.org/software/libextractor/).  We also\nrecommend installing GNU libmicrohttpd (download from\nhttps://www.gnu.org/software/libmicrohttpd/). Furthermore we recommend\nlibgnurl (from https://gnunet.org/en/gnurl.html).\nThen you can start the actual GNUnet compilation process with:\n\n\n$ export GNUNET_PREFIX=/usr/local/lib # or other directory of your choice\n# addgroup gnunetdns\n# adduser --system --home \"/var/lib/gnunet\" --group gnunet --shell /bin/sh\n# meson setup -Dprefix=$GNUNET_PREFIX/.. -C $BUILDDIR\n$ meson compile -C $BUILDDIR\n\nYou can alternatively also use the configure script and Makefile:\n\n$ ./configure --prefix=$GNUNET_PREFIX/..\n$ make\n\nAnd finally install GNUnet with:\n\n# meson install -C $BUILDDIR\n\nor\n\n# make install\n\nComplete the process by either adjusting one of our example service files\nin 'contrib/services' or by running:\n\n# sudo -u gnunet gnunet-arm -s\n\n\nNote that you must read paragraph \"Notes on setuid\", which documents steps you\nhave to follow after the installation, as a privileged user. We require some\nbinaries to be setuid. The most portable approach across all supported\nplatforms and targets is to let this be handled manually.\nThe installation will work if you do not run these steps as root, but some\ncomponents may not be installed in the perfect place or with the right\npermissions and thus won't work.\n\nThis will create the users and groups needed for running GNUnet\nsecurely and then compile and install GNUnet to $GNUNET_PREFIX/../bin/,\n$GNUNET_PREFIX/ and $GNUNET_PREFIX/../share/ and start the system\nwith the default configuration.  It is strongly recommended that you\nadd a user \"gnunet\" to run \"gnunet-arm\".  You can then still run the\nend-user applications as another user.\n\nIf you create a system user \"gnunet\", it is recommended that you edit\nthe configuration file slightly so that data can be stored in the\nsystem user home directory at \"/var/lib/gnunet\".  Depending on what\nthe $HOME-directory of your \"gnunet\" user is, you might need to set\nthe SERVICEHOME option in section \"[PATHS]\" to \"/var/lib/gnunet\" to\ndo this.  Depending on your personal preferences, you may also want to\nuse \"/etc/gnunet.conf\" for the location of the configuration file in\nthis case (instead of ~gnunet/.config/gnunet.conf\").  In this case,\nyou need to start GNUnet using \"gnunet-arm -s -c /etc/gnunet.conf\" or\nset \"XDG_CONFIG_HOME=/etc/\".\n\nYou can avoid running 'make install' as root if you have extensive sudo rights\n(can run \"chmod +s\" and \"chown\" via 'sudo').  If you run 'make install' as a\nnormal user without sudo rights (or the configure option), certain binaries\nthat require additional privileges will not be installed properly (and\nautonomous NAT traversal, WLAN, DNS/GNS and the VPN will then not work).\n\nIf you run 'configure' and 'make install' as root, GNUnet's build system will\ninstall \"libnss_gns*\" libraries to \"/lib/\" regardless (!) of the\n$GNUNET_PREFIX you might have specified, as those libraries must be in\n\"/lib/\".  If you are packaging GNUnet for binary distribution, this may cause\nyour packaging script to miss those plugins, so you might need to do some\nadditional manual work to include those libraries in your binary package(s).\nSimilarly, if you want to use the GNUnet Name System and did NOT run\nGNUnet's 'make install' process with privileged rights, the libraries will be\ninstalled to \"$GNUNET_PREFIX\" and you will have to move them to \"/lib/\"\nmanually.\n\nConfiguration\n=============\n\nNote that additional, per-user configuration files can be created by\neach user.  However, this is usually not necessary as there are few\nper-user options that normal users would want to modify.  The defaults\nthat are shipped with the installation are usually just fine.\n\nThe gnunet-setup tool is particularly useful to generate the master\nconfiguration for the peer.  gnunet-setup can be used to configure and\ntest (!) the network settings, choose which applications should be run\nand configure databases.  Other options you might want to control\ninclude system limitations (such as disk space consumption, bandwidth,\netc).  The resulting configuration files are human-readable and can\ntheoretically be created or edited by hand.\n\ngnunet-setup is a separate download and requires somewhat recent\nversions of GTK+ and Glade. You can also create the configuration file\nby hand, but this is not recommended.  For more general information\nabout the GNU build process read the INSTALL file.\n\nGNUnet uses two types of configuration files, one that specifies the\nsystem-wide defaults (typically located in\n$GNUNET_PREFIX/../share/gnunet/config.d/) and a second one that overrides\ndefault values with user-specific preferences.  The user-specific\nconfiguration file should be located in \"~/.config/gnunet.conf\" or its\nlocation can be specified by giving the \"-c\" option to the respective\nGNUnet application.\n\nFor more information about the configuration (as well as usage) refer\nto the 'GNUnet User Handbook' chapter of the documentation, included\nin this software distribution.\n\n\nUsage\n=====\n\nFor detailed usage notes, instructions and examples, refer to the\nincluded 'GNUnet Handbook'.\n\nFirst, you must obtain an initial list of GNUnet hosts.  Knowing a\nsingle peer is sufficient since after that GNUnet propagates\ninformation about other peers.  Note that the default configuration\ncontains URLs from where GNUnet downloads an initial hostlist\nwhenever it is started.  If you want to create an alternative URL for\nothers to use, the file can be generated on any machine running\nGNUnet by periodically executing\n\n$ cat $SERVICEHOME/data/hosts/* \u003e the_file\n\nand offering 'the_file' via your web server.  Alternatively, you can\nrun the built-in web server by adding '-p' to the OPTIONS value\nin the \"hostlist\" section of gnunet.conf and opening the respective\nHTTPPORT to the public.\n\nIf the solution with the hostlist URL is not feasible for your\nsituation, you can also add hosts manually.  Simply copy the hostkeys\nto \"$SERVICEHOME/data/hosts/\" (where $SERVICEHOME is the directory\nspecified in the gnunet.conf configuration file).  You can also use\n\"gnunet-peerinfo -g\" to GET a URI for a peer and \"gnunet-peerinfo -p\nURI\" to add a URI from another peer.  Finally, GNUnet peers that use\nUDP or WLAN will discover each other automatically (if they are in the\nvicinity of each other) using broadcasts (IPv4/WLAN) or multicasts\n(IPv6).\n\nThe local node is started using \"gnunet-arm -s\".  We recommend to run\nGNUnet 24/7 if you want to maximize your anonymity, as this makes\npartitioning attacks harder.\n\nOnce your peer is running, you should then be able to access GNUnet\nusing the shell:\n\n$ gnunet-search KEYWORD\n\nThis will display a list of results to the console.  You can abort\nthe command using \"CTRL-C\".  Then use\n\n$ gnunet-download -o FILENAME GNUNET_URI\n\nto retrieve a file.  The GNUNET_URI is printed by gnunet-search\ntogether with a description.  To publish files on GNUnet, use the\n\"gnunet-publish\" command.\n\n\nThe GTK user interface is shipped separately.\nAfter installing gnunet-gtk, you can invoke the setup tool and\nthe file-sharing GUI with:\n\n$ gnunet-setup\n$ gnunet-fs-gtk\n\nFor further documentation, see our webpage or the 'GNUnet User Handbook',\nincluded in this software distribution.\n\n\nHacking GNUnet\n==============\n\nContributions are welcome. Please submit bugs you find to\nhttps://bugs.gnunet.org/ or our bugs mailinglist.\nPlease make sure to run the script \"contrib/scripts/gnunet-bugreport\"\nand include the output with your bug reports.  More about how to\nreport bugs can be found in the GNUnet FAQ on the webpage.  Submit\npatches via E-Mail to gnunet-developers@gnu.org, formatted with\n`git format-patch`.\n\nIn order to run the unit tests by hand (instead of using \"make check\"),\nyou need to set the environment variable \"GNUNET_PREFIX\" to the\ndirectory where GNUnet's libraries are installed.\nBefore running any testcases, you must complete the installation.\n\nQuick summary:\n\n$ meson setup -Dprefix=$SOMEWHERE $BUILDDIR\n$ meson compile -C $BUILDDIR\n$ make install -C $BUILDDIR\n$ export $GNUNET_PREFIX=$SOMEWHERE\n$ meson test -C $BUILDDIR\n\nIf any testcases fail to pass on your system, run\n\"contrib/scripts/gnunet-bugreport\" (in the repository) or \"gnunet-bugreport\"\nwhen you already have GNUnet installed and report its output together with\ninformation about the failing testcase(s) to the Mantis bugtracking\nsystem at https://bugs.gnunet.org/.\n\n\nRunning HTTP on port 80 and HTTPS on port 443\n=============================================\n\nIn order to hide GNUnet's HTTP/HTTPS traffic perfectly, you might\nconsider running GNUnet's HTTP/HTTPS transport on port 80/443.\nHowever, we do not recommend running GNUnet as root.  Instead, forward\nport 80 to say 1080 with this command (as root, in your startup\nscripts):\n\n# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 1080\n\nor for HTTPS\n\n# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 4433\n\nThen set in the HTTP section of gnunet.conf the \"ADVERTISED_PORT\" to\n\"80\" and \"PORT\" to 1080 and similarly in the HTTPS section the\n\"ADVERTISED_PORT\" to \"443\" and \"PORT\" to 4433.\n\nYou can do the same trick for the TCP and UDP transports if you want\nto map them to a privileged port (from the point of view of the\nnetwork).  However, we are not aware of this providing any advantages\nat this point.\n\nIf you are already running an HTTP or HTTPS server on port 80 (or 443),\nyou may be able to configure it as a \"ReverseProxy\".  Here, you tell\nGNUnet that the externally visible URI is some sub-page on your website,\nand GNUnet can then tunnel its traffic via your existing HTTP server.\nThis is particularly powerful if your existing server uses HTTPS, as\nit makes it harder for an adversary to distinguish normal traffic to\nyour server from GNUnet traffic.  Finally, even if you just use HTTP,\nyou might benefit (!) from ISP's traffic shaping as opposed to being\nthrottled by ISPs that dislike P2P.  Details for configuring the\nreverse proxy are documented on our website.\n\n\nFurther Reading\n===============\n\n* Documentation\n\n  An HTML version of the GNUnet manual is deployed at\n\n    https://docs.gnunet.org\n\n  which currently displays just GNUnet documentation. In the future\n  we will add more reading material.\n\n* Academia / papers\n\n  In almost 20 years various people in our community have written and\n  collected a good number of papers which have been implemented in\n  GNUnet or projects around GNUnet.\n  There are currently 2 ways to get them:\n\n  * Using git (NOTE: 1.1 GiB as of 2019-03-09):\n    git clone https://git.gnunet.org/bibliography.git\n  * Using the webbrowser:\n    https://bib.gnunet.org/\n\nNotes on Packaging\n==================\n\n* GNUnet installs binaries which should not be called by the user into\n  $PREFIX/lib/gnunet/libexec. This folder must not be confused with the\n  $PREFIX/libexec. GNUnet does not install anything into the libexec dir\n  to compliant with https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html\n\nStay tuned\n==========\n\n* https://gnunet.org/\n* https://bugs.gnunet.org\n* https://git.gnunet.org\n* http://www.gnu.org/software/gnunet/\n* http://mail.gnu.org/mailman/listinfo/gnunet-developers\n* http://mail.gnu.org/mailman/listinfo/help-gnunet\n* http://mail.gnu.org/mailman/listinfo/info-gnunet\n* http://mail.gnu.org/mailman/listinfo/gnunet-svn\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fthejackimonster%2Fgnunet","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fthejackimonster%2Fgnunet","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fthejackimonster%2Fgnunet/lists"}