[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[www] 01/02: add news

From: gnunet
Subject: [www] 01/02: add news
Date: Sat, 14 Nov 2020 05:37:44 +0100

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository www.

commit 2e2b45034d43820c95e6fd239021f34068eca45d
Author: Martin Schanzenbach <>
AuthorDate: Sat Nov 14 13:27:37 2020 +0900

    add news
 news/2020-11-0.14.0.html.j2 | 78 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 78 insertions(+)

diff --git a/news/2020-11-0.14.0.html.j2 b/news/2020-11-0.14.0.html.j2
new file mode 100644
index 0000000..0cbb23d
--- /dev/null
+++ b/news/2020-11-0.14.0.html.j2
@@ -0,0 +1,78 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.14.0 released</h1>
+  We are pleased to announce the release of GNUnet 0.14.0.
+  This is a new major release. It breaks protocol compatibility with the 
0.13.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.13.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.13.x peers will be able to communicate with Git
+  master or 0.13.x peers, but some services will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.14.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+<h4>Download links</h4>
+  <li><a 
+  <li><a 
+  <li><a 
+  <li><a 
+  <li><a 
+  <li><a 
+  The GPG key used to sign is: 
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="";></a>
+<h4>Noteworthy changes in 0.14.0 (since 0.13.3)</h4>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Aligned with specification <a 
+      <li>Crypto agility: The GNS protocol now supports other zone keys 
besides ECDSA.
+      However, EdDSA zone keys are currently not yet implemented. <a 
+      <li>Symmetric encryption: Records are now encrypted using AES-CTR 
instead of AES-CBC. <a 
+    </ul>
+  </li>
+  <li>
+    <tt>POSTGRESQL</tt>: Allow NULL value returns and fix test cases. <a 
+  </li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>String time conversion functions no longer localized to preserve 
reversibility. <a href="";>#6615</a></li>
+    </ul>
+  </li>
+  <li><tt>Buildsystem</tt>: README updates to clarify runtime/compile/optional 
+  <li><b>(NEW)</b> <tt>MESSENGER</tt>: New messenger component 
+A detailed list of changes can be found in the <a 
href="";>ChangeLog</a> and
+the <a href="";>0.14.0 
+<h4>Known Issues</h4>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE 
subsystems which will need to be addressed in the future to achieve acceptable 
usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that 
negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability 
and performance.</li>
+  <li>There are minor implementation limitations in SET that create 
unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due 
to the low-level TRANSPORT issues.</li>
+  In addition to this list, you may also want to consult our bug tracker at <a 
href="";></a> which lists about 190 more 
specific issues.
+  This release was the work of many people. The following people contributed 
code and were thus easily identified:
+  Christian Grothoff, Daniel Golle, t3sserakt, TheJackiMonster and Martin 
+{% endblock body_content %}

To stop receiving notification emails like this one, please contact

reply via email to

[Prev in Thread] Current Thread [Next in Thread]