Merge branch 'master' into stable

15 files changed, 552 insertions, 513 deletions

diff --git a/Dockerfile b/Dockerfile
index 7b17dc87..09db58f0 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -14,7 +14,6 @@ RUN apt-get update && \
       python3-babel \
       python3-jinja2 \
       git \
-      sassc && \
     apt-get clean all && \
     apt-get -y autoremove && \
     rm -rf \
diff --git a/GNUmakefile b/GNUmakefile
deleted file mode 100644
index ffe9c281..00000000
--- a/GNUmakefile
+++ /dev/null
@@ -1,99 +0,0 @@
-#
-# Copyright (C) 2017, 2018, 2019 GNUnet e.V.
-#
-# Copying and distribution of this file, with or without modification,
-# are permitted in any medium without royalty provided the copyright
-# notice and this notice are preserved.  This file is offered as-is,
-# without any warranty.
-#
-# ----
-
-# All: build HTML pages in all languages and compile the
-# TypeScript logic in web-common.
-
-# Hardly anyone seems to read README files anymore, so keep this note here:
-# Don't remove the variables for python etc. They exist
-# because one system sticks with PEPs, and others opt
-# for installing every version side-by-side,
-# Same goes for babel.
-
-include config.mk
-
-all: locale template
-        ($(cp) rendered/static/robots.txt rendered/robots.txt)
-        ($(cp) rendered/static/stage.robots.txt rendered/stage.robots.txt)
-        ($(cp) rendered/static/robots.txt rendered/dist/robots.txt)
-        (for lang in en de es fr it ; do \
-                $(cp) rendered/static/robots.txt rendered/$$lang/robots.txt ; \
-        done)
-        ($(python) inc/make_sitemap.py -i rendered)
-        ($(cp) sitemap.xml rendered/sitemap.xml)
-        ($(cp) sitemap.xml rendered/en/sitemap.xml)
-        ($(cp) static/moved.html rendered/frontpage.html)
-        (cd rendered; $(ln) -fs frontpage.html frontpage)
-        ($(cp) static/moved_gsoc.html rendered/gsoc.html)
-        (cd rendered; $(ln) -fs gsoc.html gsoc)
-        ($(cp) static/moved_gns.html rendered/gns.html)
-        (cd rendered; $(ln) -fs gns.html gns)
-        ($(mkdir) -p rendered/node ; $(cp) static/moved_about.html rendered/node/about.html)
-        (cd rendered/node ; $(ln) -fs about.html 397)
-        ($(cp) static/moved_about.html rendered/about.html)
-        (cd rendered ; $(ln) -fs about.html philosophy)
-        (cd rendered; \
-                for lang in en de es fr it; do \
-                        $(cp) $$lang/rss.xml $$lang/news/rss.xml; \
-                done)
-
-# Extract translateable strings from jinja2 templates.
-# Because of the local i18nfix extractor module we need
-# to set the pythonpath before invoking pybabel.
-locale/messages.pot: common/*.j2.inc template/*.j2
-        $(env) PYTHONPATH=. $(pybabel) -q extract -F locale/babel.map -o locale/messages.pot .
-
-# Update translation (.po) files with new strings.
-locale-update: locale/messages.pot
-        (for lang in en de es fr it; do \
-                $(msgmerge) -q -U -m --previous locale/$$lang/LC_MESSAGES/messages.po locale/messages.pot ; \
-        done)
-        if $(grep) -nA1 '#-#-#-#-#' locale/*/LC_MESSAGES/messages.po; then echo -e "\nERROR: Conflicts encountered in PO files.\n"; exit 1; fi
-
-# Compile translation files for use.
-locale-compile:
-        (for lang in en de fr it es; do \
-                $(pybabel) -q compile -d locale -l $$lang --use-fuzzy ; \
-        done)
-
-# Process everything related to gettext translations.
-locale: locale-update locale-compile
-
-# Run the jinja2 templating engine to expand templates to HTML
-# incorporating translations.
-template: locale-compile
-        $(python) ./make_site.py
-
-it: template
-
-current_dir = $(shell pwd)
-
-run: all
-        $(browser) http://0.0.0.0:8000/rendered/en &
-        $(python) -m http.server
-
-
-# docker-all: Build using a docker image which contains all the needed
-# packages.
-
-docker: docker-all
-
-docker-all:
-        $(docker) build -t gnunet-www-builder .
-        # Importing via the shell like this is hacky,
-        # but after trying lots of other ways, this works most reliably...
-        $(python) -c 'import i18nfix'
-        $(docker) run --rm -v $$(pwd):/tmp/ --user $$(id -u):$$(id -g) gnunet-www-builder
-
-clean:
-        $(rm) -rf __pycache__
-        $(rm) -rf en/ de/ fr/ it/ es/ ru/
-        $(rm) -rf rendered/
-        $(rm) -rf *.pyc *~ \.*~ \#*\#
diff --git a/Makefile b/Makefile
index 4cb7a99b..e47f3faa 100644
--- a/Makefile
+++ b/Makefile
@@ -1,65 +1,67 @@
-# Makefile for NetBSD make (portable version: "bmake"),
-# GNU make will find 'GNUmakefile' first and use that file instead.
-# This file is in the public domain.
 #
-# I keep and maintain this file for personal use, it is faster than
-# the gmake approach.
-
-.include "config.mk"
-
-DESTDIR=$(prefix)
-
-_LOCALELIST= en de fr it es
-_DIRLIST= dist static
+# Copyright (C) 2017, 2018, 2019 GNUnet e.V.
+#
+# Copying and distribution of this file, with or without modification,
+# are permitted in any medium without royalty provided the copyright
+# notice and this notice are preserved.  This file is offered as-is,
+# without any warranty.
+#
+# ----
 
