README 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586
  1. Welcome to GNUnet
  2. ToC
  3. ===
  4. * ToC
  5. * What is GNUnet?
  6. * Dependencies
  7. o direct dependencies
  8. o test suite dependencies
  9. o optional dependencies
  10. o autotools
  11. * Notes on setuid
  12. * Scope of Operating System support
  13. * How to install
  14. o binary packages
  15. o Building GNUnet from source
  16. o Notes on compiling from Git
  17. * Configuration
  18. * Usage
  19. * Hacking GNUnet
  20. * Running HTTP on port 80 and HTTPS on port 443
  21. * Further Reading
  22. * Stay tuned
  23. What is GNUnet?
  24. ===============
  25. GNUnet is peer-to-peer framework providing a network abstractions and
  26. applications focusing on security and privacy. So far, we have
  27. created applications for anonymous file-sharing, decentralized naming
  28. and identity management, decentralized and confidential telephony and
  29. tunneling IP traffic over GNUnet. GNUnet is currently developed by a
  30. worldwide group of independent free software developers. GNUnet is a
  31. GNU package (http://www.gnu.org/).
  32. This is an ALPHA release. There are known and significant bugs as
  33. well as many missing features in this release.
  34. GNUnet is free software released under the GNU Affero General Public
  35. License (v3 or later). For details see the COPYING file in this
  36. directory. If you fork this software, you MUST adjust GNUNET_AGPL_URL
  37. in src/include/gnunet_util_lib.h to point to the source code of your
  38. fork!
  39. Additional documentation about GNUnet can be found at
  40. https://gnunet.org/ and in the 'doc/' folder.
  41. Online documentation is provided at
  42. 'https://docs.gnunet.org' and 'https://tutorial.gnunet.org'.
  43. Dependencies:
  44. =============
  45. The dependencies for building GNUnet will require around 0.74 GiB
  46. diskspace. GNUnet itself will require 8 - 9.2 MiB depending on
  47. configuration.
  48. These are the direct dependencies for running GNUnet:
  49. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  50. - Bash (for some scripts)
  51. - gettext
  52. - gnutls >= 3.2.12 (highly recommended a gnutls
  53. linked against libunbound)
  54. - curl (ideally built against gnutls) or gnurl:
  55. * libgnurl >= 7.35.0 (recommended, available from
  56. https://gnunet.org/en/gnurl.html)
  57. or
  58. * libcurl >= 7.35.0 (alternative to libgnurl)
  59. - libgcrypt >= 1.6
  60. - libunistring >= 0.9.2
  61. - libidn:
  62. * libidn2 (prefered)
  63. or
  64. * libidn >= 1.0
  65. - libmicrohttpd >= 0.9.63
  66. - libjansson
  67. - makeinfo >= 4.8
  68. - make[*3]
  69. - nss (certutil binary, for
  70. gnunet-gns-proxy-setup-ca)
  71. - openssl >= 1.0 (binary, used to generate
  72. X.509 certificate
  73. for gnunet-gns-proxy-setup-ca)
  74. - pkgconf or pkg-config
  75. - A Posix shell (for some scripts)
  76. - Texinfo >= 5.2 [*1]
  77. - libltdl >= 2.2 (part of GNU libtool)
  78. - 1 or more databases:
  79. * sqlite >= 3.8 (default database, required)
  80. and/or
  81. * mysql >= 5.1 (alternative to sqlite)
  82. and/or
  83. * postgres >= 9.5 (alternative to sqlite)
  84. - which (contrib/apparmor(?), gnunet-bugreport,
  85. and possibly more)
  86. - zlib
  87. - argon2 >= 20190702 (for proof-of-work calculations in
  88. revocation)
  89. - libsodium >= 1.0.11 (for elliptic curve cryptography)
  90. These are the dependencies for GNUnet's testsuite:
  91. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  92. - Bash (for some tests[*4])
  93. - A Posix Shell (for some tests)
  94. - python >= 3.4 (3.4 and higher technically supported,
  95. at least python 3.7 tested to work)
  96. - base tools
  97. - mostly:
  98. - bc,
  99. - curl,
  100. - sed,
  101. - awk,
  102. - which
  103. These are the optional dependencies:
  104. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  105. - awk (for linting tests)
  106. - Bash (for Docker and Vagrant)
  107. - bluez (for bluetooth support)
  108. - grof (for linting of man pages)
  109. - libextractor >= 0.6.1 (highly recommended[*5])
  110. - libopus >= 1.0.1 (for conversation tool)
  111. - libpulse >= 2.0 (for conversation tool)
  112. - libogg >= 1.3.0 (for conversation tool)
  113. - libnss (certtool binary (for convenient
  114. installation of GNS proxy))
  115. - libzbar >= 0.10 (for gnunet-qr)
  116. - libpbc >= 0.5.14 (for Attribute-Based Encryption and
  117. Identity Provider functionality)
  118. - libgabe (for Attribute-Based Encryption and
  119. Identity Provider functionality, from
  120. https://github.com/schanzen/libgabe)
  121. - mandoc (for linting of man pages, generation of
  122. html output of man pages (not part of
  123. the regular build))
  124. - miniupnpc
  125. - perl5 (for some utilities)
  126. - TeX Live >= 2012 (for gnunet-bcd[*])
  127. - texi2mdoc (for automatic mdoc generation [*2], not
  128. the texi2mdoc script distributed with
  129. autogen but the texi2mdoc C application)
  130. Recommended autotools for compiling the Git version are:
  131. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  132. - autoconf >= 2.59
  133. - automake >= 1.11.1
  134. - libtool >= 2.2
  135. [*] Mandatory for compiling the info output of the documentation,
  136. a limited subset ('texlive-tiny' in Guix) is enough.
  137. [*1] The default configuration is to build the info output of the
  138. documentation, and therefore require texinfo. You can pass
  139. '--disable-documentation' to the configure script to change this.
  140. [*2] If you still prefer to have documentation, you can pass
  141. '--enable-texi2mdoc-generation' to build the mdocml ("mandoc")
  142. documentation (experimental stages in gnunet).
  143. If this proves to be reliable, we will
  144. include the mdocml output in the release tarballs.
  145. Contrary to the name, texi2mdoc does not require Texinfo,
  146. It is a standalone ISO C utility.
  147. [*3] GNU make introduced the != operator in version 4.0.
  148. GNU make was released in october 2013, reasonable to
  149. be widespread by now. If this is not working out for
  150. you, open a bug so that we can get a more portable
  151. fix in.
  152. [*4] We are commited to portable tools and solutions
  153. where possible. New scripts should be Posix sh
  154. compatible, current and older scripts are
  155. in the process of being rewritten to comply
  156. with this requirement.
  157. [*5] While libextractor ("LE") is optional, it is recommended to
  158. build gnunet against it. If you install it later,
  159. you won't benefit from libextractor.
  160. If you are a distributor, we recommend to split
  161. LE into basis + plugins rather than making LE
  162. an option as an afterthought by the user.
  163. LE itself is very small, but its dependency chain
  164. on first, second, third etc level can be big.
  165. There is a small effect on privacy if your LE build
  166. differs from one which includes all
  167. plugins (plugins are build as shared objects):
  168. if users publish a directory with a mixture of file
  169. types (for example mpeg, jpeg, png, gif) the
  170. configuration of LE could leak which plugins are
  171. installed for which filetypes are not providing
  172. more details.
  173. However, this leak is just a minor concern.
  174. Notes on setuid
  175. ===============
  176. For a correct functionality depending on the host OS, you need
  177. to run the equivalent of these steps after installation.
  178. Replace $(DESTDIR)$(libexecdir) with the appropriate paths,
  179. for example /usr/local/lib/gnunet/libexec/. Note that this
  180. obviously must be run as priviledged user.
  181. chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn
  182. chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn
  183. chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-transport-wlan
  184. chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-transport-wlan
  185. chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-transport-bluetooth
  186. chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-transport-bluetooth
  187. chown root $(DESTDIR)$(libexecdir)/gnunet-helper-dns
  188. chgrp $(GNUNETDNS_GROUP) $(DESTDIR)$(libexecdir)/gnunet-helper-dns
  189. chmod 4750 $(DESTDIR)$(libexecdir)/gnunet-helper-dns
  190. chgrp $(GNUNETDNS_GROUP) $(DESTDIR)$(libexecdir)/gnunet-helper-dns
  191. chown gnunet:$(GNUNETDNS_GROUP) $(DESTDIR)$(libexecdir)/gnunet-helper-dns
  192. chmod 2750 $(DESTDIR)$(libexecdir)/gnunet-helper-dns
  193. chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-exit
  194. chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-exit
  195. chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-nat-server
  196. chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-nat-client
  197. chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-nat-server
  198. chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-nat-client
  199. Scope of Operating System support
  200. =================================
  201. We actively support GNUnet on a broad range of Free Software Operating
  202. Systems.
  203. For proprietary Operating Systems, like for example Microsoft Windows
  204. or Apple OS X, we accept patches if they don't break anything for
  205. other Operating Systems.
  206. If you are implementing support for a proprietary Operating System,
  207. you should be aware that progress in our codebase could break
  208. functionality on your OS and cause unpredicted behavior we can
  209. not test. However, we do not break support on Operating Systems
  210. with malicious intent.
  211. Regressions which do occur on these Operating Systems are 3rd
  212. class issues and we expect users and developers of these
  213. Operating Systems to send proposed patches to fix regressions.
  214. For more information about our stand on some of the motivating
  215. points here, read the 'Philosophy' Chapter of our handbook.
  216. How to install?
  217. ===============
  218. binary packages
  219. ~~~~~~~~~~~~~~~
  220. We recommend to use binary packages provided by the package manager integrated
  221. within your Operating System. GNUnet is reportedly available for at least:
  222. ALT Linux, Archlinux, Debian, Deepin, Devuan, GNU Guix, Hyperbola,
  223. Kali Linux, LEDE/OpenWRT, Manjaro, Nix, Parabola, Pardus, Parrot,
  224. PureOS, Raspbian, Rosa, Trisquel, and Ubuntu.
  225. If GNUnet is available for your Operating System and it is missing,
  226. send us feedback so that we can add it to this list. Furthermore, if
  227. you are interested in packaging GNUnet for your Operating System,
  228. get in touch with us at gnunet-developers@gnu.org if you require
  229. help with this job.
  230. If you were using an Operating System with the apt package manager,
  231. GNUnet could be installed as simple as:
  232. $ apt-get install gnunet
  233. Generic installation instructions are in the INSTALL file in this
  234. directory.
  235. Building GNUnet from source
  236. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  237. IMPORTANT: You can read further notes about compilation from source in
  238. the handbook under doc/handbook/, which includes notes about specific
  239. requirements for operating systems aswell. If you are a package
  240. mantainer for an Operating System we invite you to add your notes if
  241. you feel it is necessary and can not be covered in your Operating
  242. System's documentation.
  243. Two prominent examples which currently lack cross-compilation
  244. support in GNUnet (and native binaries) are MS Windows and Apple macOS.
  245. For macOS we recommend you to do the build process via Homebrew and a
  246. recent XCode installation. We don't recommend using GNUnet with any
  247. recent MS Windows system as it officially spies on its users (according
  248. to its T&C), defying some of the purposes of GNUnet.
  249. Note that some functions of GNUnet require "root" access. GNUnet will
  250. install (tiny) SUID binaries for those functions is you run "make
  251. install" as root. If you do not, GNUnet will still work, but some
  252. functionality will not be available (including certain forms of NAT
  253. traversal).
  254. GNUnet requires the GNU MP library (https://www.gnu.org/software/gmp/)
  255. and libgcrypt (https://www.gnupg.org/). You can specify the path to
  256. libgcrypt by passing "--with-gcrypt=PATH" to configure. You will also
  257. need either sqlite (http://www.sqlite.org/), MySQL
  258. (http://www.mysql.org/) or PostGres (http://www.postgres.org/).
  259. If you install from source, you need to install GNU libextractor first
  260. (download from https://www.gnu.org/software/libextractor/). We also
  261. recommend installing GNU libmicrohttpd (download from
  262. https://www.gnu.org/software/libmicrohttpd/). Furthermore we recommend
  263. libgnurl (from https://gnunet.org/en/gnurl.html).
  264. Then you can start the actual GNUnet compilation process with:
  265. $ export GNUNET_PREFIX=/usr/local/lib # or other directory of your choice
  266. # addgroup gnunetdns
  267. # adduser --system --home "/var/lib/gnunet" --group gnunet --shell /bin/sh
  268. # ./configure --prefix=$GNUNET_PREFIX/.. --with-extractor=$LE_PREFIX
  269. $ make
  270. And finally install GNUnet with:
  271. # make install
  272. Complete the process by either adjusting one of our example service files
  273. in 'contrib/services' or by running:
  274. # sudo -u gnunet gnunet-arm -s
  275. Note that you must read paragraph "Notes on setuid", which documents steps you
  276. have to follow after the installation, as a priviledged user. We require some
  277. binaries to be setuid. The most portable approach across all supported
  278. platforms and targets is to let this be handled manually.
  279. The installation will work if you do not run these steps as root, but some
  280. components may not be installed in the perfect place or with the right
  281. permissions and thus won't work.
  282. This will create the users and groups needed for running GNUnet
  283. securely and then compile and install GNUnet to $GNUNET_PREFIX/../bin/,
  284. $GNUNET_PREFIX/ and $GNUNET_PREFIX/../share/ and start the system
  285. with the default configuration. It is strongly recommended that you
  286. add a user "gnunet" to run "gnunet-arm". You can then still run the
  287. end-user applications as another user.
  288. If you create a system user "gnunet", it is recommended that you edit
  289. the configuration file slightly so that data can be stored in the
  290. system user home directory at "/var/lib/gnunet". Depending on what
  291. the $HOME-directory of your "gnunet" user is, you might need to set
  292. the SERVICEHOME option in section "[PATHS]" to "/var/lib/gnunet" to
  293. do this. Depending on your personal preferences, you may also want to
  294. use "/etc/gnunet.conf" for the location of the configuration file in
  295. this case (instead of ~gnunet/.config/gnunet.conf"). In this case,
  296. you need to start GNUnet using "gnunet-arm -s -c /etc/gnunet.conf" or
  297. set "XDG_CONFIG_HOME=/etc/".
  298. You can avoid running 'make install' as root if you have extensive sudo rights
  299. (can run "chmod +s" and "chown" via 'sudo'). If you run 'make install' as a
  300. normal user without sudo rights (or the configure option), certain binaries
  301. that require additional privileges will not be installed properly (and
  302. autonomous NAT traversal, WLAN, DNS/GNS and the VPN will then not work).
  303. If you run 'configure' and 'make install' as root, GNUnet's build system will
  304. install "libnss_gns*" libraries to "/lib/" regardless (!) of the
  305. $GNUNET_PREFIX you might have specified, as those libraries must be in
  306. "/lib/". If you are packaging GNUnet for binary distribution, this may cause
  307. your packaging script to miss those plugins, so you might need to do some
  308. additional manual work to include those libraries in your binary package(s).
  309. Similarly, if you want to use the GNUnet Name System and did NOT run
  310. GNUnet's 'make install' process with priviledged rights, the libraries will be
  311. installed to "$GNUNET_PREFIX" and you will have to move them to "/lib/"
  312. manually.
  313. Notes on compiling from Git
  314. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  315. Finally, if you are compiling the code from git, you have to
  316. run "sh ./bootstrap" before running "./configure". If you receive an error during
  317. the running of "sh ./bootstrap" that looks like "macro `AM_PATH_GTK'
  318. not found in library", you may need to run aclocal by hand with the -I
  319. option, pointing to your aclocal m4 macros, i.e.
  320. $ aclocal -I /usr/local/share/aclocal
  321. Configuration
  322. =============
  323. Note that additional, per-user configuration files can be created by
  324. each user. However, this is usually not necessary as there are few
  325. per-user options that normal users would want to modify. The defaults
  326. that are shipped with the installation are usually just fine.
  327. The gnunet-setup tool is particularly useful to generate the master
  328. configuration for the peer. gnunet-setup can be used to configure and
  329. test (!) the network settings, choose which applications should be run
  330. and configure databases. Other options you might want to control
  331. include system limitations (such as disk space consumption, bandwidth,
  332. etc). The resulting configuration files are human-readable and can
  333. theoretically be created or edited by hand.
  334. gnunet-setup is a separate download and requires somewhat recent
  335. versions of GTK+ and Glade. You can also create the configuration file
  336. by hand, but this is not recommended. For more general information
  337. about the GNU build process read the INSTALL file.
  338. GNUnet uses two types of configuration files, one that specifies the
  339. system-wide defaults (typically located in
  340. $GNUNET_PREFIX/../share/gnunet/config.d/) and a second one that overrides
  341. default values with user-specific preferences. The user-specific
  342. configuration file should be located in "~/.config/gnunet.conf" or its
  343. location can be specified by giving the "-c" option to the respective
  344. GNUnet application.
  345. For more information about the configuration (as well as usage) refer
  346. to the 'GNUnet User Handbook' chapter of the documentation, included
  347. in this software distribution.
  348. Usage
  349. =====
  350. For detailed usage notes, instructions and examples, refer to the
  351. included 'GNUnet Handbook'.
  352. First, you must obtain an initial list of GNUnet hosts. Knowing a
  353. single peer is sufficient since after that GNUnet propagates
  354. information about other peers. Note that the default configuration
  355. contains URLs from where GNUnet downloads an initial hostlist
  356. whenever it is started. If you want to create an alternative URL for
  357. others to use, the file can be generated on any machine running
  358. GNUnet by periodically executing
  359. $ cat $SERVICEHOME/data/hosts/* > the_file
  360. and offering 'the_file' via your web server. Alternatively, you can
  361. run the build-in web server by adding '-p' to the OPTIONS value
  362. in the "hostlist" section of gnunet.conf and opening the respective
  363. HTTPPORT to the public.
  364. If the solution with the hostlist URL is not feasible for your
  365. situation, you can also add hosts manually. Simply copy the hostkeys
  366. to "$SERVICEHOME/data/hosts/" (where $SERVICEHOME is the directory
  367. specified in the gnunet.conf configuration file). You can also use
  368. "gnunet-peerinfo -g" to GET a URI for a peer and "gnunet-peerinfo -p
  369. URI" to add a URI from another peer. Finally, GNUnet peers that use
  370. UDP or WLAN will discover each other automatically (if they are in the
  371. vicinity of each other) using broadcasts (IPv4/WLAN) or multicasts
  372. (IPv6).
  373. The local node is started using "gnunet-arm -s". We recommend to run
  374. GNUnet 24/7 if you want to maximize your anonymity, as this makes
  375. partitioning attacks harder.
  376. Once your peer is running, you should then be able to access GNUnet
  377. using the shell:
  378. $ gnunet-search KEYWORD
  379. This will display a list of results to the console. You can abort
  380. the command using "CTRL-C". Then use
  381. $ gnunet-download -o FILENAME GNUNET_URI
  382. to retrieve a file. The GNUNET_URI is printed by gnunet-search
  383. together with a description. To publish files on GNUnet, use the
  384. "gnunet-publish" command.
  385. The GTK user interface is shipped separately.
  386. After installing gnunet-gtk, you can invoke the setup tool and
  387. the file-sharing GUI with:
  388. $ gnunet-setup
  389. $ gnunet-fs-gtk
  390. For further documentation, see our webpage or the 'GNUnet User Handbook',
  391. included in this software distribution.
  392. Hacking GNUnet
  393. ==============
  394. Contributions are welcome. Please submit bugs you find to
  395. https://bugs.gnunet.org/ or our bugs mailinglist.
  396. Please make sure to run the script "contrib/scripts/gnunet-bugreport"
  397. and include the output with your bug reports. More about how to
  398. report bugs can be found in the GNUnet FAQ on the webpage. Submit
  399. patches via E-Mail to gnunet-developers@gnu.org, formated with
  400. `git format-patch`.
  401. In order to run the unit tests by hand (instead of using "make check"),
  402. you need to set the environment variable "GNUNET_PREFIX" to the
  403. directory where GNUnet's libraries are installed.
  404. Before running any testcases, you must complete the installation.
  405. Quick summary:
  406. $ ./configure --prefix=$SOMEWHERE
  407. $ make
  408. $ make install
  409. $ export $GNUNET_PREFIX=$SOMEWHERE
  410. $ make check
  411. Some of the testcases require python >= 3.4, and the python module
  412. "pexpect" to be installed.
  413. If any testcases fail to pass on your system, run
  414. "contrib/scripts/gnunet-bugreport" (in the repository) or "gnunet-bugreport"
  415. when you already have GNUnet installed and report its output together with
  416. information about the failing testcase(s) to the Mantis bugtracking
  417. system at https://bugs.gnunet.org/.
  418. Running HTTP on port 80 and HTTPS on port 443
  419. =============================================
  420. In order to hide GNUnet's HTTP/HTTPS traffic perfectly, you might
  421. consider running GNUnet's HTTP/HTTPS transport on port 80/443.
  422. However, we do not recommend running GNUnet as root. Instead, forward
  423. port 80 to say 1080 with this command (as root, in your startup
  424. scripts):
  425. # iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 1080
  426. or for HTTPS
  427. # iptables -t nat -A PREROUTING -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 4433
  428. Then set in the HTTP section of gnunet.conf the "ADVERTISED_PORT" to
  429. "80" and "PORT" to 1080 and similarly in the HTTPS section the
  430. "ADVERTISED_PORT" to "443" and "PORT" to 4433.
  431. You can do the same trick for the TCP and UDP transports if you want
  432. to map them to a priviledged port (from the point of view of the
  433. network). However, we are not aware of this providing any advantages
  434. at this point.
  435. If you are already running an HTTP or HTTPS server on port 80 (or 443),
  436. you may be able to configure it as a "ReverseProxy". Here, you tell
  437. GNUnet that the externally visible URI is some sub-page on your website,
  438. and GNUnet can then tunnel its traffic via your existing HTTP server.
  439. This is particularly powerful if your existing server uses HTTPS, as
  440. it makes it harder for an adversary to distinguish normal traffic to
  441. your server from GNUnet traffic. Finally, even if you just use HTTP,
  442. you might benefit (!) from ISP's traffic shaping as opposed to being
  443. throttled by ISPs that dislike P2P. Details for configuring the
  444. reverse proxy are documented on our website.
  445. Further Reading
  446. ===============
  447. * Documentation
  448. An HTML version of the GNUnet manual is deployed at
  449. https://docs.gnunet.org
  450. which currently displays just GNUnet documentation. In the future
  451. we will add more reading material.
  452. * Academia / papers
  453. In almost 20 years various people in our community have written and
  454. collected a good number of papers which have been implemented in
  455. GNUnet or projects around GNUnet.
  456. There are currently 2 ways to get them:
  457. * Using git (NOTE: 1.1 GiB as of 2019-03-09):
  458. git clone https://git.gnunet.org/bibliography.git
  459. * Using the webbrowser:
  460. https://bib.gnunet.org/
  461. Stay tuned
  462. ==========
  463. * https://gnunet.org/
  464. * https://bugs.gnunet.org
  465. * https://git.gnunet.org
  466. * http://www.gnu.org/software/gnunet/
  467. * http://mail.gnu.org/mailman/listinfo/gnunet-developers
  468. * http://mail.gnu.org/mailman/listinfo/help-gnunet
  469. * http://mail.gnu.org/mailman/listinfo/info-gnunet
  470. * http://mail.gnu.org/mailman/listinfo/gnunet-svn