aboutsummaryrefslogtreecommitdiff
path: root/template
diff options
context:
space:
mode:
Diffstat (limited to 'template')
-rw-r--r--template/news/2011-11-24-archived-vfork.html.j262
-rw-r--r--template/news/2013-11-15-special-use-gns.html.j214
-rw-r--r--template/news/2013-12-28-archived-typos-pkeys.html.j216
-rw-r--r--template/news/2018-06.html.j2108
-rw-r--r--template/news/2018-07.html.j27
-rw-r--r--template/news/2019-0.11.0.html.j272
-rw-r--r--template/news/2019-0.11.1.html.j255
-rw-r--r--template/news/2019-0.11.2.html.j255
-rw-r--r--template/news/2019-0.11.3.html.j252
-rw-r--r--template/news/2019-0.11.4.html.j250
-rw-r--r--template/news/2019-0.11.5.html.j247
-rw-r--r--template/news/2019-0.11.6.html.j252
-rw-r--r--template/news/2019-0.11.7.html.j256
-rw-r--r--template/news/2019-0.11.8.html.j247
-rw-r--r--template/news/2019-0.12.0.html.j285
-rw-r--r--template/news/2019-0.12.1.html.j226
-rw-r--r--template/news/2019-02.html.j275
-rw-r--r--template/news/2019-06-DSTJ.html.j214
-rw-r--r--template/news/2019-06.html.j27
-rw-r--r--template/news/2019-07-GHM_Aug_2019.html.j27
-rw-r--r--template/news/2019-10-GNSSpec1.html.j219
-rw-r--r--template/news/2019-10-ICANNPanel.html.j213
-rw-r--r--template/news/2019-11-ICANNUpdate.html.j210
-rw-r--r--template/news/2019-12-UpcomingTalks.html.j273
-rw-r--r--template/news/2020-01-0.12.2.html.j271
-rw-r--r--template/news/2020-01-GNSSpec2.html.j228
-rw-r--r--template/news/2020-05-GHM_Jun_2020.html.j28
-rw-r--r--template/news/2020-06-GNSSpec3.html.j225
-rw-r--r--template/news/2020-07-0.13.0.html.j2103
-rw-r--r--template/news/2020-07-0.13.1.html.j229
-rw-r--r--template/news/2020-08-0.13.2.html.j258
-rw-r--r--template/news/2020-09-0.13.3.html.j251
-rw-r--r--template/news/2020-11-0.14.0.html.j281
-rw-r--r--template/news/2020-11-GNSSpec4.html.j245
-rw-r--r--template/news/2021-03-0.14.1.html.j248
-rw-r--r--template/news/2021-03-gsoc-update.html.j213
-rw-r--r--template/news/2021-04-DISSENS.html.j266
-rw-r--r--template/news/index.html.j257
l---------template/news/oldnews-2011.html.j21
l---------template/news/oldnews-2013.html.j21
-rw-r--r--template/news/oldnews-2018.html.j250
l---------template/news/oldnews-2019.html.j21
42 files changed, 1758 insertions, 0 deletions
diff --git a/template/news/2011-11-24-archived-vfork.html.j2 b/template/news/2011-11-24-archived-vfork.html.j2
new file mode 100644
index 00000000..61249c38
--- /dev/null
+++ b/template/news/2011-11-24-archived-vfork.html.j2
@@ -0,0 +1,62 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>vfork and the signal race</h1>
4<p>
5 <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
6</p>
7<p>
8Many articles uniformly claim that using vfork should be
9<a href="https://web.archive.org/web/20150924082249/http://tldp.org/HOWTO/Secure-Programs-HOWTO/avoid-vfork.html">avoided</a>
10and that the only difference between vfork and fork is (or used-to-be)
11<a href="https://web.archive.org/web/20150924082249/http://www.unixguide.net/unix/programming/1.1.2.shtml">performance</a>
12and that thus vfork is
13<a href="https://web.archive.org/web/20150924082249/http://stackoverflow.com/questions/4856255/the-difference-between-fork-vfork-exec-and-clone">obsolete</a>.
14Here, I wanted to document a technical case where vfork is actually required and where using fork instead of vfork (or operating system implementors implementing vfork as an alias for fork) causes a hard-to-find data race.
15</p>
16<p>
17GNUnet uses a hypervisor process (gnunet-service-arm) to control the peer's service processes. Services are started (vfork+exec) on-demand. The hypervisor is also responsible for stopping the services and sends a SIGTERM signal to the services to stop them. SIGTERM must be used to allow the services to shutdown gracefully. Naturally, after shutting down a service with a signal, the hypervisor waits for SIGCHILD and then cleans up with waitpid. Once all services processes have completed, the hypervisor can exit as well. It should also be noted that the hypervisor handles SIGTERM (by shutting down all services), so a signal handler is installed for that signal.
18</p>
19<p>
20The reason why we must use vfork is the following. After the hypervisor has started the service, it might be asked to stop the service at any time. We've actually managed (by scripting it) to reliably trigger a case where the hypervisor would start a service (fork) and then receive a request to terminate the service and issues the SIGTERM signal to the child before the child process had a chance to call exec. As a result, the SIGTERM would go to the (existing) handler of the hypervisor's code, then the child process would be exec'ed and essentially the signal was thereby lost in the race between kill and exec:
21</p>
22<p>
23If exec wins, the signal either kills the process hard during the service startup phase, which is fine, or the service process might handle it normally and terminate --- also fine).
24</p>
25<p>
26If kill wins the race, the signal would be lost and the hypervisor would wait 'forever' for the child to terminate.
27</p>
28<p>
29The solution with vfork is elegant and simple: by blocking the parent, vexec guarantees that the parent's signal handler is no longer active (and replaced by default handlers or the child's custom handlers) by the time the parent is able to issue a 'kill'.
30</p>
31<p>
32In conclusion, with parents that issue 'kill' on child processes, the use of vfork can make an important semantic difference and not only (possibly) offer performance advantages. The situation above cannot be easily fixed by other means and thus vfork is an important POSIX call that should be supported properly by all quality implementations. A possible hack to work around a lack of vfork would be to create a pipe in the parent, set it to close-on-exec, fork the child, close the write end and then do a blocking read from the read end. Once you get a read error, the child has exec'ed. Rather ugly in my opinion.
33</p>
34<p>
35Currently, gnunet-service-arm can hang indefinitely on systems that do not provide a correct implementation of vfork (however, in practice normal users should never encounter this).
36</p>
37<p>
38<b>better suggestion from Thomas Bushnell</b>
39<br>
40I just got an alternative suggestion to using either a pipe and vfork from Thomas Bushnell, which I like and will use:
41
42"The hypervisor at start creates a global variable hypervisor_pid, initialized from getpid().
43
44The signal handler in the hypervisor then does this:
45<br>
46<code class="block">
47if getpid() == hypervisor_pid<br>
48 kill_all_children_and_exit();<br>
49else<br>
50 exit();<br>
51</code>
52
53In this way, if the child is between fork and exec when the parent gets its kill, and then it tries to kill the child, and the kill happens before the child execs (the problematic case you describe), then the child simply enters the hypervisor's signal handler, notices that it's not the hypervisor, and exits.
54<br>
55Thomas"
56<br>
57Thanks for the suggestion!
58</p>
59<p>
60Thomas's suggestion is all fine and well, except that it doesn't work on OS X. As the attached simple program "killing-child-kills-parent.c" demonstrates, OS X manages to sometimes either deliver the signal to the wrong process (?) or not update getpid() between fork+exec or is otherwise generally broken. The program simply installs a signal handler in the parent with the guard suggested by Thomas, then forks + exec's "sleep" and then immediately kills the child. So we expect the signal to either reach our signal handler (child between fork+exec), causing the child to 'exit', or to reach 'sleep' which should also die. Somehow instead the "Should NEVER get this signal!" message is printed. Well, OS X is known to be a pile of crap, so no surprise. Using 'vfork' instead of fork gets us the desired behavor -- howver, this is clearly just a hack. So vfork is back (on OS X) as of SVN 25495.
61</p>
62{% endblock body_content %}
diff --git a/template/news/2013-11-15-special-use-gns.html.j2 b/template/news/2013-11-15-special-use-gns.html.j2
new file mode 100644
index 00000000..329e74d3
--- /dev/null
+++ b/template/news/2013-11-15-special-use-gns.html.j2
@@ -0,0 +1,14 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>Special-Use Domain Names of Peer-to-Peer Name Systems</h1>
4<p>
5 <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
6</p>
7<p>
8We just submitted our draft for
9<a href="https://web.archive.org/web/20140901155643/https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/">Special-Use Domain Names of Peer-to-Peer Name Systems</a> to IETF.
10The intention is to reserve the TLDs ".exit", ".i2p", ".gnu",
11".onion" and ".zkey" for use by the GNUnet, I2P and Tor peer-to-peer overlay
12networks.
13</p>
14{% endblock body_content %}
diff --git a/template/news/2013-12-28-archived-typos-pkeys.html.j2 b/template/news/2013-12-28-archived-typos-pkeys.html.j2
new file mode 100644
index 00000000..a541ef94
--- /dev/null
+++ b/template/news/2013-12-28-archived-typos-pkeys.html.j2
@@ -0,0 +1,16 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>Typo-Protected Public Keys</h1>
4<p>
5 <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
6</p>
7<p>
8When users type in public keys (such as the 53-characters of a GNS zone), they might make typos. The usual way to fix typos is to add a checksum, further increasing the length of the sequence that has to be typed in.
9<br>
10We can fix this by including the checksum of the public key in the public key itself, simply by trying new private keys until the corresponding public key happens to have a checksum (over the other bits) in the bits designated for the checksum. If a checksum is 16 bits, we would only need to try 216 keys. The basic idea of brute-forcing keys to match a particular pattern <a href="https://web.archive.org/web/20141008173738/https://bitcointalk.org/index.php?topic=84569.0">was proposed before</a> for creating "vanity" public keys, but this might be another practical variant.
11</p>
12<p>
13<b>Acknowledgements</b><br/>
14The idea popped up in a discussion on the need for short public keys for GNS with Dan Bernstein and Tanja Lange at 30c3.
15</p>
16{% endblock body_content %}
diff --git a/template/news/2018-06.html.j2 b/template/news/2018-06.html.j2
new file mode 100644
index 00000000..08428466
--- /dev/null
+++ b/template/news/2018-06.html.j2
@@ -0,0 +1,108 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.0pre66</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.0pre66.<br>
6 This is a pre-release to assist developers and downstream packagers to test the package before the final release after four years of development.
7</p>
8<p>
9 In terms of usability, users should be aware that there are still a very large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (~200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.0 release and especially this pre-release are only suitable for early adopters with some reasonable pain tolerance.
10</p>
11<h4 class="western">License change</h4>
12<p>
13 GNUnet 0.11.0pre66 is the first release that will be made under the GNU Affero General Public License v3+. After a significant amount of internal discussion lead constructively by lynX (thanks!), the conclusion has been that the IPC and REST APIs should be extended with support for an GNUNET_MESSAGE_TYPE_AGPL or /agpl request that enables users of these client/service-style APIs to download the source code.
14</p>
15<p>
16 Naturally, the discussion on licensing may not necessarily end here, but at this point we are not aware of any dissent in the community and this release seems to be the right time to make such a change. While the final decision was not subjected to a broad feedback round, this was done simply on the grounds that this placement of the AGPL API seems to addresses all concerns that were raised. Finally, thanks to the copyright assignment all developers are participating in, the community will be able to revise this decision later if necessary.
17</p>
18<p>
19 It should also be noted that this change does not impose additional restrictions on the licensing models of GNU Taler or pEp: both projects have agreements with GNUnet e.V. that ensure that they can make decisions that fit these applications (not to mention significant parts of GNU Taler are already AGPLv3+ already).
20</p>
21<h4 class="western">About GNUnet</h4>
22<p>
23 GNUnet is a framework for secure peer-to-peer networking. GNUnet&#39;s primary design goals are to protect the privacy of its users and to guard itself against attacks or abuse. At this point, GNUnet offers four primary applications on top of the framework:
24</p>
25<p>
26 The file-sharing service allows anonymous censorship-resistant file-sharing. Files, searches and search results are encrypted to make it hard to control, track or censor users. GNUnet&#39;s anonymity protocol (gap) is designed to make it difficult to link users to their file-sharing activities. Users can also individually trade-off between performance and anonymity. Despite providing anonymity, GNUnet&#39;s excess-based economy rewards contributing users with better performance.
27</p>
28<p>
29 The VPN service allows offering of services within GNUnet (using the .gnu TLD) and can be used to tunnel IPv4 and IPv6 traffic over the P2P network. The VPN can also be used for IP protocol translation (6-to-4, 4-to-6) and it is possible to tunnel IP traffic over GNUnet (6-over-4, 4-over-6). Note that at this stage, it is possible for peers to determine the IP address at which services are hosted, so the VPN does not offer anonymity.
30</p>
31<p>
32 The GNU Name System (GNS) provides a fully-decentralized and censorship resistant replacement for DNS. GNS can be used alongside DNS and can be integrated with legacy applications (such as traditional browsers) with moderate effort. GNS provides censorship-resistance, memorable names and cryptographic integrity protection for the records. Note that at this stage, it is possible for a strong adversary to determine which peer is responsible for a particular zone, GNS does not offer strong anonymity. However, GNS offers query privacy, that is other participants can typically not decrypt queries or replies.
33</p>
34<p>
35 Conversation allows voice calls to be made over GNUnet. Users are identified using GNS and voice data is encrypted. However, Conversation does not provide anonymity at this stage --- other peers may observe a connection between the two endpoints and it is possible to determine the IP address associated with a phone.
36</p>
37<p>
38 Other applications, including in particular the SecuShare social networking application, are still strictly experimental.
39</p>
40<p>
41 For developers, GNUnet offers:
42</p>
43<ul>
44 <li>Access to all subsystems via clean C APIs</li>
45 <li>Mostly written in C, but extensions possible in other languages</li>
46 <li>Multi-process architecture for fault-isolation between components</li>
47 <li>Use of event loop and processes instead of threads for ease of development</li>
48 <li>Extensive logging and statistics facilities</li>
49 <li>Integrated testing library for automatic deployment of large-scale experiments with tens of thousands of peers</li>
50</ul>
51<h4 class="western">Noteworthy improvements in 0.11.0pre66</h4>
52<ul>
53 <li>Improved documentation, converting Drupal handbook to Texinfo (thanks ng0!)</li>
54 <li>GNU Name System now can take over arbitrary TLDs, and support for conversion from DNS zones to GNS exists</li>
55 <li>Critical bugfixes in CORE, DHT and CADET subsystems</li>
56</ul>
57<p>
58 The above is just the short list, our bugtracker lists over 350 individual issues that were resolved (see <a href="https://gnunet.org/bugs/changelog_page.php">Changelog</a>)
59</p>
60<h4 class="western">Known Issues</h4>
61<p>
62 We have a few issues that are most likely not resolved in the final release. Users should be aware of these issues, which we hope to address shortly.
63</p>
64<ul>
65 <li>There are known major design issues in TRANSPORT, ATS and CORE which will need to be addressed for usability, performance and security.</li>
66 <li>There are known moderate implementation limitations in CADET that impact performance.</li>
67 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
68 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
69 <li>The Web site and manuals still need significant rework.</li>
70 <li>Subsystems related to SecuShare and RPS remain experimental.</li>
71</ul>
72<p>
73 In addition to this list, you may also want to consult our bug tracker at https://gnunet.org/bugs/ which lists about 200 more specific issues.
74</p>
75<h4>Availability</h4>
76<p>
77 The GNUnet 0.11.0pre66 source code is available from all GNU FTP mirrors. The GTK frontends (which includes the gnunet-setup tool) are a separate download. Please note that some mirrors might still be synchronizing.
78</p>
79<ul>
80 <li>GNUnet on a FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0pre66.tar.gz</li>
81 <li>GNUnet GTK on an FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0pre66.tar.gz</li>
82 <li>GNUnet FUSE on an FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0pre66.tar.gz</li>
83 <li>GNUnet on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-0.11.0pre66.tar.gz</li>
84 <li>GNUnet GTK on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-gtk-0.11.0pre66.tar.gz</li>
85 <li>GNUnet FUSE on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-fuse-0.11.0pre66.tar.gz</li>
86</ul>
87<p>
88 Note that GNUnet is now started using &quot;gnunet-arm -s&quot;. GNUnet should be stopped using &quot;gnunet-arm -e&quot;.
89</p>
90<h4 class="western">Thanks</h4>
91<p>
92 This release was the work of many people. The following people contributed code and were thus easily identified:
93 Christian Grothoff,
94 Matthias Wachs, Bart Polot, Sree Harsha Totakura, Nathan S. Evans,
95 Martin Schanzenbach, Julius B&uuml;nger, Nils Gillmann, Philipp
96 T&ouml;lke, Florian Dold, &#1056;&#1091;&#1089;&#1083;&#1072;&#1085;
97 &#1048;&#1078;&#1073;&#1091;&#1083;&#1072;&#1090;&#1086;&#1074;,
98 tg(x), David Barksdale, Christian Fuchs, Nils Durner, Omar Tarabai,
99 Maximilian Szengel, Supriti Singh, lurchi, David Brodski, xrs, Fabian
100 Oehlmann, Carlo von lynX, Christophe Genevey Metat, Jeffrey Burdges,
101 Safey A.Halim, Daniel Golle, Phil, Bruno Cabral, Ji Lu, Heikki
102 Lindholm, Markus Teich, t3sserakt, Claudiu Olteanu, Marcello
103 Stanisci, Moon, anryko, Arthur Dewarumez, Julien Morvan, Adnan H, Lin
104 Tong, Andreas Fuchs, Christian Rupp, jah, Alejandra Morales, Matthias
105 Kolja Miehl, Andrew Cann, Antonio Ojea, Pascal Mainini, amirouche and
106 hark.
107</p>
108{% endblock body_content %}
diff --git a/template/news/2018-07.html.j2 b/template/news/2018-07.html.j2
new file mode 100644
index 00000000..e8c14fea
--- /dev/null
+++ b/template/news/2018-07.html.j2
@@ -0,0 +1,7 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>Second GNUnet Hacker Meeting 2018 at La D&#233;centrale, Switzerland</h1>
4 <p>
5 The GNUnet hackers met for the second time this year. The primary goal was to squash bugs to bring out a new release. Aside from this we worked hard on improving the documentation and to launch this new website.
6 </p>
7{% endblock body_content %}
diff --git a/template/news/2019-0.11.0.html.j2 b/template/news/2019-0.11.0.html.j2
new file mode 100644
index 00000000..ddf04623
--- /dev/null
+++ b/template/news/2019-0.11.0.html.j2
@@ -0,0 +1,72 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.0 released</h1>
4 <p>
5 We are pleased to announce the release of GNUnet 0.11.0.<br>
6 This is a major release after about five years of development. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.0 release is still only suitable for early adopters with some reasonable pain tolerance.
7</p>
8<h4>Download links</h4>
9<ul>
10 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz</a></li>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
16</ul>
17<p>
18 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>
19</p>
20<p>
21 Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
22</p>
23<h4>Noteworthy changes in 0.11.0</h4>
24<ul>
25 <li>The Web site and manuals have undergone significant rework. You can find an archive of the old Web site at <a href="http://web.archive.org/web/*/gnunet.org">archive.org</a>.</li>
26 <li>The code now builds again on macOS. GNUnet on macOS is <i>experimental</i>. While it builds and seems to run fine, some tests are known to fail.</li>
27 <li>Build process now works properly with libidn2</li>
28 <li>Except for <tt>gnunet-qr</tt>, all Python code was migrated to Python 3.7.</li>
29 <li>Fixed security issues in secret sharing cryptography logic</li>
30 <li>Services running out of file descriptors on <tt>accept()</tt> no longer busy wait</li>
31 <li>Fixed crash in gnunet-gns2dns proxy</li>
32 <li>GNS responses are now padded to minimize information disclosure from the size</li>
33 <li>Fixed API issues and (rare) crash bugs in CADET</li>
34 <li>The experimental SecuShare code is not included in the release, you can now find it in the <a href="https://git.gnunet.org/gnunet-secushare.git/">gnunet-secushare</a> Git repository.</li>
35 <li>The Ascension tool (separate download) now allows importing DNS zones into GNS via AXFR.</li>
36 <li>GNUnet now includes a decentralised identity attribute sharing service: reclaimID. A ready-to-use client can be found in an <a href="https://gitlab.com/reclaimid/client">external repo</a>.</li>
37 <li>The code now builds again on NetBSD. GNUnet on NetBSD is <i>experimental</i>. While it builds and seems to run fine, full support requires more changes in the core of GNUnet It will soon be available via pkgsrc.</li>
38 <li>Many things changed on the build system side. If you package GNUnet for an operating system or otherwise package manager, make sure that you read the README.</li>
39</ul>
40<p>
41 The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=258">over 100 individual issues</a> that were resolved since 0.11.0pre66.
42</p>
43 <h4>Known Issues</h4>
44 <ul>
45 <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>
46 <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
47 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
48 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
49 <li>The RPS subsystem remains experimental.</li>
50 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
51 </ul>
52<p>
53 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 150 more specific issues.
54</p>
55<h4>Thanks</h4>
56<p>
57 This release was the work of many people. The following people
58 contributed code and were thus easily identified:
59 Christian Grothoff, Matthias Wachs, Bart Polot, Sree Harsha Totakura,
60 Nathan S. Evans, Martin Schanzenbach, Julius B&#xFC;nger, ng0,
61 Philipp T&#xF6;lke, Florian Dold, &#x420;&#x443;&#x441;&#x43B;&#x430;&#x43D; &#x418;&#x436;&#x431;&#x443;&#x43B;&#x430;&#x442;&#x43E;&#x432;, tg(x), David Barksdale,
62 Christian Fuchs, Nils Durner, Omar Tarabai, Maximilian Szengel, Supriti
63 Singh, lurchi, David Brodski, xrs, Fabian Oehlmann, Carlo von lynX,
64 Christophe Genevey Metat, Jeffrey Burdges, Safey A.Halim, Daniel Golle,
65 Phil, Bruno Cabral, Ji Lu, Heikki Lindholm, Markus Teich, t3sserakt,
66 Claudiu Olteanu, Marcello Stanisci, Moon, Hernani Marques, anryko, Arthur Dewarumez,
67 Julien Morvan, Adnan H, rexxnor, Lin Tong, Andreas Fuchs, Christian Rupp, jah,
68 Alejandra Morales, Bernd Fix, Feideus, Matthias Kolja Miehl, Andrew Cann, Antonio Ojea,
69 Pascal Mainini, amirouche and hark.
70 <a href="https://bugs.gnunet.org/view.php?id=5569">Special thanks</a> to Florian Weimer.
71</p>
72{% endblock body_content %}
diff --git a/template/news/2019-0.11.1.html.j2 b/template/news/2019-0.11.1.html.j2
new file mode 100644
index 00000000..82f27c85
--- /dev/null
+++ b/template/news/2019-0.11.1.html.j2
@@ -0,0 +1,55 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.1 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.1.
6 <br>
7 This is a bugfix release for 0.11.0, mostly fixing minor bugs, improving documentation and fixing various build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.1 release is still only suitable for early adopters with some reasonable pain tolerance.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.1.)
20</p>
21<p>
22 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>
23</p>
24<p>
25 Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
26</p>
27<h4>Noteworthy changes in 0.11.1</h4>
28<ul>
29 <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li>
30 <li>REST and GNS proxy configuration options for address binding were added</li>
31 <li>gnunet-publish by default no longer includes creation time</li>
32 <li>Unreliable message ordering logic in CADET was fixed</li>
33 <li>Various improvements to build system and documentation</li>
34</ul>
35<p>
36 The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312"> 14 individual issues</a> that were resolved since 0.11.0.
37</p>
38<h4>Known Issues</h4>
39<ul>
40 <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>
41 <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
42 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
43 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
44 <li>The RPS subsystem remains experimental.</li>
45 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
46</ul>
47<p>
48 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.
49</p>
50<h4>Thanks</h4>
51<p>
52 This release was the work of many people. The following people contributed code and were thus easily identified:
53 ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
54</p>
55{% endblock body_content %}
diff --git a/template/news/2019-0.11.2.html.j2 b/template/news/2019-0.11.2.html.j2
new file mode 100644
index 00000000..504a203c
--- /dev/null
+++ b/template/news/2019-0.11.2.html.j2
@@ -0,0 +1,55 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.2 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.2.
6<br>
7 This is a bugfix release for 0.11.0, mostly fixing minor bugs, improving documentation and fixing various build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.2 release is still only suitable for early adopters with some reasonable pain tolerance.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.2.)
20</p>
21<p>
22 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>
23</p>
24<p>
25 Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
26</p>
27<h4>Noteworthy changes in 0.11.2</h4>
28<ul>
29 <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li>
30 <li>REST and GNS proxy configuration options for address binding were added</li>
31 <li>gnunet-publish by default no longer includes creation time</li>
32 <li>Unreliable message ordering logic in CADET was fixed</li>
33 <li>Various improvements to build system and documentation</li>
34</ul>
35<p>
36 The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312">14 individual issues</a> that were resolved since 0.11.0.
37</p>
38<h4>Known Issues</h4>
39<ul>
40 <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>
41 <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
42 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
43 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
44 <li>The RPS subsystem remains experimental.</li>
45 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
46</ul>
47<p>
48 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.
49</p>
50<h4>Thanks</h4>
51<p>
52 This release was the work of many people. The following people contributed code and were thus easily identified:
53 ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
54</p>
55{% endblock body_content %}
diff --git a/template/news/2019-0.11.3.html.j2 b/template/news/2019-0.11.3.html.j2
new file mode 100644
index 00000000..50b207a1
--- /dev/null
+++ b/template/news/2019-0.11.3.html.j2
@@ -0,0 +1,52 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.3 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.3.
6<br>
7 This is a bugfix release for 0.11.2, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.3 release is still only suitable for early adopters with some reasonable pain tolerance.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.3.)
20</p>
21<p>
22 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>
23</p>
24<p>
25 Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
26</p>
27<h4>Noteworthy changes in 0.11.3 (since 0.11.2)</h4>
28<ul>
29 <li>gnunet-zoneimport now handles <tt>-h</tt> correctly</li>
30 <li><tt>iptables</tt> and other similar binaries are no longer hard-coded but detected at configure time (with hard-coded fallback locations).</li>
31 <li><tt>make uninstall</tt> now properly uninstalls all files</li>
32 <li>Passing the no longer available <tt>--with-nssdir</tt> configuration option now results in a hard error.</li>
33 <li><tt>GNUNET_memcmp()</tt> and <tt>GNUNET_is_zero()</tt> macros introduced for improved type safety (but not yet used consistently).</li>
34</ul>
35<h4>Known Issues</h4>
36<ul>
37 <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>
38 <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
39 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
40 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
41 <li>The RPS subsystem remains experimental.</li>
42 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
43</ul>
44<p>
45 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.
46</p>
47<h4>Thanks</h4>
48<p>
49 This release was the work of many people. The following people contributed code and were thus easily identified:
50 ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius B&#xFC;nger.
51</p>
52{% endblock body_content %}
diff --git a/template/news/2019-0.11.4.html.j2 b/template/news/2019-0.11.4.html.j2
new file mode 100644
index 00000000..9aad565f
--- /dev/null
+++ b/template/news/2019-0.11.4.html.j2
@@ -0,0 +1,50 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.4 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.4.
6<br>
7 This is a bugfix release for 0.11.3, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.4 release is still only suitable for early adopters with some reasonable pain tolerance.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.4.)
20</p>
21<p>
22 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>
23</p>
24<h4>Noteworthy changes in 0.11.4 (since 0.11.3)</h4>
25<ul>
26 <li><tt>gnunet-arm -s </tt> no longer logs into the console by default and instead into a logfile (in $GNUNET_HOME).</li>
27 <li>The reclaim subsystem is no longer experimental. See also <a href="https://reclaim-identity.io">re:claimID</a>. Further, the internal encryption scheme moved from ABE to GNS-style encryption.</li>
28 <li>GNUnet now depends on a more recent version of libmicrohttpd.</li>
29 <li>The REST API now includes read-only access to the configuration.</li>
30 <li>All manpages are now in mdocml format.</li>
31 <li><tt>gnunet-download-manager.scm</tt> removed.</li>
32</ul>
33<h4>Known Issues</h4>
34<ul>
35 <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>
36 <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
37 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
38 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
39 <li>The RPS subsystem remains experimental.</li>
40 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
41</ul>
42<p>
43 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.
44</p>
45<h4>Thanks</h4>
46<p>
47 This release was the work of many people. The following people contributed code and were thus easily identified:
48 ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius B&#xFC;nger.
49</p>
50{% endblock body_content %}
diff --git a/template/news/2019-0.11.5.html.j2 b/template/news/2019-0.11.5.html.j2
new file mode 100644
index 00000000..049aa8b5
--- /dev/null
+++ b/template/news/2019-0.11.5.html.j2
@@ -0,0 +1,47 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.5 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.5.
6<br>
7 This is a bugfix release for 0.11.4, mostly fixing a few minor bugs and improving performance, in particular for identity management with a large number of egos. In the wake of this release, we also launched the <a href="https://rest.gnunet.org">REST API documentation</a>. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.5 release is still only suitable for early adopters with some reasonable pain tolerance.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 gnunet-gtk saw some minor changes to adopt it to API changes in the main code related to the identity improvements. gnunet-fuse was not released again, as there were no changes and the 0.11.0 version is expected to continue to work fine with gnunet-0.11.5.
20</p>
21<p>
22 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>
23</p>
24<h4>Noteworthy changes in 0.11.5 (since 0.11.4)</h4>
25<ul>
26 <li><tt>gnunet-identity</tt> is much faster when creating or deleting egos given a large number of existing egos.</li>
27 <li>GNS now supports CAA records.</li>
28 <li>Documentation, comments and code quality was improved.</li>
29</ul>
30<h4>Known Issues</h4>
31<ul>
32 <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>
33 <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
34 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
35 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
36 <li>The RPS subsystem remains experimental.</li>
37 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
38</ul>
39<p>
40 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.
41</p>
42<h4>Thanks</h4>
43<p>
44 This release was the work of many people. The following people contributed code and were thus easily identified:
45 Christian Grothoff, Florian Dold, Marcello Stanisci, ng0, Martin Schanzenbach and Bernd Fix.
46</p>
47{% endblock body_content %}
diff --git a/template/news/2019-0.11.6.html.j2 b/template/news/2019-0.11.6.html.j2
new file mode 100644
index 00000000..3ee063b3
--- /dev/null
+++ b/template/news/2019-0.11.6.html.j2
@@ -0,0 +1,52 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.6 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.6.
6<br>
7 This is a bugfix release for 0.11.5, fixing a lot of minor bugs, improving stability and code quality. Further, our videos are back on the homepage. In this release, we again improved the webpage in general and updated our documentation. <i>As always:</i> 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 (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.6 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 gnunet-fuse was not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.6.
20</p>
21<p>
22 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>
23</p>
24<h4>Noteworthy changes in 0.11.6 (since 0.11.5)</h4>
25<ul>
26 <li><tt>gnunet-identity</tt> can now print private keys.</li>
27 <li>The <tt>REST</tt> service can be configured to echo the HTTP Origin header value for Cross-Origin-Resource-Sharing (CORS) when it is called by a browser plugin. Optionally, a CORS Origin to echo can be also be directly configured.</li>
28 <li><tt>re:claimID</tt> tickets are now re-used whenever possible.</li>
29 <li>SUID binary detection mechanisms implemented to improve compatiblity with some distributions.</li>
30 <li><tt>TRANSPORT</tt>, <tt>TESTBED</tt> and <tt>CADET</tt> tests now pass again on macOS.</li>
31 <li><tt>CADET</tt>: Replaced enum <tt>GNUNET_CADET_ChannelOption</tt> with <tt>GNUNET_MQ_PriorityPreferences</tt> in preparation of API changed in the future.</li>
32 <li>The GNS proxy Certification Authority is now generated using gnutls-certtool, if available, with opennssl/certtool as fallback.</li>
33 <li>Documentation, comments and code quality was improved.</li>
34</ul>
35<h4>Known Issues</h4>
36<ul>
37 <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>
38 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
39 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
40 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
41 <li>The RPS subsystem remains experimental.</li>
42 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
43</ul>
44<p>
45 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.
46</p>
47<h4>Thanks</h4>
48<p>
49 This release was the work of many people. The following people contributed code and were thus easily identified:
50 Martin Schanzenbach, Julius B&uuml;nger, ng0, Christian Grothoff, Alexia Pagkopoulou, rexxnor, xrs, lurchi and t3sserakt.
51</p>
52{% endblock body_content %}
diff --git a/template/news/2019-0.11.7.html.j2 b/template/news/2019-0.11.7.html.j2
new file mode 100644
index 00000000..f2b38231
--- /dev/null
+++ b/template/news/2019-0.11.7.html.j2
@@ -0,0 +1,56 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.7 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.7.
6<br>
7 This is a bugfix release for 0.11.6, fixing a lot of minor bugs, improving stability and code quality. Further, win32 support was removed for reasons you may read below. In this release, we again improved the webpage in general and updated our documentation. <i>As always:</i> 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 (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.7 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 gnunet-fuse is not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.7. The GPG key used to sign is: <tt>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</tt>
20</p>
21<p>
22 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>
23</p>
24<h4>Noteworthy changes in 0.11.7 (since 0.11.6)</h4>
25<ul>
26 <li><tt>ARM</tt>: GNUnet CLI tools are now able to detect if gnunet(-arm) is not running and will exit with a warning (before the command would just hang and wait for GNUnet to be started). #5906</li>
27 <li>win32 and mingw support were dropped, which resulted in a significant number of lines of code to be gone. The code has been unmaintained in our code base for many years and there are no known users. For details and further reasons refer to the discussion <a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-09/msg00002.html">in our archives</a>.</li>
28 <li>Removal of plibc, win32 and mingw support means you can now compile gnunet without requiring a Cxx compiler (you just need a C compiler). #5877</li>
29 <li><tt>REST</tt>: The new config endpoints can now be used to read and write the GNUnet config. #5808</li>
30 <li><tt>REST</tt>: The service is not started per user in multiuser setups.</li>
31 <li><tt>REST</tt>: Added tests for namestore and GNS. #5638</li>
32 <li><tt>re:claimID / OIDC</tt>: Now supports <a href="https://tools.ietf.org/html/rfc7636">PKCE</a>. #5807</li>
33 <li>SUID binary detection mechanisms implemented to improve compatiblity with some distributions.</li>
34 <li><tt>CREDENTIAL</tt> subsystem reworked and renamed to <tt>ABD</tt> (attribute-based delegation).</li>
35 <li><a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-10/msg00023.html">Minor TRANSPORT fixes</a> and <a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-10/msg00022.html">NAT changes</a>.</li>
36 <li><tt>GNS</tt> prepared code for <a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">LSD001 changes</a>. #5920</li>
37 <li>Documentation, comments and code quality was improved.</li>
38</ul>
39<h4>Known Issues</h4>
40<ul>
41 <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>
42 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
43 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
44 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
45 <li>The RPS subsystem remains experimental.</li>
46 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
47</ul>
48<p>
49 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.
50</p>
51<h4>Thanks</h4>
52<p>
53 This release was the work of many people. The following people contributed code and were thus easily identified:
54 Martin Schanzenbach, ng0, Christian Grothoff, Alexia Pagkopoulou, Andreas Ebner, Corvus Corax, xrs and t3sserakt.
55</p>
56{% endblock body_content %}
diff --git a/template/news/2019-0.11.8.html.j2 b/template/news/2019-0.11.8.html.j2
new file mode 100644
index 00000000..9a92eaac
--- /dev/null
+++ b/template/news/2019-0.11.8.html.j2
@@ -0,0 +1,47 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.11.8 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.11.8.
6<br>
7 This is a hotfix release for 0.11.7. <i>As always:</i> 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 (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.8 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
8</p>
9<h4>Download links</h4>
10<ul>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz</a></li>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz.sig</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz</a></li>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
17</ul>
18<p>
19 gnunet-fuse and gnunet-gtk were not released again, as there were no changes and the 0.11.0/0.11.7 versions are expected to continue to work fine with gnunet-0.11.8. The GPG key used to sign is: <tt>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</tt>
20</p>
21<p>
22 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>
23</p>
24<h4>Noteworthy changes in 0.11.8 (since 0.11.7)</h4>
25<ul>
26 <li><tt>GNS</tt> Portability fixes.</li>
27 <li><tt>PQ</tt>: Fixed build with postgresql plugin. (Regression introduces as part of #5733)</li>
28</ul>
29<h4>Known Issues</h4>
30<ul>
31 <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>
32 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
33 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
34 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
35 <li>The RPS subsystem remains experimental.</li>
36 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
37</ul>
38<p>
39 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.
40</p>
41
42<h4>Thanks</h4>
43<p>
44 This release was the work of many people. The following people contributed code and were thus easily identified:
45 ng0, Daniel Golle.
46</p>
47{% endblock body_content %}
diff --git a/template/news/2019-0.12.0.html.j2 b/template/news/2019-0.12.0.html.j2
new file mode 100644
index 00000000..6cf68160
--- /dev/null
+++ b/template/news/2019-0.12.0.html.j2
@@ -0,0 +1,85 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.12.0 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.12.0.
6<br>
7 This is a new major release. It breaks protocol compatibility with the 0.11.x versions.
8 Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
9 the 0.11.x GNUnet network, and interactions between old and new peers
10 will result in signature verification failures. 0.11.x peers will <b>NOT</b>
11 be able to communicate with Git master or 0.12.x peers.<br/>
12 In terms of usability, users should be aware that there are still
13 <b>a large number of known open issues</b> in particular with respect to ease
14 of use, but also some critical privacy issues especially for mobile users.
15 Also, the nascent network is tiny and thus unlikely to
16 provide good anonymity or extensive amounts of interesting information.
17 As a result, the 0.12.0 release is still <b>only suitable for early adopters
18 with some reasonable pain tolerance</b>.
19</p>
20<h4>Download links</h4>
21<ul>
22 <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>
23 <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>
24 <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>
25 <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>
26 <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>
27 <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>
28</ul>
29<p>
30 The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
31</p>
32<p>
33 Note that due to mirror synchronization, not all links might be functional
34 early after the release. For direct access try
35 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
36</p>
37<h4>Noteworthy changes in 0.12.0 (since 0.11.8)</h4>
38<ul>
39 <li><tt>GNS</tt>:
40 <ul>
41 <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>
42 <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>
43 <li>NSS plugin now properly handles non-standard IDNA names. <a href="https://bugs.gnunet.org/view.php?id=5927">#5927</a></li>
44 <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>
45 <li>Fixed BOX service/protocol label parsing (for TLSA et al)</li>
46 </ul>
47 </li>
48 <li><tt>GNS/NSE</tt>: Zone revocation proof of work algorithm changed to be less susceptible to specialized ASIC hardware.
49 <a href="https://bugs.gnunet.org/view.php?id=3795">#3795</a></li>
50 <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
51 <li><tt>UTIL</tt>:
52 <ul>
53 <li>Improved and documented RSA binary format. <a href="https://bugs.gnunet.org/view.php?id=5968">#5968</a></li>
54 <li>Removed redundant hashing in EdDSA signatures. <a href="https://bugs.gnunet.org/view.php?id=5398">#5398</a></li>
55 <li>The <tt>gnunet-logread</tt> script for log auditing (requires perl) can now be installed.</li>
56 <li>Now using <a href="https://tweetnacl.cr.yp.to/">TweetNaCl</a> for ECDH implementation.</li>
57 </ul>
58 </li>
59 <li><tt>Buildsystem</tt>: A significant number of build system issued have been fixed and improvements implemented, including:
60 <ul>
61 <li>GLPK dependency dropped.</li>
62 <li>Fixed guix package definition.</li>
63 </ul>
64 </li>
65 <li><tt>Documentation</tt>: Improvements to the handbook and documentation.</li>
66</ul>
67<h4>Known Issues</h4>
68<ul>
69 <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>
70 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
71 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
72 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
73 <li>The RPS subsystem remains experimental.</li>
74 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
75</ul>
76<p>
77 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.
78</p>
79
80<h4>Thanks</h4>
81<p>
82 This release was the work of many people. The following people contributed code and were thus easily identified:
83 ng0, Christian Grothoff, Florian Dold, xrs, Naomi Phillips and Martin Schanzenbach.
84</p>
85{% endblock body_content %}
diff --git a/template/news/2019-0.12.1.html.j2 b/template/news/2019-0.12.1.html.j2
new file mode 100644
index 00000000..7911fcd1
--- /dev/null
+++ b/template/news/2019-0.12.1.html.j2
@@ -0,0 +1,26 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.12.1 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.12.1.
6<br>
7 This is a very minor release. It largely fixes one function that is
8 needed by GNU Taler 0.6.0. Please read the release notes
9 for GNUnet 0.12.0, as they still apply. Updating is only recommended
10 for those using GNUnet in combination with GNU Taler.
11</p>
12<h4>Download links</h4>
13<ul>
14 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz</a></li>
15 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz.sig</a></li>
16</ul>
17<p>
18 The GPG key used to sign is: <tt>D8423BCB326C7907033929C7939E6BE1E29FC3CC</tt>
19</p>
20<p>
21 Note that due to mirror synchronization, not all links might be functional
22 early after the release. For direct access try
23 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
24</p>
25
26{% endblock body_content %}
diff --git a/template/news/2019-02.html.j2 b/template/news/2019-02.html.j2
new file mode 100644
index 00000000..0925eb75
--- /dev/null
+++ b/template/news/2019-02.html.j2
@@ -0,0 +1,75 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>2019-02: Topics for GSoC 2019</h1>
4<p>
5 GNUnet is participating in the Google Summer of Code again through GNU. If you are interested in any of these projects, reach out to us!
6</p>
7<section>
8 <h4>Android Port</h4>
9 <p>
10 It is time for GNUnet to run properly on Android. Note that GNUnet is written in C, and this is not about rewriting GNUnet in Java, but about getting the C code to run on Android.<br>
11 Mentor: <a href="https://www.goebel-consult.de/">Hartmut Goebel</a>
12 </p>
13</section>
14
15<section>
16 <h4>Help with Continuous Integration setup</h4>
17 <p>
18 There is a push for migrating our CI to Gitlab. The CI should eventually not just run "make check" on various platforms, but also perform tests with multiple peers running in different VMs with specific network topologies (i.e. NAT) between them being simulated. The CI should also be integrated with Gauger for performance regression analysis. Running jobs only when dependencies have changed and scripting more granular triggers or ideally automatic dependency discovery (as done by the autotools) is also important.<br>
19 Mentor: TBD
20 </p>
21</section>
22
23<section>
24 <h4>Migrate gnunet-qr from Python 2.7 to C using libzbar</h4>
25 <p>
26 Python 2.7 is reaching its end-of-life, and we want to get rid of the dependency on Python. The existing gnunet-qr tool is a rather simple wrapper around python-zbar, which itself wraps libzbar. The goal of this project is to directly use libzbar to scan QR codes for GNUnet / the GNU Name System (see also <a href="https://bugs.gnunet.org/view.php?id=5562">#5562</a>).<br>
27 Mentor: Christian Grothoff
28 </p>
29</section>
30
31<section>
32 <h4>re:claimID OpenID Connect performance improvements</h4>
33 <p>
34 reclaimID is a decentralized identity system build on top of the GNU Name System. Upon authorization, the user provides a requesting party (RP) such as a website with an authorization ticket (e.g. piggybacked in an OpenID authorization code). The RP uses information contained in this ticket to
35 </p>
36 <ol>
37 <li> Retrieve the decryption key from GNS</li>
38 <li> Retrieve the user attributes from GNS</li>
39 </ol>
40 <p>
41 The GNS lookups ensure that the RP receives up-to-date attributes and functional decryption keys. However, in particular the RP-specific encryption key resolution can be slow and even fail depending on the network topology. We propose that in an initial exchange, in particular OpenID authorization code flows, we try to incorporate key and maybe even an attribute set in the ticket exchange. In order to mitigate this issue, this project is meant to investigate and implement how...
42 </p>
43 <ol>
44 <li> ... decryption keys can be added to an initial exchange in OpenID.</li>
45 <li> ... initial set(s) of attributes can be piggybacked in OpenID.</li>
46 </ol>
47 <p>
48 Mentor: Martin Schanzenbach
49 </p>
50</section>
51
52<section>
53 <h4>re:claimID alternative GNS-based encryption</h4>
54 <p>
55 re:claimID is a decentralized identity system build on top of the GNU Name System. The initial design and implementation of re:claimID includes an attribute-based encryption module in order to prevent unauthorized access to attributes in the name system. Our motivation for re:claimID was for it to be name system agnostic, which means the design theoretically also works for other name systems such as namecoin. Other name systems often do not have built-in mechanisms in order to do this. Hence, we implemented an ABE access control layer. Our ABE implementation requires two third party libraries: libpbc and libgabe. While we could merge libgabe into the gnunet service implementation of re:claimID, libpbc is a rather large, third party library which lacks packaging in distributions and for platforms. On the other hand, GNS supports record data encryption using symmetric keys as labels. If we make the access control layer of re:claimID more generic in order to support both ABE and GNS encryption, we could reduce the required depenencies. This would result in gnunet packages to include re:claimID by default. In short, the goals are to...
56 </p>
57 <ol>
58 <li> ... improve performance by reducing encryption overhead.</li>
59 <li> ... reduce dependencies.</li>
60 </ol>
61 <p>
62 Mentor: Martin Schanzenbach
63 </p>
64</section>
65
66<section>
67 <h4>Enable all networking applications to run over GNUnet out of the box</h4>
68 <p>
69 One great problem of the current Internet is the lack of disintermediation. When people want to talk they need a chat service. When they want to share files they need a file transfer service. Although GNUnet already possesses quite advanced integration into Linux networking, a little extra work is needed for existing applications like irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. Once people have added a person to their GNS they can immediately message, exchange files and suchlike directly, with nothing but the GNUnet in the middle, using applications that have been distributed with unix systems ever since the 1980&#39;s. We can produce an OS distribution where these things work out of the box with the nicknames of people instead of cloud services. For more information and context, read <a href="https://bugs.gnunet.org/view.php?id=4625">bug id 4625</a>.
70 </p>
71 <p>
72 Mentors: lynX &amp; dvn
73 </p>
74</section>
75{% endblock body_content %}
diff --git a/template/news/2019-06-DSTJ.html.j2 b/template/news/2019-06-DSTJ.html.j2
new file mode 100644
index 00000000..0d1d3c67
--- /dev/null
+++ b/template/news/2019-06-DSTJ.html.j2
@@ -0,0 +1,14 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>Peer DSTJ is dead, long live peer Y924</h1>
4<p>
5 After some issues with our infrastructure we needed to replace our bootstrapping peer. To avoid problems when connecting to GNUnet the operator of a peer needs to update its node by removing the peer ID <i>DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</i> from the system. Here are two strategies to find copies of the respective file:
6</p>
7<ol>
8 <li><tt>$ locate DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</tt></li>
9 <li><tt>$ find / -name DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</tt></li>
10</ol>
11<p>
12 Update: DSTJ has now been blacklisted. Please update your GNUnet peer.
13</p>
14{% endblock body_content %}
diff --git a/template/news/2019-06.html.j2 b/template/news/2019-06.html.j2
new file mode 100644
index 00000000..295138b9
--- /dev/null
+++ b/template/news/2019-06.html.j2
@@ -0,0 +1,7 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet Hacker Meeting 2019 at La D&#233;centrale, Switzerland</h1>
4 <p>
5 The members of the GNUnet community met again in the wonderful souroundings of St. Imier to hack on GNUnet. New people joined our sessions until late at night. From bug squashing to digging our own dog food, from workshops to theoretical discussions of new services and usecases. And of course, pizza was in the game.
6 </p>
7{% endblock body_content %}
diff --git a/template/news/2019-07-GHM_Aug_2019.html.j2 b/template/news/2019-07-GHM_Aug_2019.html.j2
new file mode 100644
index 00000000..c846432e
--- /dev/null
+++ b/template/news/2019-07-GHM_Aug_2019.html.j2
@@ -0,0 +1,7 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet Hacker Meeting in August 2019 at Wernsdort (near Berlin)</h1>
4 <p>
5 In August 2019, some of us met in Wernsdorf for focused work on GNUnet.
6 </p>
7{% endblock body_content %}
diff --git a/template/news/2019-10-GNSSpec1.html.j2 b/template/news/2019-10-GNSSpec1.html.j2
new file mode 100644
index 00000000..3941c162
--- /dev/null
+++ b/template/news/2019-10-GNSSpec1.html.j2
@@ -0,0 +1,19 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNS Technical Specification Milestone 1/4</h1>
4<p>
5 We are happy to announce the completion of the first milestone for the GNS Specification. The objective is to provide a detailed and comprehensive guide for implementors of the GNU Name System. The initial milestone consists of documenting the cryptographic principles of GNS data structures. This includes the specification of the GNS record wire and serialization formats as well as internationalization.<br>
6 <i>NOTE: The currently specified protocol is planned to be implemented for GNUnet 0.12. The current GNS implementation (0.11) exhibits minor but compatibility breaking deviations from this specification.</i> The draft specification <b>LSD001</b> can be found at:
7</p>
8<ul>
9 <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
10 <li><a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">Link to TXT version</a></li>
11 <li><a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.html">Link to HTML version</a></li>
12</ul>
13<p>
14 The next milestone will bring the resolver logic specification.
15</p>
16<p>
17 This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
18</p>
19{% endblock body_content %}
diff --git a/template/news/2019-10-ICANNPanel.html.j2 b/template/news/2019-10-ICANNPanel.html.j2
new file mode 100644
index 00000000..08885fa6
--- /dev/null
+++ b/template/news/2019-10-ICANNPanel.html.j2
@@ -0,0 +1,13 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet project invited to ICANN66</h1>
4<p>
5 We are delighted to announce that ICANN has invited the GNUnet project to speak at the <a href="https://meetings.icann.org/en/montreal66">next ICANN Annual General Meeting</a>. We have been invited to join a panel discussion on <i>Emerging Internet Identifier Technologies</i> in order to share our ideas and work on the <i>GNU Name System (GNS)</i>. ICANN generously offered to cover travel and accomodation.
6</p>
7<p>
8 The meeting will take place in Montreal between 2 - 7 November. The panel will tentatively be help on November 6th.
9</p>
10<p>
11 <b>UPDATE:</b> The panel is on Tueday, November 5th 13:30 EDT with the possibility of remote participation: <a href="https://66.schedule.icann.org/meetings/1116895">Link</a>
12</p>
13{% endblock body_content %}
diff --git a/template/news/2019-11-ICANNUpdate.html.j2 b/template/news/2019-11-ICANNUpdate.html.j2
new file mode 100644
index 00000000..1edbbb8c
--- /dev/null
+++ b/template/news/2019-11-ICANNUpdate.html.j2
@@ -0,0 +1,10 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNS&#64;ICANN66</h1>
4<p>
5 The <a href="https://meetings.icann.org/en/montreal66">ICANN Annual General Meeting</a> is concluded. We were invited to join a panel discussion on <i>Emerging Internet Identifier Technologies</i> in order to share our ideas and work on the <i>GNU Name System (GNS)</i>.
6</p>
7<p>
8 You can find the presentation on GNS in <a href="{{ url_localized('video.html') }}">our video section</a>. The handshake.org project, which proposes a decentralized, blockchain-based governance of the root zone (as opposed to governance by ICANN), joined us on the panel. The full video including questions and answers can be found <a href="https://icann.zoom.us/recording/share/M8N-Duq935XheIZoBedIwmi3VqRUAe2iOPwECiTNLxKwIumekTziMw?startTime=1572978711000">here</a>.
9</p>
10{% endblock body_content %}
diff --git a/template/news/2019-12-UpcomingTalks.html.j2 b/template/news/2019-12-UpcomingTalks.html.j2
new file mode 100644
index 00000000..b92d1cdd
--- /dev/null
+++ b/template/news/2019-12-UpcomingTalks.html.j2
@@ -0,0 +1,73 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>Upcoming GNUnet Talks</h1>
4 <p>There will be various talks in the next few months on GNUnet and related
5 projects on both the Chaos Communication Congress (36C3) as well as FOSDEM.
6 Here is an overview:
7 </p>
8 <h2>Privacy and Decentralization @ 36c3 (YBTI)</h2>
9 <p>
10 We are pleased to have 5 talks to present as part of our
11 "youbroketheinternet/wefixthenet" session, taking place on the
12 <a href="https://oio.social/">OIO (Open
13 Infrastructure Orbit)</a> stage:
14 </p>
15
16 <ul>
17 <li>
18 "re:claimID - Self-sovereign, Decentralised Identity Management and
19 Personal Data Sharing" by Hendrik Meyer zum Felde
20 will take place at 2019-12-27 18:30 in OIO Stage.
21 <a href="https://talks.oio.social/36c3-oio/talk/XHLTUD/">Info</a>
22 </li>
23 <li>
24 "Buying Snacks via NFC with GNU Taler" by Dominik Hofer
25 will take place at 2019-12-27 21:20 in OIO Stage
26 <a href="https://talks.oio.social/36c3-oio/talk/MMB78C/">Info</a>
27 </li>
28 <li>
29 "CloudCalypse 2: Social network with net2o" by Bernd Paysan
30 will take place at 2019-12-28 21:20 in OIO Stage
31 <a href="https://talks.oio.social/36c3-oio/talk/GUZH7V/">Info</a>
32 </li>
33 <li>
34 "Delta Chat: e-mail based messaging, the Rustocalypse and UX driven
35 approach" by holger krekel
36 will take place at 2019-12-29 17:40 in OIO Stage
37 <a href="https://talks.oio.social/36c3-oio/talk/WSLWVM/">Info</a>
38 </li>
39 <li>
40 "Cryptography of Killing Proof-of-Work" by Jeff Burdges
41 will take place at 2019-12-30 12:00 in OIO Stage
42 <a href="https://talks.oio.social/36c3-oio/talk/GGV8G3/">Info</a>
43 </li>
44 </ul>
45
46 <p>
47 In addition to these talks, we will be hosting a snack machine which
48 accepts <a href="https://taler.net">Taler</a> for payment.
49 The first of its kind! It will be filled
50 with various goodies, including Swiss chocolates, books, and electronics.
51 The machine will be located somewhere in the OIO assembly, and there
52 will be a station at which you may exchange Euro for digital Euro for
53 immediate use.
54 We welcome all to come try it out. :)
55 </p>
56 <h2>Decentralized Internet and Privacy devroom @FOSDEM 2020</h2>
57 <p>
58 We have 2 GNUnet-related talks at the
59 <a href="https://fosdem.org/2020/schedule/track/decentralized_internet_and_privacy/">
60 Decentralized Internet and Privacy devroom</a> at FOSDEM 2020 in February:
61 </p>
62 <ul>
63 <li>
64 GNUnet: A network protocol stack for building secure, distributed, and
65 privacy-preserving applications
66 <a href="https://fosdem.org/2020/schedule/event/dip_gnunet/">Info</a>
67 </li>
68 <li>
69 Knocking Down the Nest: secushareBOX - p2p, encrypted IoT and beyond...
70 <a href="https://fosdem.org/2020/schedule/event/dip_secusharebox/">Info</a>
71 </li>
72 </ul>
73{% endblock body_content %}
diff --git a/template/news/2020-01-0.12.2.html.j2 b/template/news/2020-01-0.12.2.html.j2
new file mode 100644
index 00000000..21375aa6
--- /dev/null
+++ b/template/news/2020-01-0.12.2.html.j2
@@ -0,0 +1,71 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.12.2 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.12.2.
6<br>
7 This is a new bugfix release.
8 In terms of usability, users should be aware that there are still
9 <b>a large number of known open issues</b> in particular with respect to ease
10 of use, but also some critical privacy issues especially for mobile users.
11 Also, the nascent network is tiny and thus unlikely to
12 provide good anonymity or extensive amounts of interesting information.
13 As a result, the 0.12.2 release is still <b>only suitable for early adopters
14 with some reasonable pain tolerance</b>.
15</p>
16<h4>Download links</h4>
17<ul>
18 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz</a></li>
19 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz.sig</a></li>
20 <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>
21 <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>
22 <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>
23 <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>
24</ul>
25<p>
26 The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
27</p>
28<p>
29 Note that due to mirror synchronization, not all links might be functional
30 early after the release. For direct access try
31 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
32</p>
33<h4>Noteworthy changes in 0.12.2 (since 0.12.1)</h4>
34<ul>
35 <li>
36 <tt>GNS</tt>: Resolver clients are now able to specify a recursion depth limit.
37 </li>
38 <li>
39 <tt>TRANSPORT/TNG</tt>: The transport rewrite (aka TNG) is underway and
40 various transport components have been worked on, including TCP, UDP and UDS
41 communicators.
42 </li>
43 <li>
44 <tt>RECLAIM</tt>: Added preliminary support for third party attested
45 credentials.
46 </li>
47 <li>
48 <tt>UTIL</tt>: The cryptographic changes introduced in 0.12.0 broke ECDSA
49 ECDH and consequently other components. The offending ECDSA key normalization
50 was dropped.
51 </li>
52</ul>
53<h4>Known Issues</h4>
54<ul>
55 <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>
56 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
57 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
58 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
59 <li>The RPS subsystem remains experimental.</li>
60 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
61</ul>
62<p>
63 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.
64</p>
65
66<h4>Thanks</h4>
67<p>
68 This release was the work of many people. The following people contributed code and were thus easily identified:
69 Christian Grothoff, Florian Dold, Christian Ulrich, dvn, lynx and Martin Schanzenbach.
70</p>
71{% endblock body_content %}
diff --git a/template/news/2020-01-GNSSpec2.html.j2 b/template/news/2020-01-GNSSpec2.html.j2
new file mode 100644
index 00000000..e673d35d
--- /dev/null
+++ b/template/news/2020-01-GNSSpec2.html.j2
@@ -0,0 +1,28 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNS Technical Specification Milestone 2/4</h1>
4<p>
5 We are happy to announce the completion of the second milestone for the GNS
6 Specification. The second milestone consists of documenting the GNS name
7 resolution process and record handling.<br>
8 With the release of GNUnet 0.12.x, the currently specified protocol is
9 implemented according to the specification. As before, the draft specification
10 <b>LSD001</b> can be found at:
11</p>
12<ul>
13 <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
14 <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
15 <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
16</ul>
17<p>
18 As already announced on the <a href="https://lists.gnu.org/archive/html/gnunet-developers/2020-01/msg00000.html">mailing list</a>,
19 the Go implementation of GNS is also proceeding as planned and implements the
20 specification.
21</p>
22<p>
23 The next and third milestone will cover namespace revocation.
24</p>
25<p>
26 This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
27</p>
28{% endblock body_content %}
diff --git a/template/news/2020-05-GHM_Jun_2020.html.j2 b/template/news/2020-05-GHM_Jun_2020.html.j2
new file mode 100644
index 00000000..f270d87d
--- /dev/null
+++ b/template/news/2020-05-GHM_Jun_2020.html.j2
@@ -0,0 +1,8 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>Online GNUnet Hacker Meeting in June 2020</h1>
4 <p>
5 We are happy to announce that we will have a GNUnet
6 Hacker Meeting from 17-21 of June 2020 taking place online. For more information see <a href="https://md.hasi.it/s/gnunet">here</a>.
7 </p>
8{% endblock body_content %}
diff --git a/template/news/2020-06-GNSSpec3.html.j2 b/template/news/2020-06-GNSSpec3.html.j2
new file mode 100644
index 00000000..2e69ccb9
--- /dev/null
+++ b/template/news/2020-06-GNSSpec3.html.j2
@@ -0,0 +1,25 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNS Technical Specification Milestone 3/4</h1>
4<p>
5 We are happy to announce the completion of the third milestone for the GNS
6 Specification. The third milestone consists of documenting the GNS zone
7 revocation process. As part of this, we have reworked the proof-of-work
8 algorithms in GNUnet also used for GNS revocations.<br>
9 The (protocol breaking) changes will be released as part of GNUnet 0.13.0.
10 The specification document <b>LSD001</b> can be found at:
11</p>
12<ul>
13 <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
14 <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
15 <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
16</ul>
17<p>
18 In preparation for the fourth and last milestone, we have started the
19 <a href="https://mailarchive.ietf.org/arch/msg/secdispatch/Kj8zXoQssiFLp8bM5l5n1OtXt7s/">IETF process to find a working group</a> and expect to present our
20 work initially at <a href="https://ietf.org/how/meetings/108/">IETF 108</a>.
21</p>
22<p>
23 This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
24</p>
25{% endblock body_content %}
diff --git a/template/news/2020-07-0.13.0.html.j2 b/template/news/2020-07-0.13.0.html.j2
new file mode 100644
index 00000000..ef8c0d89
--- /dev/null
+++ b/template/news/2020-07-0.13.0.html.j2
@@ -0,0 +1,103 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.13.0 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.13.0.
6<br>
7 This is a new major release. It breaks protocol compatibility with the 0.12.x versions.
8 Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
9 the 0.12.x GNUnet network, and interactions between old and new peers
10 will result in signature verification failures. 0.12.x peers will <b>NOT</b>
11 be able to communicate with Git master or 0.13.x peers.<br/>
12 In terms of usability, users should be aware that there are still
13 <b>a large number of known open issues</b> in particular with respect to ease
14 of use, but also some critical privacy issues especially for mobile users.
15 Also, the nascent network is tiny and thus unlikely to
16 provide good anonymity or extensive amounts of interesting information.
17 As a result, the 0.13.0 release is still <b>only suitable for early adopters
18 with some reasonable pain tolerance</b>.
19</p>
20<h4>Download links</h4>
21<ul>
22 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz</a></li>
23 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz.sig</a></li>
24 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz</a></li>
25 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz.sig</a></li>
26 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz</a></li>
27 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz.sig</a></li>
28</ul>
29<p>
30 The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
31</p>
32<p>
33 Note that due to mirror synchronization, not all links might be functional
34 early after the release. For direct access try
35 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
36</p>
37<h4>Noteworthy changes in 0.13.0 (since 0.12.2)</h4>
38<ul>
39 <li><tt>GNS</tt>:
40 <ul>
41 <li>Aligned with specification <a href="https://lsd.gnunet.org/lsd0001/">LSD001</a>.
42 <li>NSS plugin "block" fixed. <a href="https://bugs.gnunet.org/view.php?id=5782">#5782</a></li>
43 <li>Broken set NICK API removed.<a href="https://bugs.gnunet.org/view.php?id=6092">#6092</a></li>
44 <li>New record flags: SUPPLEMENTAL. Records which are not explicitly
45 configured/published under a specific label but which are still
46 informational are returned by the resolver and flagged accordingly. <a href="https://bugs.gnunet.org/view.php?id=6103">#6103</a></li>
47 <li><tt>gnunet-namestore</tt> now complains when adding TLSA or SRV records outside of a BOX</li>
48 </ul>
49 </li>
50 <li>
51 <tt>CADET</tt>: Fixed tunnel establishment as well as an outstanding bug regarding tunnel destruction. <a href="https://bugs.gnunet.org/view.php?id=5822">#5822</a>
52 </li>
53 <li><tt>GNS/REVOCATION</tt>: Revocation proof of work has function changed to
54 argon2 and modified to reduce variance.</li>
55 <li><tt>RECLAIM</tt>: Increased ticket length to 256 bit. <a href="https://bugs.gnunet.org/view.php?id=6047">#6047</a></li>
56 <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
57 <li><tt>UTIL</tt>:
58 <ul>
59 <li>Serialization / file format of ECDSA private keys harmonized with
60 other libraries. Old private keys will no longer work! <a href="https://bugs.gnunet.org/view.php?id=6070">#6070</a></li>
61 <li>Now using <a href="https://doc.libsodium.org/">libsodium</a> for EC
62 cryptography.</li>
63 <li>Builds against cURL which is not linked against gnutls are now possible but still not recommended.
64 Configure will warn that this will impede the GNS functionality. This change will make hostlist discovery
65 work more reliable for some distributions.</li>
66 <li><tt>GNUNET_free_non_null</tt> removed. <tt>GNUNET_free</tt> changed to not assert that the pointer is not NULL.
67 For reference see the <a href="https://taler.net/papers/codeblau-report-2020-q2.pdf">Taler security audit</a>.</li>
68 <li>AGPL request handlers added GNUnet and extension templates.</li>
69 </ul>
70 </li>
71 <li><b>(NEW) </b><tt>GANA Registry</tt>: We have established a registry to be used for names and numbers in GNUnet.
72 This includes constants for protocols including GNS record types and GNUnet peer-to-peer messages. See <a href="https://gana.gnunet.org">GANA</a>.</li>
73 <li><b>(NEW) </b><tt>Living Standards</tt>: LSD subdomain and LSD0001 website: <a href="https://lsd.gnunet.org/lsd0001">LSD0001</a></li>
74 <li><b>(NEW) </b><tt>Continuous integration</tt>: <a href="https://buildbot.gnunet.org">Buildbot</a> is back.</li>
75 <li><tt>Buildsystem</tt>: A significant number of build system changes:
76 <ul>
77 <li>libmicrohttpd and libjansson are now required dependencies.</li>
78 <li>New dependency: <a href="https://doc.libsodium.org/">libsodium</a>.</li>
79 <li>Fixed an issue with libidn(2) detection.</tt>
80 </ul>
81 </li>
82</ul>
83A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
84the <a href="https://bugs.gnunet.org/roadmap_page.php?version_id=338">0.13.0 bugtracker</a>.
85<h4>Known Issues</h4>
86<ul>
87 <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>
88 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
89 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
90 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
91 <li>The RPS subsystem remains experimental.</li>
92 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
93</ul>
94<p>
95 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.
96</p>
97
98<h4>Thanks</h4>
99<p>
100 This release was the work of many people. The following people contributed code and were thus easily identified:
101 Christian Grothoff, Florian Dold, Jonathan Buchanan, t3sserakt, nikita and Martin Schanzenbach.
102</p>
103{% endblock body_content %}
diff --git a/template/news/2020-07-0.13.1.html.j2 b/template/news/2020-07-0.13.1.html.j2
new file mode 100644
index 00000000..b7670242
--- /dev/null
+++ b/template/news/2020-07-0.13.1.html.j2
@@ -0,0 +1,29 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.13.1 released</h1>
4<p>
5 This is a bugfix release for gnunet and gnunet-gtk specifically.
6 <br>
7 For gnunet, no changes to the source have been made. However,
8 the default configuration had to be modified to support the changes
9 made in 0.13.0.
10 <br>
11 For gnunet-gtk, this fixes a more serious issue where the
12 0.13.0 tarball failed to build.
13</p>
14<h4>Download links</h4>
15<ul>
16 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz</a></li>
17 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz.sig</a></li>
18 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz</a></li>
19 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz.sig</a></li>
20</ul>
21<p>
22 The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
23</p>
24<p>
25 Note that due to mirror synchronization, not all links might be functional
26 early after the release. For direct access try
27 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
28</p>
29{% endblock body_content %}
diff --git a/template/news/2020-08-0.13.2.html.j2 b/template/news/2020-08-0.13.2.html.j2
new file mode 100644
index 00000000..3dfa7e61
--- /dev/null
+++ b/template/news/2020-08-0.13.2.html.j2
@@ -0,0 +1,58 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3<h1>GNUnet 0.13.2 released</h1>
4<p>
5 This is a bugfix release for gnunet 0.13.1.<br/>
6 It fixes some build issues and contains changes to the REST API
7 implmementation (no change in the API itself) as well as OpenID Connect related
8 fixes to re:claimID.
9</p>
10<h4>Download links</h4>
11<ul>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz.sig</a></li>
14</ul>
15<p>
16 The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
17</p>
18<p>
19 Note that due to mirror synchronization, not all links might be functional
20 early after the release. For direct access try
21 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
22</p>
23<h4>Noteworthy changes in 0.13.2 (since 0.13.1)</h4>
24<ul>
25 <li><tt>REST</tt>:
26 <ul>
27 <li>Plugins may now handle any namespace. <a href="https://bugs.gnunet.org/view.php?id=6462">#6462</a></li>
28 <li>Fixed incomplete/missing cleanup and teardown of REST plugins.</li>
29 </ul>
30 </li>
31 <li><tt>RECLAIM</tt>:
32 <ul>
33 <li>Support for <tt>/.well-known/openid-configuration</tt>. <a href="https://bugs.gnunet.org/view.php?id=6463">#6463</a></li>
34 <li>Support for standard scope values (<tt>profile, address, email, phone</tt>) and corresponding mapping to standard claim values</li>
35 <li>Correct processing of <tt>claims</tt> parameter for individual claim requests.</li>
36 <li>Support for <tt>POST</tt> token request.</li>
37 <li>Support for public clients (Token request without client secrets).</li>
38 <li>Fixed urlencoding of parameters on redirect</li>
39 </ul>
40 </li>
41 <li><tt>UTIL</tt>: New string API for percent-encode/decode.</li>
42 <li><tt>MYSQL</tt>: Fix version detection and build against mysql-8 and later. <a href="https://bugs.gnunet.org/view.php?id=6465">#6465</a></li>
43 <li><tt>POSTGRESQL</tt>: Ensure postgresql fails hard if there is an error in the SQL. <a href="https://bugs.gnunet.org/view.php?id=6437">#6437</a></li>
44 <li><tt>Extensions</tt>:
45 <ul>
46 <li>Load GNSRECORD plugins within GNUnet's context.</li>
47 <li>Add convenience function to return GNUnet's default configuration.</li>
48 </ul>
49 </li>
50</ul>
51
52<h4>Thanks</h4>
53<p>
54 This release was the work of many people. The following people contributed code and were thus easily identified:
55 Christian Grothoff, Florian Dold, Alessio Vanni, t3sserakt, Martin Schanzenbach.
56</p>
57
58{% endblock body_content %}
diff --git a/template/news/2020-09-0.13.3.html.j2 b/template/news/2020-09-0.13.3.html.j2
new file mode 100644
index 00000000..dc9440c3
--- /dev/null
+++ b/template/news/2020-09-0.13.3.html.j2
@@ -0,0 +1,51 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3<h1>GNUnet 0.13.3 released</h1>
4<p>
5 Continuing to "release early / release often", we present
6 GNUnet 0.13.3. This is a bugfix release for gnunet 0.13.2.<br/>
7 It fixes some build issues and contains major changes to
8 the re:claimID API.
9</p>
10<h4>Download links</h4>
11<ul>
12 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz</a></li>
13 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz.sig</a></li>
14</ul>
15<p>
16 The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
17</p>
18<p>
19 Note that due to mirror synchronization, not all links might be functional
20 early after the release. For direct access try
21 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
22</p>
23<h4>Noteworthy changes in 0.13.3 (since 0.13.2)</h4>
24<ul>
25 <li><tt>REST</tt>:
26 <ul>
27 <li>re:claimID attestation API change reflected in endpoint naming.</li>
28 <li>Fix regression in <tt>NAMESTORE</tt> REST API endpoint processing.</li>
29 </ul>
30 </li>
31 <li><tt>RECLAIM</tt>:
32 "Attestations" renamed to "Credentials". Credentials are now converted to "Presentations" when a ticket is issued in preparation
33 for <a href="https://www.w3.org/TR/vc-data-model/">DID-style VCs</a> and Privacy-ABCs.
34 </li>
35 <li><tt>UTIL</tt>: Fix <tt>gnunet-qr</tt> device parameter.</li>
36 <li><tt>SET</tt>: Separated into set intersection (SETI) and set union subsystems (SETU).</a></li>
37 <li><tt>BUILD</tt>:
38 <ul>
39 <li>Fix build on OpenBSD.</li>
40 <li>Correctly check for required libsodium version. <a href="https://bugs.gnunet.org/view.php?id=6506">#6506</a></li>
41 </ul>
42 </li>
43</ul>
44
45<h4>Thanks</h4>
46<p>
47 This release was the work of many people. The following people contributed code and were thus easily identified:
48 Christian Grothoff, Jonathan Buchanan, Johannes Späth and Martin Schanzenbach.
49</p>
50
51{% endblock body_content %}
diff --git a/template/news/2020-11-0.14.0.html.j2 b/template/news/2020-11-0.14.0.html.j2
new file mode 100644
index 00000000..853b4548
--- /dev/null
+++ b/template/news/2020-11-0.14.0.html.j2
@@ -0,0 +1,81 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNUnet 0.14.0 released</h1>
4<p>
5 We are pleased to announce the release of GNUnet 0.14.0.
6<br>
7 This is a new major release. It breaks protocol compatibility with the 0.13.x versions.
8 Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
9 the 0.13.x GNUnet network, and interactions between old and new peers
10 will result in issues. 0.13.x peers will be able to communicate with Git
11 master or 0.13.x peers, but some services - in particular GNS - will not be compatible.<br/>
12 In terms of usability, users should be aware that there are still
13 <b>a large number of known open issues</b> in particular with respect to ease
14 of use, but also some critical privacy issues especially for mobile users.
15 Also, the nascent network is tiny and thus unlikely to
16 provide good anonymity or extensive amounts of interesting information.
17 As a result, the 0.14.0 release is still <b>only suitable for early adopters
18 with some reasonable pain tolerance</b>.
19</p>
20<h4>Download links</h4>
21<ul>
22 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz</a></li>
23 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz.sig</a></li>
24 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz</a></li>
25 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz.sig</a></li>
26 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz</a></li>
27 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz.sig</a></li>
28</ul>
29<p>
30 The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
31</p>
32<p>
33 Note that due to mirror synchronization, not all links might be functional
34 early after the release. For direct access try
35 <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
36</p>
37<h4>Noteworthy changes in 0.14.0 (since 0.13.3)</h4>
38<ul>
39 <li><tt>GNS</tt>:
40 <ul>
41 <li>Aligned with specification <a href="https://lsd.gnunet.org/lsd0001/">LSD001</a>.
42 <li>Crypto agility: The GNS protocol now supports other zone types besides ECDSA-based PKEYs.
43 However, the alternative EdDSA-based EDKEY crypto is not yet implemented. <a href="https://bugs.gnunet.org/view.php?id=6485">#6485</a></li>
44 <li>PKEY zones: ECDSA zone record sets are now encrypted using AES-CTR. <a href="https://bugs.gnunet.org/view.php?id=6487">#6487</a></li>
45 </ul>
46 </li>
47 <li>
48 <tt>IDENTITY</tt>: Identities can now be created either as ECDSA (default) or EdDSA key pairs.</li>
49 </li>
50 <li>
51 <tt>POSTGRESQL</tt>: Allow NULL value returns and fix test cases. <a href="https://bugs.gnunet.org/view.php?id=6524">#6524</a>
52 </li>
53 <li><tt>UTIL</tt>:
54 String time conversion functions no longer localized to preserve reversibility. <a href="https://bugs.gnunet.org/view.php?id=6615">#6615</a>
55 </li>
56 <li><tt>Buildsystem</tt>: README updates to clarify runtime/compile/optional dependencies</li>
57 <li><b>(NEW)</b> <tt>MESSENGER</tt>: New messenger component (experimental)</li>
58</ul>
59<p>
60 A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
61 the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.14.0 bugtracker</a>.
62</p>
63<h4>Known Issues</h4>
64<ul>
65 <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>
66 <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
67 <li>There are known moderate design issues in FS that also impact usability and performance.</li>
68 <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
69 <li>The RPS subsystem remains experimental.</li>
70 <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
71</ul>
72<p>
73 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.
74</p>
75
76<h4>Thanks</h4>
77<p>
78 This release was the work of many people. The following people contributed code and were thus easily identified:
79 Christian Grothoff, Daniel Golle, t3sserakt, TheJackiMonster and Martin Schanzenbach.
80</p>
81{% endblock body_content %}
diff --git a/template/news/2020-11-GNSSpec4.html.j2 b/template/news/2020-11-GNSSpec4.html.j2
new file mode 100644
index 00000000..13e0f28d
--- /dev/null
+++ b/template/news/2020-11-GNSSpec4.html.j2
@@ -0,0 +1,45 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>GNS Technical Specification Milestone 4/4 and Packaging 1+2</h1>
4<p>
5 We are happy to announce the completion of the fourth and last milestone for the GNS
6 Specification. The fourth milestone consists of involving a broader community
7 for feedback and improvements:
8<p>
9<ul>
10 <li><a href="https://news.ycombinator.com/item?id=23766947">Hacker News</a></li>
11 <li><a href="https://datatracker.ietf.org/meeting/108/session/secdispatch">IETF 108 secdispatch</a>
12 (see also associated discussions on the mailinglist)</li>
13 <li><a href="https://centr.org/news/news/alternative-dns.html">Reporting on IETF secdispatch</a></li>
14 <li><a href="https://mailarchive.ietf.org/arch/msg/din/jkbYgEsyuZCknyYQxN-LxDtWpsY/">IRTF DINRG</a></li>
15 <li><a href="https://lists.gnu.org/archive/html/gnunet-developers/2020-07/msg00043.html">Mailing list</a></li>
16</ul>
17<p>
18 Based on this and private feedback received, we updated the draft and
19 the implementation. Most notably, GNS now supports alternative cryptographic
20 schemes for zone keys ("crypto agility") which allows alternative zone types.
21 The (protocol breaking) changes will be released as part of GNUnet 0.14.0.
22 The specification document <b>LSD001</b> can be found at:
23</p>
24<ul>
25 <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
26 <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
27 <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
28 <li><a href="https://datatracker.ietf.org/doc/draft-schanzen-gns/">Link to IETF Datatracker (updated less frequently)</a></li>
29</ul>
30<p>
31 Further, work on packaging has been done on Alpine (Packaging 1) and Debian (Packaging 2) packages.
32 The packaging for Alpine is complete, the Debian package is in progress as
33 review and final integration is out of our hands. For reference see also:
34</p>
35<ul>
36 <li><a href="https://pkgs.alpinelinux.org/packages?name=gnunet&branch=edge">Alpine package</a></li>
37 <li><a href="https://salsa.debian.org/debian/gnunet/-/merge_requests/3">Debian package</a></li>
38</ul>
39<p>
40 We will continue to engage with IETF/IRTF as much as possible (online or in-person)
41 including future presentations and discussions at IETF/IRTF.
42 There is still a packaging task open for Fedora (3) which is still work in progress.
43 This work was (and other aspects still are) generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
44</p>
45{% endblock body_content %}
diff --git a/template/news/2021-03-0.14.1.html.j2 b/template/news/2021-03-0.14.1.html.j2
new file mode 100644
index 00000000..0249b984
--- /dev/null
+++ b/template/news/2021-03-0.14.1.html.j2
@@ -0,0 +1,48 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3<h1>GNUnet 0.14.1</h1>
4<p>
5Continuing to "release early / release often", we present
6GNUnet 0.14.1. This is a bugfix release for gnunet 0.14.0.
7</p>
8<h4>Download links</h4>
9<ul>
10 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz</a></li>
11 <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz.sig</a></li>
12</ul>
13<p>
14The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
15</p>
16<p>
17Note that due to mirror synchronization, not all links may be functional
18early after the release. For direct access try
19<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
20</p>
21<h4>Noteworthy changes in 0.14.1 (since 0.14.0)</h4>
22<ul>
23 <li><tt>TNG</tt>: Various improvements to communicators. <a href="https://bugs.gnunet.org/view.php?id=6361">#6361</a>,<a href="https://bugs.gnunet.org/view.php?id=5550">#5550</a>
24 </li>
25 <li><tt>GNS</tt>: Use autogenerated records header file from GANA.</li>
26 <li><tt>FS</tt>: Improve modularity of FS structs. <a href="https://bugs.gnunet.org/view.php?id=6743">#6743</a></li>
27 <li><tt>SETU</tt>: Various improvements as part of the ongoing work on <a href="https://lsd.gnunet.org/lsd0003">LSD0003</a>.</li>
28 <li><tt>IDENTITY</tt>: Fix wrong key construction for anonymous ECDSA identity.</li>
29 <li><tt>RPS</tt>: Code cleanup mostly addressing warnings.</li>
30 <li><tt>UTIL</tt>:
31 <ul>
32 <li>Added a Base32 en/decoded CLI <tt>gnunet-base32</tt>.</li>
33 <li>Use timeflakes as UUIDs. <a href="https://bugs.gnunet.org/view.php?id=6716">#6716</a></li>
34 </ul>
35 </li>
36 <li><tt>Buildsystem</tt>: Fix libunistring detection. <a href="https://bugs.gnunet.org/view.php?id=6485">#6485</a></li>
37</ul>
38<p>
39A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
40the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.14.1 bugtracker</a>.
41</p>
42
43<h4>Thanks</h4>
44<p>
45This release was the work of many people. The following people contributed code and were thus easily identified:
46Christian Grothoff, Florian Dold, t3sserakt, TheJackiMonster, Elias Summermatter, Julius Bünger and Thien-Thi Nguyen.
47</p>
48{% endblock body_content %}
diff --git a/template/news/2021-03-gsoc-update.html.j2 b/template/news/2021-03-gsoc-update.html.j2
new file mode 100644
index 00000000..d638549a
--- /dev/null
+++ b/template/news/2021-03-gsoc-update.html.j2
@@ -0,0 +1,13 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>No GSoC projects in 2021</h1>
4<p>
5 For 2021, <a href="https://lists.gnu.org/archive/html/summer-of-code/2021-03/msg00000.html">GNU has not been selected as a GSoC organization</a>.
6 This also means that <a href="{{ url_localized('gsoc.html')}}">GNUnet GSoC
7 projects</a> will not be offered through the GSoC programme.
8 Thanks to all of those interested in our proposed projects and their efforts
9 in preparing proposals, including preliminary discussions with us.
10 If you are still interested in tackling any of the proposed open issues, you
11 are very welcome to do so.
12<p>
13{% endblock body_content %}
diff --git a/template/news/2021-04-DISSENS.html.j2 b/template/news/2021-04-DISSENS.html.j2
new file mode 100644
index 00000000..51553aed
--- /dev/null
+++ b/template/news/2021-04-DISSENS.html.j2
@@ -0,0 +1,66 @@
1{% extends "common/news.j2" %}
2{% block body_content %}
3 <h1>DISSENS: Decentralized Identities for Self-sovereign End-users (NGI TRUST)</h1>
4<p>
5 Since mid 2020, a consortium between <a class="link" href="https://taler.net">Taler Systems S.A.</a>,
6the <a class="link" href="https://bfh.ch">Bern University of Applied Sciences</a> and <a class="link" href="https://aisec.fraunhofer.de">Fraunhofer AISEC</a> has been working
7 on bringing privacy-friendly payments using GNU Taler and self-sovereign
8 identity using GNUnet's <a class="link" href="https://reclaim.gnunet.org">re:claimID</a>
9 together in an e-commerce framework.
10</p>
11<p>
12<img style="width: 100%; border: 1px solid #333" src="{{ url_static('dissens-overview.png')}}"/>
13</p>
14<h2>Content</h2>
15<p>
16 Registrations of accounts prior to receiving services online is the standard process for commercial offerings on the Internet which depend on two corner stones of the Web: Payment processing and digital identities. The use of third-party identity provider services (IdPs) is practical as it delegates the task of verifying and storing personal information. The use of payment processors is convenient for the customer as it provides one-click payments. However, the quasi-oligopoly of services providers in those areas include Google and Facebook for identities and PayPal or Stripe for payment processing. Those corporations are not only based in privacy-unfriendly jurisdictions, but also exploit private data for profit.
17</p>
18<p>
19DISSENS makes the case that what is urgently needed are fundamentally different, user-centric and privacy-friendly alternatives to the above.
20Self-sovereign identity (SSI) management is the way to replace IdPs with a user-centric, decentralized mechanism where data and access control is fully under the control of the data subject.
21In combination with a privacy-friendly payment system, DISSENS aims to achieve the same one-click user experience that is currently achieved by privacy-invasive account-based Web shops, but without the users having to setup accounts.
22</p>
23<p>
24To achieve this, DISSENS integrates re:claimID with the GNU Taler payment system in a pilot in order to demonstrate the practical feasibility and benefits of privacy enhancing technologies for users and commercial service providers.
25DISSENS also implements a reference scenario which includes credentials issued by the partners Fraunhofer AISEC and BFH for employees and students, respectively. Users are able to access and use a pilot service developed by Taler Systems S.A. while being able to claim specific discounts for students and researchers.
26</p>
27<p>
28This approach offers significant benefits over existing solutions built using other SSI systems such as <a class="link" href="https://www.sovrin.org">Sovrin</a> or <a class="link" href="https://www.serto.id">serto</a> (formerly uPort):
29</p>
30<b>No gatekeepers; No vendor lock-in:</b>
31<p>
32The approach is completely open to issuers and does not impose any registration restrictions (such as registration fees) in order to define domain specific credentials. Further, the system does not impose a consortium-based governance model — which tend to eventually be driven by commercial interests and not consumer interests. The design enables all participants in the ecosystem to participate without prior onboarding while at the same time being offered full transparency and control regarding their personal data and processes involved.
33</p>
34<b>Support for non-interactive business processes:</b>
35<p>
36At the same time, unlike the SSI systems cited above, re:claimID offers a way to access user information without online interaction with the user. Offline access of shared identity data is a crucial requirement in almost any business process as such processes often occur after direct interaction with the user. For example, customer information such as billing addresses are required in — possibly recurring — back office billing processes which occur well after interaction with a customer.
37</p>
38<b>Scalability and sustainability:</b>
39<p>
40Finally, both re:claimID as the SSI system as well as Taler do not suffer from the usual predicament Blockchain-based systems find themselves in: Both systems do not require a decentralized, public ledger. This eliminates the need for consensus mechanisms, which do not scale and are ecologically unsustainable. In fact, DISSENS employs decentralization only where it provides the most value and use more efficient technology stacks where needed: re:claimID builds on top of the <a class="link" href="{{ url_localized('gns.html') }}">GNU Name System</a>, which makes use of a DHT, an efficient (O(log n)) peer-to-peer data structure. For payments, GNU Taler uses centralized infrastructure operated by audited and regulated exchange providers and facilitates account-less end-to-end interactions between customers and services where all parties have O(1) transaction costs.
41</p>
42<p>
43The result of DISSENS will provide businesses and credential issuers with ready-to-use and standards-compliant templates to build privacy-friendly services in the Web.
44The aim of the DISSENS project was to design a technology stack which combines privacy-friendly online payments with self-sovereign personal data management. The result enables users to be in complete control over their digital identity and personal information while at the same time being able to selectively share information necessary to use commercial services. The pilot demonstrates a sustainable, user-centric, standard-compliant and accessible use case for public service employees and students in the domain of commercial food delivery.
45It serves as an easy-to-adapt template for the integration of other scenarios and use cases.
46</p>
47<h2>Future work</h2>
48<p>
49GNUnet is working on the underlying components mature to the point that Taler+re:claimID can be recommended to operators to enable for account-less shopping with or without verified credentials. This will also require the continuation of our
50work on the low-level transport rewrite as it is a core component of GNS which
51in turn is what makes re:claimID spin.
52</p>
53<h2>Links</h2>
54<ul>
55 <li>Mid-project <a class="link" href="https://gnunet.org/~schanzen/2021-01-18-reclaimID-Taler-Shopping.webm">demonstration video</a> (~7 MB).</li>
56 <li><a class="link" href="https://git.gnunet.org/bibliography.git/plain/docs/dissens2021.pdf">The paper</a> (also accepted for publication without appendix at the <a class="link" href="https://oid2021.compute.dtu.dk/">Open Identity Summit 2021</a>)</li>
57 <li><a class="link" href="https://wordpress.org/plugins/gnu-taler-payment-for-woocommerce/">Taler WooCommerce plugin</a> (wordpress.org)</li>
58 <li>The privacy credential library <a class="link" href="https://github.com/Fraunhofer-AISEC/libpabc">libpabc</a> (github.com).</li>
59 <li><a class="link" href="https://git.taler.net/woocommerce-taler.git">Setup scripts and installation documentation for a Taler + re:claimID + WooCommerce service</a> (taler.net).</li>
60</ul>
61<p>
62</p>
63<p>
64 This work is generously funded by <a class="link" href="https://www.ngi.eu">the EC's Next Generation Internet (NGI) initiative</a> as part of their <a class="link" href="https://www.ngi.eu/ngi-projects/ngi-trust/">NGI TRUST</a> programme.
65</p>
66{% endblock body_content %}
diff --git a/template/news/index.html.j2 b/template/news/index.html.j2
new file mode 100644
index 00000000..abd20092
--- /dev/null
+++ b/template/news/index.html.j2
@@ -0,0 +1,57 @@
1{% extends "common/base.j2" %}
2{% block body_content %}
3 <div class="container-fluid">
4 <div class="container">
5 <article>
6 <div class="row">
7 <div class="container text-center">
8 <h1>{{ _("News") }}<a name="news"></a></h1>
9 <section>
10 <p>
11 {% trans %}
12 News posts about changes related to
13 GNUnet such as releases and events
14 {% endtrans %}
15 &#8211;
16 <a href="{{ url_localized('rss.xml') }}">{{ _("subscribe to our RSS feed") }}</a>
17 </p>
18 </section>
19 </div>
20 </div>
21 <div class="row">
22 {% for year, yitem in newsdata|selectattr('date.year', 'gt', 2019)|groupby('date.year')|reverse %}
23 <b>{{ year }}</b>
24 <ul class="timeline">
25 {% for item in yitem %}
26 <li>
27 <section class="item-preview">
28 <header>
29 <h3>{{ item['title']|e }}</h3>
30 <p class="item-date">
31 {{ item['date'] }}
32 </p>
33 </header>
34 <p class="item-abstract">
35 {{ get_abstract(item['page'], 500) }} <br/>
36 [<a href="{{ url_localized(item['page']) }}" title="{{ item['date']}}">{{ _("read more") }}</a>]
37 </p>
38 </section>
39 </li>
40 {% endfor %}
41 </ul>
42 {% endfor %}
43 </div>
44 <h2>
45 {% trans %}
46 News archives:
47 {% endtrans %}
48 </h2>
49 <ul>
50 {% for year, yitem in newsdata|selectattr('date.year', 'lt', 2020)|groupby('date.year')|reverse %}
51 <li><a href="{{ 'oldnews-' + year|string + '.html' }}">{{ year }} ({{yitem|length}})</a></li>
52 {% endfor %}
53 </ul>
54 </article>
55 </div>
56 </div>
57{% endblock body_content %}
diff --git a/template/news/oldnews-2011.html.j2 b/template/news/oldnews-2011.html.j2
new file mode 120000
index 00000000..ef5fcbee
--- /dev/null
+++ b/template/news/oldnews-2011.html.j2
@@ -0,0 +1 @@
oldnews-2018.html.j2 \ No newline at end of file
diff --git a/template/news/oldnews-2013.html.j2 b/template/news/oldnews-2013.html.j2
new file mode 120000
index 00000000..ef5fcbee
--- /dev/null
+++ b/template/news/oldnews-2013.html.j2
@@ -0,0 +1 @@
oldnews-2018.html.j2 \ No newline at end of file
diff --git a/template/news/oldnews-2018.html.j2 b/template/news/oldnews-2018.html.j2
new file mode 100644
index 00000000..b5833a31
--- /dev/null
+++ b/template/news/oldnews-2018.html.j2
@@ -0,0 +1,50 @@
1{% extends "common/base.j2" %}
2{% block body_content %}
3<!-- Simply link to or copy this file as-is (no modifications required)
4 news/oldnews-::year::. This will generate a new news archive page.
5 Note that you may still have to modify the currently displayed
6 year ranges in the index.html.j2.
7-->
8 <div class="container-fluid">
9 <div class="container">
10 <article>
11 <div class="row">
12 <div class="container text-center">
13 <h1>{{ _("News") + " " + self._TemplateReference__context.name[13:17] }}<a name="news"></a></h1>
14 <section>
15 <p>
16 {% trans %}
17 News posts about changes related to
18 GNUnet such as releases and events
19 {% endtrans %}
20 &#8211;
21 <a href="{{ url_localized('rss.xml') }}">{{ _("subscribe to our RSS feed") }}</a>
22 </p>
23 </section>
24 </div>
25 </div>
26 <div class="row">
27 <b>{{ self._TemplateReference__context.name[13:17] }}</b>
28 <ul class="timeline">
29 {% for item in newsdata|selectattr('date.year', 'eq', self._TemplateReference__context.name[13:17]|int) %}
30 <li>
31 <section class="item-preview">
32 <header>
33 <h3>{{ item['title']|e }}</h3>
34 <p class="item-date">
35 {{ item['date'] }}
36 </p>
37 </header>
38 <p class="item-abstract">
39 {{ item['abstract'] }} <br/>
40 [<a href="{{ item['page'] }}" title="{{ item['date']}}">{{ _("read more") }}</a>]
41 </p>
42 </section>
43 </li>
44 {% endfor %}
45 </ul>
46 </div>
47 </article>
48 </div>
49 </div>
50{% endblock body_content %}
diff --git a/template/news/oldnews-2019.html.j2 b/template/news/oldnews-2019.html.j2
new file mode 120000
index 00000000..ef5fcbee
--- /dev/null
+++ b/template/news/oldnews-2019.html.j2
@@ -0,0 +1 @@
oldnews-2018.html.j2 \ No newline at end of file
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-27 11:42:55 +0000