-.PHONY: all run locale-compile locale install clean
+# All: build HTML pages in all languages and compile the
+# TypeScript logic in web-common.
 
-.OBJDIR=rendered
+# Hardly anyone seems to read README files anymore, so keep this note here:
+# Don't remove the variables for python etc. They exist
+# because one system sticks with PEPs, and others opt
+# for installing every version side-by-side,
+# Same goes for babel.
 
-# Work this into an mk file
+include config.mk
 
-# All: build HTML pages in all languages and compile the
-# TypeScript logic in web-common.
 all: locale template
-.for _lang in ${_LOCALELIST}
-        ($(cp) rendered/static/robots.txt rendered/${_lang})
-        ($(cp) rendered/static/stage.robots.txt rendered/${_lang})
-.endfor
+        ($(cp) rendered/static/robots.txt rendered/robots.txt)
+        ($(cp) rendered/static/stage.robots.txt rendered/stage.robots.txt)
         ($(cp) rendered/static/robots.txt rendered/dist/robots.txt)
-        # ($(cp) favicon.ico rendered/)
-        # $(sh) make_sitemap.sh
+        (for lang in en de es fr it ; do \
+                $(cp) rendered/static/robots.txt rendered/$$lang/robots.txt ; \
+        done)
+        ($(python) inc/make_sitemap.py -i rendered)
         ($(cp) sitemap.xml rendered/sitemap.xml)
-        ($(cp) rendered/sitemap.xml rendered/en/sitemap.xml)
+        ($(cp) sitemap.xml rendered/en/sitemap.xml)
         ($(cp) static/moved.html rendered/frontpage.html)
         (cd rendered; $(ln) -fs frontpage.html frontpage)
         ($(cp) static/moved_gsoc.html rendered/gsoc.html)
         (cd rendered; $(ln) -fs gsoc.html gsoc)
         ($(cp) static/moved_gns.html rendered/gns.html)
         (cd rendered; $(ln) -fs gns.html gns)
-        ($(mkdir) -p rendered/node; $(cp) static/moved_about.html rendered/node/about.html)
+        ($(mkdir) -p rendered/node ; $(cp) static/moved_about.html rendered/node/about.html)
         (cd rendered/node ; $(ln) -fs about.html 397)
         ($(cp) static/moved_about.html rendered/about.html)
         (cd rendered ; $(ln) -fs about.html philosophy)
+        (cd rendered; \
+                for lang in en de es fr it; do \
+                        $(cp) $$lang/rss.xml $$lang/news/rss.xml; \
+                done)
 
 # Extract translateable strings from jinja2 templates.
-locale/messages.pot: template/*.j2 common/*.j2 common/*.j2.inc
+# Because of the local i18nfix extractor module we need
+# to set the pythonpath before invoking pybabel.
+locale/messages.pot: common/*.j2.inc template/*.j2
         $(env) PYTHONPATH="." $(pybabel) -q extract -F locale/babel.map -o locale/messages.pot .
 
 # Update translation (.po) files with new strings.
 locale-update: locale/messages.pot
-.for _lang in ${_LOCALELIST}
-        $(msgmerge) -q -U -m --previous locale/${_lang}/LC_MESSAGES/messages.po locale/messages.pot
-.endfor
-        if $(grep) -nA1 '#-#-#-#-#' locale/*/LC_MESSAGES/messages.po; then \
-                $(echo) -e "\nERROR: Conflicts encountered in PO files.\n"; \
-                exit 1; \
-        fi
+        (for lang in en de es fr it; do \
+                $(msgmerge) -q -U -m --previous locale/$$lang/LC_MESSAGES/messages.po locale/messages.pot ; \
+        done)
+        if $(grep) -nA1 '#-#-#-#-#' locale/*/LC_MESSAGES/messages.po; then echo -e "\nERROR: Conflicts encountered in PO files.\n"; exit 1; fi
 
 # Compile translation files for use.
 locale-compile:
-.for _lang in ${_LOCALELIST}
-        $(pybabel) -q compile -d locale -l ${_lang} --use-fuzzy
-.endfor
+        (for lang in en de fr it es; do \
+                $(pybabel) -q compile -d locale -l $$lang --use-fuzzy ; \
+        done)
 
 # Process everything related to gettext translations.
 locale: locale-update locale-compile
@@ -67,38 +69,31 @@ locale: locale-update locale-compile
 # Run the jinja2 templating engine to expand templates to HTML
 # incorporating translations.
 template: locale-compile
-        $(python) ./make_site.py -vvvv
+        $(python) ./make_site.py
 
-run:
-.if defined(browser) && !empty(DESTDIR) && !empty(python)
-        $(browser) http://0.0.0.0:8000/rendered/en/ &
-        $(python) -m http.server
-.endif
+it: template
 
-install:
-        $(mkdir) -p $(prefix)/share/gnunet-www
-        $(cp) -R rendered/* $(prefix)/share/gnunet-www
+current_dir = $(shell pwd)
 
-uninstall:
-        $(rm) -rf $(prefix)/share/gnunet-www
+run: all
+        $(browser) http://0.0.0.0:8000/rendered/en &
+        $(python) -m http.server
 
-submodules/init:
-        $(git) submodule update --init --recursive
 
-submodules/update:
-        $(git) submodule update --recursive --remote
+# docker-all: Build using a docker image which contains all the needed
+# packages.
 
 docker: docker-all
 
 docker-all:
-.if defined(docker)
         $(docker) build -t gnunet-www-builder .
         # Importing via the shell like this is hacky,
         # but after trying lots of other ways, this works most reliably...
         $(python) -c 'import i18nfix'
         $(docker) run --rm -v $$(pwd):/tmp/ --user $$(id -u):$$(id -g) gnunet-www-builder
-.endif
-
-CLEANFILES+=    *.pyc *~ \.*~ *.core
 
-.include <bsd.prog.mk>
+clean:
+        $(rm) -rf __pycache__
+        $(rm) -rf en/ de/ fr/ it/ es/ ru/
+        $(rm) -rf rendered/
+        $(rm) -rf *.pyc *~ \.*~ \#*\#
diff --git a/README b/README
index 9857ac6a..6fb8ac15 100644
--- a/README
+++ b/README
@@ -67,6 +67,8 @@ Writing News
 
 Writing news posts for gnunet.org involves a couple of steps.
 If you intend to write a new post, read this carefully.
+Note that this section will be worked into a separate onboarding
+section in the manual.
 
 * Every news post is wrapped in an <article> element, outside
   of the news post itself.
@@ -77,18 +79,17 @@ If you intend to write a new post, read this carefully.
   assigned as the title for the rss feed item for this post.
 
 * Every news post must get added as a dict to the newspost list
-  in template.py. If you are not sure what those words mean, search
-  "newsposts" in template.py. There you will find a structure where
-  you have to add a new member including the "," at the end.
+  in www.yml. If you are not sure what those words mean, search
+  "newsposts" in www.yml.
+  There you will find a structure where you have to add a new
+  member.
   New posts get added to the top of the list, not at the bottom
   (this list is also responsible for the 5 newest entries on the
   frontpage).
 
-  {
-        'page': 'name-of-page.html',
-        'date': '2019-10-31',
-        'title': 'My new post'
-  },
+  - page: 2019-0.12.0.html
+    date: 2019-12-15
+    title: GNUnet 0.12.0
 
   * page must be the name of the file without the leading news/
   * date must be a valid date in exactly this format.
@@ -133,8 +134,8 @@ Additional Notes
 Please use HTML codes, not international signs as found on your keyboard.
 
 This website has been tested with:
-* python 3.6.5 and jinja2 2.9.6.
 * python 3.7.1, Babel 2.6.0, py-jinja2 2.10 (pkgsrc, NetBSD 8.0)
+
 Since python development in collaborative environments with
 a whole range of possibilities in what your environment looks
 like, please state problems on the mailinglist instead of just
diff --git a/bootstrap b/bootstrap
index 7630c337..dcc5ae3a 100755
--- a/bootstrap
+++ b/bootstrap
@@ -11,7 +11,7 @@ if ! git --version >/dev/null; then
 fi
 
 git submodule update --init
-git submodule update --recursive --remote
+git submodule update --recursive
 git submodule sync
 cp build-system/taler-build-scripts/configure ./configure || true
 cp build-system/taler-build-scripts/conf/.style.yapf .style.yapf || true
diff --git a/build-system/taler-build-scripts b/build-system/taler-build-scripts
-Subproject 1915a74bbb4cd2ae9bc541a382dfebc37064a2f
+Subproject d725a0cd1b4aa3ff54452a702b8c19db3f3c339
diff --git a/inc b/inc
-Subproject 46295bc38988c16a9a6c8c0cf8930abd20193a0
+Subproject bdef602fcbd13d59aef971307b3730247a8b9c5
diff --git a/locale/de/LC_MESSAGES/messages.po b/locale/de/LC_MESSAGES/messages.po
index bef9c6d6..06477135 100644
--- a/locale/de/LC_MESSAGES/messages.po
+++ b/locale/de/LC_MESSAGES/messages.po
@@ -11,10 +11,10 @@ msgstr ""
 "PO-Revision-Date: 2018-02-24 17:42\n"
 "Last-Translator: Torsten Grothoff <torsten@grothoff.org>\n"
 "Language-Team: German <LL@li.org>\n"
+"Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Language: de\n"
 "Generated-By: Babel 2.4.0\n"
 
 #~ msgid "GNUnet"
diff --git a/locale/es/LC_MESSAGES/messages.po b/locale/es/LC_MESSAGES/messages.po
index 13e165e9..a19f6a50 100644
--- a/locale/es/LC_MESSAGES/messages.po
+++ b/locale/es/LC_MESSAGES/messages.po
@@ -12,10 +12,10 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: es\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Language: es\n"
 "Generated-By: Babel 2.4.0\n"
 
 #~ msgid "Contact"
diff --git a/locale/fr/LC_MESSAGES/messages.po b/locale/fr/LC_MESSAGES/messages.po
index 2a89f105..1d1ec761 100644
--- a/locale/fr/LC_MESSAGES/messages.po
+++ b/locale/fr/LC_MESSAGES/messages.po
@@ -12,8 +12,8 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: fr\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Language: fr\n"
 "Generated-By: Babel 2.4.0\n"
diff --git a/locale/it/LC_MESSAGES/messages.po b/locale/it/LC_MESSAGES/messages.po
index 433198f8..ca9bf922 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/LC_MESSAGES/messages.po
@@ -12,10 +12,10 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: it\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Language: it\n"
 "Generated-By: Babel 2.4.0\n"
 
 #~ msgid "_project_title"
diff --git a/news/2019-0.12.0.html.j2 b/news/2019-0.12.0.html.j2
new file mode 100644
index 00000000..6cf68160
--- /dev/null
+++ b/news/2019-0.12.0.html.j2
@@ -0,0 +1,85 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.11.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.11.x GNUnet network, and interactions between old and new peers
+  will result in signature verification failures.  0.11.x peers will <b>NOT</b>
+  be able to communicate with Git master or 0.12.x peers.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> 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.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.12.0 (since 0.11.8)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Changed key derivation protocols to adhere with <a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">LSD001</a>. <a href="https://bugs.gnunet.org/view.php?id=5921">#5921</a></li>
+      <li>Names are not expected to be UTF-8 (as opposed to IDNA). <a href="https://bugs.gnunet.org/view.php?id=5922">#5922</a></li>
+      <li>NSS plugin now properly handles non-standard IDNA names. <a href="https://bugs.gnunet.org/view.php?id=5927">#5927</a></li>
+      <li>NSS plugin will refuse to process requests from root (as GNUnet code should never run as root). <a href="https://bugs.gnunet.org/view.php?id=5927">#5907</a></li>
+      <li>Fixed BOX service/protocol label parsing (for TLSA et al)</li>
+    </ul>
+  </li>
+  <li><tt>GNS/NSE</tt>: Zone revocation proof of work algorithm changed to be less susceptible to specialized ASIC hardware.
+  <a href="https://bugs.gnunet.org/view.php?id=3795">#3795</a></li>
+  <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Improved and documented RSA binary format. <a href="https://bugs.gnunet.org/view.php?id=5968">#5968</a></li>
+      <li>Removed redundant hashing in EdDSA signatures. <a href="https://bugs.gnunet.org/view.php?id=5398">#5398</a></li>
+      <li>The <tt>gnunet-logread</tt> script for log auditing (requires perl) can now be installed.</li>
+      <li>Now using <a href="https://tweetnacl.cr.yp.to/">TweetNaCl</a> for ECDH implementation.</li>
+    </ul>
+  </li>
+  <li><tt>Buildsystem</tt>: A significant number of build system issued have been fixed and improvements implemented, including:
+    <ul>
+      <li>GLPK dependency dropped.</li>
+      <li>Fixed guix package definition.</li>
+    </ul>
+  </li>
+  <li><tt>Documentation</tt>: Improvements to the handbook and documentation.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Florian Dold, xrs, Naomi Phillips and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/gnurl.html.j2 b/template/gnurl.html.j2
index 7d5a7365..7393bb6f 100644
--- a/template/gnurl.html.j2
+++ b/template/gnurl.html.j2
@@ -1,7 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
   <article class="container">
-
     <header>
       <h1>gnurl (libgnurl)</h1>
       <a href="#motivation">motivation</a>
@@ -15,353 +14,395 @@
       <a href="#maintainer">maintainer</a>
     </header>
 
-    <div class="container">
-      <p>
-        {% trans %}
-          libgnurl is a micro fork of libcurl. The goal of libgnurl
-          is to support only HTTP and HTTPS (and only HTTP 1.x) with
-          a single crypto backend (GnuTLS) to ensure a small footprint
-          and uniform experience for developers regardless of how
-          libcurl was compiled.<br>
-          Our main usecase is for GNUnet, but it might be usable for
-          others, hence we're releasing the code
-          to the general public.<br>
-          libgnurl is released under the same
-          license as libcurl. Please read the README for instructions, as you
-          must supply the correct options to configure to get a proper build of
-          libgnurl.
-        {% endtrans %}
-      </p>
-      <h3>{{ _("About gnurl") }}</h3>
-      <p>
-        {% trans %}
-          Large parts of the following 6 paragraphs are old and need
-          to be rewritten.
-        {% endtrans %}
-      </p>
-      <a name="motivation"></a>
-      <h4>{{_("Motivation") }}</h4>
-      <p>
-        {% trans %}
-          cURL supports many crypto backends. GNUnet requires the use of
-          GnuTLS, but other variants are used by some distributions. Supporting
-          other crypto backends would again expose us to a wider array of
-          security issues, may create licensing issues and most importantly
-          introduce new bugs as some crypto backends are known to introduce
-          subtle runtime issues. While it is possible to have two versions of
-          libcurl installed on the same system, this is error-prone, especially
-          as if we are linked against the wrong version, the bugs that arise
-          might be rather subtle.
-        {% endtrans %}
-      </p>
-      <p>
-        {% trans %}
-          For GNUnet, we also need a particularly modern version of
-          GnuTLS. Thus, it would anyway be necessary to recompile cURL for
-          GNUnet. But what happens if one links cURL against this version of
-          GnuTLS? Well, first one would install GnuTLS by hand in the
-          system. Then, we build cURL. cURL will build against it just fine, but
-          the linker will eventually complain bitterly. The reason is that cURL
-          also links against a bunch of other system libraries (gssapi, ldap,
-          ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above),
-          which --- as they are part of the distribution --- were linked against
-          an older version of GnuTLS. As a result, the same binary would be
-          linked against two different versions of GnuTLS. That is typically a
-          recipe for disaster. Thus, in order to avoid updating a dozen system
-          libraries (and having two versions of those installed), it is
-          necessary to disable all of those cURL features that GNUnet does not
-          use, and there are many of those. For GNUnet, the more obscure
-          protocols supported by cURL are close to dead code --- mostly
-          harmless, but not useful. However, as some application may use one of
-          those features, distributions are typically forced to enable all of
-          those features, and thus including security issues that might arise
-          from that code.
-        {% endtrans %}
-      </p>
-      <p>
-        {% trans %}
-          So to use a modern version of GnuTLS, a sane approach is to disable
-          all of the "optional" features of cURL that drag in system libraries
-          that link against the older GnuTLS. That works, except that one should
-          then NEVER install that version of libcurl in say /usr or /usr/local,
-          as that may break other parts of the system that might depend on these
-          features that we just disabled. Libtool versioning doesn't help here,
-          as it is not intended to deal with libraries that have optional
-          features. Naturally, installing cURL somewhere else is also
-          problematic, as we now need to be really careful that the linker will
-          link GNUnet against the right version. Note that none of this can
-          really be trivially fixed by the cURL developers.
-        {% endtrans %}
-      </p>
-      <a name="rename"></a>
-      <h4>{{_("Rename to fix") }}</h4>
-      <p>
-        {% trans %}
-          How does forking fix it? Easy. First, we can get rid of all of the
-          compatibility issues --- if you use libgnurl, you state that you don't
-          need anything but HTTP/HTTPS. Those applications that need more,
-          should stick with the original cURL. Those that do not, can choose to
-          move to something simpler. As the library gets a new name, we do not
-          have to worry about tons of packages breaking as soon as one rebuilds
-          it. So renaming itself and saying that "libgnurl = libcurl with only
-          HTTP/HTTPS support and GnuTLS" fixes 99%% of the problems that darkened
-          my mood. Note that this pretty much CANNOT be done without a fork, as
-          renaming is an essential part of the fix. Now, there might be creative
-          solutions to achieve the same thing within the standard cURL build
-          system, but I'm not happy to wait for a decade for Daniel to review
-          the patches. The changes libgnurl makes to curl are miniscule and can
-          easily be applied again and again whenever libcurl makes a new
-          release.
-        {% endtrans %}
-      </p>
-      <a name="using"></a>
-      <h4>{{_("Using libgnurl") }}</h4>
-      <p>
-        {% trans %}
-          Projects that use cURL only for HTTP/HTTPS and that would work
-          with GnuTLS should be able to switch to libgnurl by changing
-          "-lcurl" to "-lgnurl". That's it. No changes to the source code
-          should be required,
-          as libgnurl strives for bug-for-bug compatibility with the
-          HTTP/HTTPS/GnuTLS subset of cURL.
-          We might add new features relating to this core subset if they
-          are proposed, but so far we have kept our changes minimal and
-          no additions to the original curl source have been written.
-        {% endtrans %}
-      </p>
-      <a name="gotchas"></a>
-      <h4>{{_("Gotchas") }}</h4>
-      <p>
-        {% trans %}
-          libgnurl and gnurl are not intended to be used as a replacement
-          for curl for users. Since no conflicts in filenames should occur
-          you are not expected to remove curl to make use of gnurl and
-          viceversa.
-        {% endtrans %}
-      </p>
-    </div>
-
-    <div class="row container">
-      <div class="col-md">
-        <a name="source"></a>
-        <h3>{{ _("Source Code") }}</h3>
-        <p>
-          {% trans %}
-            You can get the gnurl git repository using:
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            <code>git clone https://git.taler.net/gnurl.git</code>
-          </li>
-          <li>
-            <code>git clone git://git.taler.net/gnurl.git</code>
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            The versions are checked in as (signed) git tags.
-          {% endtrans %}
-        </p>
+    <section class="container">
+      <div class="row">
+        <div class="col-md">
+          <p>
+            {% trans %}
+              libgnurl is a micro fork of libcurl. The goal of
+              libgnurl is to support only HTTP and HTTPS (and only
+              HTTP 1.x) with a single crypto backend (GnuTLS) to
+              ensure a small footprint and uniform experience for
+              developers regardless of how libcurl was compiled.
+            {% endtrans %}
+          </p>
+          <p>
+            {% trans %}
+              Our main usecase is for GNUnet, but it might be usable
+              for others, hence we&#39;re releasing the code to the
+              general public.
+            {% endtrans %}
+          </p>
+          <p>
+            {% trans %}
+              libgnurl is released under the same license as
+              libcurl. Please read the README for instructions, as you
+              must supply the correct options to configure to get a
+              proper build of libgnurl.
+            {% endtrans %}
+          </p>
+        </div>
       </div>
-      <div class="col-md">
-        <a name="downloads"></a>
-        <h3>{{ _("Downloads") }}</h3>
-        <p>
-          {% trans %}
-            Releases are published on <a href="https://ftpmirror.gnu.org/gnu/gnunet/">ftpmirror.gnu.org/gnu/gnunet</a>.
-            gnurl is available from within a variety of distributions and package managers.
-            Package Managers which include gnurl are:
-            <a href="https://www.gnu.org/software/guix/">GNU Guix</a> (available as "gnurl"),
-            <a href="https://gentoo.org">Gentoo</a> through the collaborative ebuild collection
-            <a href="https://git.gnunet.org/youbroketheinternet-overlay.git/">youbroketheinternet</a>,
-            <a href="https://nixos.org/nix/">Nix</a>, and as www/gnurl in
-            <a href="https://pkgsrc.org">pkgsrc</a>.
-          {% endtrans %}
-        </p>
+      <div class="row">
+        <div class="col-md">
+          <h2>{{ _("About gnurl") }}</h3>
+          <p>
+            {% trans %}
+              Large parts of the following 6 paragraphs are old and need
+              to be rewritten.
+            {% endtrans %}
+          </p>
+        </div>
       </div>
-    </div>
-
-    <div class="row container">
-      <div class="col-md">
-        <a name="building"></a>
-        <h3>{{ _("Building gnurl") }}</h3>
-        <p>
-          {% trans %}
-            We suggest to closely follow release announcements, as they
-            might indicate changes in how gnurl is to be build.
-            <br>
-            If your package manager provides a binary build or build
-            instructions to build gnurl from source automated and
-            integrated with your environment, we strongly suggest to use
-            this binary build.
-            <br>
-            There are two ways to build gnurl. The first one builds from
-            the most recent git tag, the second one uses the distributed
-            tarball. Distributors generally are supposed to build from
-            the tarball, but we describe both methods here. Both methods
-            are written with a NetBSD 9 userland in mind, substitute tools
-            as necessary.
-            <br>
-            You should <b>avoid</b> building gnurl from the tip of the
-            default git branch, as only tags are considered to be stable
-            and approved builds.
-          {% endtrans %}
-        </p>
-        <h4>{{ _("Building from the distributed tarball (prefered method)") }}</h4>
-        <p>
-          {% trans %}
-            If you want to verify the signature, install an OpenPGP compatible tool such
-            as security/gnupgp2 (and set it up). Assuming you use pkgin:
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            pkgin update
-          </li>
-          <li>
-            pkgin install gnupg2
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            Fetch the signature key from
-          {% endtrans %}
-          <a href="https://keys.openpgp.org/search?q=ng0%40n0.is">keys.openpgp.org</a>
-          {% trans %}
-            or via commandline with gnupg2.
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            Fetch the release, the signature, the checksum file as well as its signature:
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            ftp https://ftpmirror.gnu.org/gnu/gnunet/gnurl-7.65.3.tar.Z
-          </li>
-          <li>
-            ftp https://ftpmirror.gnu.org/gnu/gnunet/gnurl-7.65.3.tar.Z.sig
-          </li>
-          <li>
-            ftp https://ftpmirror.gnu.org/gnu.org/gnunet/gnurl-7.65.3.sum.txt
-          </li>
-          <li>
-            ftp https://ftpmirror.gnu.org/gnu.org/gnunet/gnurl-7.65.3.sum.txt.sig
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            verify the signatures, and verify the checksums against the
-            checksums in the .sum.txt file.
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            unpack the tarball:
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            tar -zxf gnurl-7.65.3.tar.Z
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            Change into the directory
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            cd gnurl-7.65.3
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            Now you can either run
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            ./configure
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            directly (and read configure-gnurl before you do so) or invoke
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            ./configure-gnurl
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            and pass additional parameters such as a custom PREFIX location.
-            Further reference can be the
-          {% endtrans %}
-          <a href="http://pkgsrc.se/www/gnurl">www/gnurl</a> Makefile.
-          {% trans %}
-            Now run
-          {% endtrans %}
-        </p>
-        <ul>
-          <li>
-            make
-          </li>
-          <li>
-            make check
+      <div class="row">
+        <div class="col-md">
+          <a name="motivation"></a>
+          <h3>{{_("Motivation") }}</h4>
+          <p>
+            {% trans %}
+              cURL supports many crypto backends. GNUnet requires the use of
+              GnuTLS, but other variants are used by some distributions. Supporting
+              other crypto backends would again expose us to a wider array of
+              security issues, may create licensing issues and most importantly
+              introduce new bugs as some crypto backends are known to introduce
+              subtle runtime issues. While it is possible to have two versions of
+              libcurl installed on the same system, this is error-prone, especially
+              as if we are linked against the wrong version, the bugs that arise
+              might be rather subtle.
+            {% endtrans %}
+          </p>
+          <p>
             {% trans %}
-              (this is optional)
+              For GNUnet, we also need a particularly modern version of
+              GnuTLS. Thus, it would anyway be necessary to recompile cURL for
+              GNUnet. But what happens if one links cURL against this version of
+              GnuTLS? Well, first one would install GnuTLS by hand in the
+              system. Then, we build cURL. cURL will build against it just fine, but
+              the linker will eventually complain bitterly. The reason is that cURL
+              also links against a bunch of other system libraries (gssapi, ldap,
+              ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above),
+              which --- as they are part of the distribution --- were linked against
+              an older version of GnuTLS. As a result, the same binary would be
+              linked against two different versions of GnuTLS. That is typically a
+              recipe for disaster. Thus, in order to avoid updating a dozen system
+              libraries (and having two versions of those installed), it is
+              necessary to disable all of those cURL features that GNUnet does not
+              use, and there are many of those. For GNUnet, the more obscure
+              protocols supported by cURL are close to dead code --- mostly
+              harmless, but not useful. However, as some application may use one of
+              those features, distributions are typically forced to enable all of
+              those features, and thus including security issues that might arise
+              from that code.
             {% endtrans %}
-          </li>
-          <li>
-            make install
-          </li>
-        </ul>
-        <p>
-          {% trans %}
-            and you are done.
-          {% endtrans %}
-        </p>
-        <h4>{{ _("Building from a tagged git commit") }}</h4>
-        <p>
-          {% trans %}
-            Follow the steps above, but instead of downloading the tarball,
-            clone the git tag you want to build from.
-          {% endtrans %}
-        </p>
+          </p>
+          <p>
+            {% trans %}
+              So to use a modern version of GnuTLS, a sane approach is to disable
+              all of the "optional" features of cURL that drag in system libraries
+              that link against the older GnuTLS. That works, except that one should
+              then NEVER install that version of libcurl in say /usr or /usr/local,
+              as that may break other parts of the system that might depend on these
+              features that we just disabled. Libtool versioning doesn't help here,
+              as it is not intended to deal with libraries that have optional
+              features. Naturally, installing cURL somewhere else is also
+              problematic, as we now need to be really careful that the linker will
+              link GNUnet against the right version. Note that none of this can
+              really be trivially fixed by the cURL developers.
+            {% endtrans %}
+          </p>
+        </div>
       </div>
-    </div>
+      <div class="row">
+        <div class="col-md">
+          <a name="rename"></a>
+          <h3>{{_("Rename to fix") }}</h4>
+          <p>
+            {% trans %}
+              How does forking fix it? Easy. First, we can get rid of all of the
+              compatibility issues --- if you use libgnurl, you state that you don&#39;t
+              need anything but HTTP/HTTPS. Those applications that need more,
+              should stick with the original cURL. Those that do not, can choose to
+              move to something simpler. As the library gets a new name, we do not
+              have to worry about tons of packages breaking as soon as one rebuilds
+              it. So renaming itself and saying that "libgnurl = libcurl with only
+              HTTP/HTTPS support and GnuTLS" fixes 99%% of the problems that darkened
+              my mood. Note that this pretty much CANNOT be done without a fork, as
+              renaming is an essential part of the fix. Now, there might be creative
+              solutions to achieve the same thing within the standard cURL build
+              system, but I'm not happy to wait for a decade for Daniel to review
+              the patches. The changes libgnurl makes to curl are miniscule and can
+              easily be applied again and again whenever libcurl makes a new
+              release.
+            {% endtrans %}
+          </p>
+        </div>
+        <div class="col-md">
+          <a name="using"></a>
+          <h3>{{_("Using libgnurl") }}</h4>
+          <p>
+            {% trans %}
+              Projects that use cURL only for HTTP/HTTPS and that would work
+              with GnuTLS should be able to switch to libgnurl by changing
+              "-lcurl" to "-lgnurl". That&#39;s it. No changes to the source code
+              should be required,
+              as libgnurl strives for bug-for-bug compatibility with the
+              HTTP/HTTPS/GnuTLS subset of cURL.
+              We might add new features relating to this core subset if they
+              are proposed, but so far we have kept our changes minimal and
+              no additions to the original curl source have been written.
+            {% endtrans %}
+          </p>
+        </div>
+      </div>
+      <div class="row">
+        <div class="col-md">
+          <a name="gotchas"></a>
+          <h3>{{_("Gotchas") }}</h4>
+          <p>
+            {% trans %}
+              libgnurl and gnurl are not intended to be used as a replacement
+              for curl for users:
+              <br>
+              This does not mean there is no confidence in the work done
+              with gnurl, it means that tools which expect curl or libcurl
+              will not make use of a different named binary and library.
+              If you know what you are doing, you should be able to use
+              gnurl as part of your tooling in place of curl. We do not
+              recommend to do so however, as the only usage it is tested
+              for <em>so far</em> is as part of Taler&#39;s and GNunet&#39;s
+              build-system.
+              <br>
+              Since no conflicts in filenames occur you are not expected
+              to remove curl to make use of gnurl and viceversa.
+            {% endtrans %}
+          </p>
+        </div>
+      </div>
+
+      <div class="row">
+        <div class="col-md">
+          <a name="source"></a>
+          <h2>{{ _("Source Code") }}</h3>
+          <p>
+            {% trans %}
+              You can get the gnurl git repository using:
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              <code>git clone https://git.taler.net/gnurl.git</code>
+            </li>
+            <li>
+              <code>git clone git://git.taler.net/gnurl.git</code>
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              The versions are checked in as (signed) git tags.
+            {% endtrans %}
+          </p>
+        </div>
 
-    <div class="row container">
-      <div class="col-md">
-        <a name="reporting"></a>
-        <h3>{{ _("Reporting Bugs") }}</h3>
-        <p>
-          {% trans %}
-            You can report bugs on our bug tracker:
-            <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>. Alternatively
-            you can use our bug mailinglist, but we prefer to track bugs
-            on the bugtracker.
-          {% endtrans %}
-        </p>
+        <div class="col-md">
+          <a name="downloads"></a>
+          <h2>{{ _("Downloads") }}</h3>
+          <p>
+            {% trans %}
+              Releases are published on <a href="https://ftpmirror.gnu.org/gnu/gnunet/">ftpmirror.gnu.org/gnu/gnunet</a>.
+              gnurl is available from within a variety of distributions and package managers.
+              Package Managers which include gnurl are:
+              <a href="https://www.gnu.org/software/guix/">GNU Guix</a> (available as "gnurl"),
+              <a href="https://gentoo.org">Gentoo</a> through the collaborative ebuild collection
+              <a href="https://git.gnunet.org/youbroketheinternet-overlay.git/">youbroketheinternet</a>,
+              <a href="https://nixos.org/nix/">Nix</a>, and as www/gnurl in
+              <a href="https://pkgsrc.org">pkgsrc</a>.
+            {% endtrans %}
+          </p>
+        </div>
       </div>
-      <div class="col-md">
-        <a name="maintainer"></a>
-        <h3>{{ _("Maintainer and Cryptographic signatures") }}</h3>
-        <p>
-          {% trans %}
-            gnurl/libgnurl is maintained by ng0.
-            Releases are signed
-            with the OpenPGP Key <b>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</b>,
-            with the key fingerprint <b>A88C 8ADD 1298 28D7 EAC0  2E52 E22F 9BBF EE34 8588</b>.
-          {% endtrans %}
-        </p>
+
+      <div class="row">
+        <div class="col-md">
+          <a name="building"></a>
+          <h2>{{ _("Building gnurl") }}</h3>
+          <p>
+            {% trans %}
+              We suggest to closely follow release announcements, as they
+              might indicate changes in how gnurl is to be build.
+              <br>
+              If your package manager provides a binary build or build
+              instructions to build gnurl from source automated and
+              integrated with your environment, we strongly suggest to use
+              this binary build.
+              <br>
+              There are two ways to build gnurl. The first one builds from
+              the most recent git tag, the second one uses the distributed
+              tarball. Distributors generally are supposed to build from
+              the tarball, but we describe both methods here. Both methods
+              are written with a NetBSD 9 userland in mind, substitute tools
+              as necessary.
+              <br>
+              You should <b>avoid</b> building gnurl from the tip of the
+              default git branch, as only tags are considered to be stable
+              and approved builds.
+            {% endtrans %}
+          </p>
+          <h3>{{ _("Building from the distributed tarball (prefered method)") }}</h4>
+          <p>
+            {% trans %}
+              If you want to verify the signature, install an OpenPGP compatible tool such
+              as security/gnupgp2 (and set it up). Assuming you use pkgin:
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              pkgin update
+            </li>
+            <li>
+              pkgin install gnupg2
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              Fetch the signature key from
+            {% endtrans %}
+            <a href="https://keys.openpgp.org/search?q=ng0%40n0.is">keys.openpgp.org</a>
+            {% trans %}
+              or via commandline with gnupg2.
+            {% endtrans %}
+          </p>
+          <p>
+            {% trans %}
+              Fetch the release, the signature, the checksum file as well as its signature:
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              ftp https://ftpmirror.gnu.org/gnu/gnunet/gnurl-7.65.3.tar.Z
+            </li>
+            <li>
+              ftp https://ftpmirror.gnu.org/gnu/gnunet/gnurl-7.65.3.tar.Z.sig
+            </li>
+            <li>
+              ftp https://ftpmirror.gnu.org/gnu.org/gnunet/gnurl-7.65.3.sum.txt
+            </li>
+            <li>
+              ftp https://ftpmirror.gnu.org/gnu.org/gnunet/gnurl-7.65.3.sum.txt.sig
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              verify the signatures, and verify the checksums against the
+              checksums in the .sum.txt file.
+            {% endtrans %}
+          </p>
+          <p>
+            {% trans %}
+              unpack the tarball:
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              tar -zxf gnurl-7.65.3.tar.Z
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              Change into the directory
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              cd gnurl-7.65.3
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              Now you can either run
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              ./configure
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              directly (and read configure-gnurl before you do so) or invoke
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              ./configure-gnurl
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              and pass additional parameters such as a custom PREFIX location.
+              Further reference can be the
+            {% endtrans %}
+            <a href="http://pkgsrc.se/www/gnurl">www/gnurl</a> Makefile.
+            {% trans %}
+              Now run
+            {% endtrans %}
+          </p>
+          <ul>
+            <li>
+              make
+            </li>
+            <li>
+              make check
+              {% trans %}
+                (this is optional)
+              {% endtrans %}
+            </li>
+            <li>
+              make install
+            </li>
+          </ul>
+          <p>
+            {% trans %}
+              and you are done.
+            {% endtrans %}
+          </p>
+          <h3>{{ _("Building from a tagged git commit") }}</h4>
+          <p>
+            {% trans %}
+              Follow the steps above, but instead of downloading the tarball,
+              clone the git tag you want to build from.
+            {% endtrans %}
+          </p>
+        </div>
       </div>
-    </div>
 
+      <div class="row">
+        <div class="col-md">
+          <a name="reporting"></a>
+          <h2>{{ _("Reporting Bugs") }}</h3>
+          <p>
+            {% trans %}
+              You can report bugs on our bug tracker:
+              <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>. Alternatively
+              you can use our bug mailinglist, but we prefer to track bugs
+              on the bugtracker.
+            {% endtrans %}
+          </p>
+        </div>
+
+        <div class="col-md">
+          <a name="maintainer"></a>
+          <h2>{{ _("Maintainer and Cryptographic signatures") }}</h3>
+          <p>
+            {% trans %}
+              gnurl/libgnurl is maintained by ng0.
+              Releases are signed with the OpenPGP Key
+              <b>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</b>,
+              with the key fingerprint
+              <b>A88C 8ADD 1298 28D7 EAC0  2E52 E22F 9BBF EE34 8588</b>.
+            {% endtrans %}
+          </p>
+        </div>
+      </div>
+    </section>
   </article> <!-- /container -->
 {% endblock body_content %}
diff --git a/template/install.html.j2 b/template/install.html.j2
index 03313f64..2245b9fb 100644
--- a/template/install.html.j2
+++ b/template/install.html.j2
@@ -7,12 +7,24 @@
   </header>
 
   <div class="row container justify-content-center">
-          <div class="alert" style="background-color: #419edb;">
-        <div class="alert-content">
+    <div class="alert" style="background-color: #419edb;">
+      <div class="alert-content">
           Notice: GNUnet is still undergoing major development. It is
           largely <i>not yet ready</i> for usage beyond developers.
-        </div>
       </div>
+    </div>
+  </div>
+
+  <h3>Current release downloads:</h3>
+  <div class="row container justify-content-center">
+    <div class="col-md">
+    <b>gnunet</b>: <a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz">0.12.0</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig">sig</a>) sha512sum: <tt>5457d6f80478b28821de70b4da419d40d6972d270622bdeb83e5552b286fd032</tt><br>
+    <b>gnunet-gtk</b>: <a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz">0.12.0</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig">sig</a>) sha512sum: <tt>cb99da11d68107f9709ee5be49cc574e9a03054767334767930ae6b0bd1a4421</tt><br/>
+    <b>gnunet-fuse</b>: <a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz">0.12.0</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig">sig</a>) sha512sum: <tt>4d42dc3112f36ada150b3904e207b93373c90d4fbd5a1c6415ee7f5c6a428e3b</tt>
+    </div>
+  </div>
+  <h3>Instructions</h3><br/>
+  <div class="row container justify-content-center">
     <div class="col-md">
       {% trans %}
       <p>The following GNUnet installation instructions help you building from source for your Operating System.</p>
diff --git a/www.yml b/www.yml
index 8a019878..aeb0dbaa 100644
--- a/www.yml
+++ b/www.yml
@@ -56,6 +56,11 @@ meetingnotes:
   2017: 2017-12-27
   2018: 2018-12-27
 newsposts:
+  - page: 2019-0.12.0.html
+    date: 2019-12-20
+    title: GNUnet 0.12.0
+    abstract:
+    content:
   - page: 2019-11-ICANNUpdate.html
     date: 2019-11-10
     title: GNS@ICANN66