aboutsummaryrefslogtreecommitdiff
path: root/news/2019-0.11.1.inc
diff options
context:
space:
mode:
Diffstat (limited to 'news/2019-0.11.1.inc')
-rw-r--r--news/2019-0.11.1.inc156
1 files changed, 88 insertions, 68 deletions
diff --git a/news/2019-0.11.1.inc b/news/2019-0.11.1.inc
index dd6e5452..d4ebc414 100644
--- a/news/2019-0.11.1.inc
+++ b/news/2019-0.11.1.inc
@@ -1,25 +1,22 @@
1<article> 1<article>
2<h3> 2 <h3>
3<a name="gnunet-0.11.1-release">2019-04-03: GNUnet 0.11.1 released</a> 3 <a name="gnunet-0.11.1-release">2019-04-03: GNUnet 0.11.1 released</a>
4</h3> 4 </h3>
5 5 <p>
6<p> 6 We are pleased to announce the release of GNUnet 0.11.1.
7We are pleased to announce the release of GNUnet 0.11.1. 7 </p>
8<p> 8 <p>
9 9 This is a bugfix release for 0.11.0, mostly fixing minor bugs,
10<p> 10 improving documentation and fixing various build issues. In
11This is a bugfix release for 0.11.0, mostly fixing minor bugs, 11 terms of usability, users should be aware that there are still a large
12improving documentation and fixing various build issues. In 12 number of known open issues in particular with respect to ease of use,
13terms of usability, users should be aware that there are still a large 13 but also some critical privacy issues especially for mobile users.
14number of known open issues in particular with respect to ease of use, 14 Also, the nascent network is tiny (about 200 peers) and thus unlikely to
15but also some critical privacy issues especially for mobile users. 15 provide good anonymity or extensive amounts of interesting
16Also, the nascent network is tiny (about 200 peers) and thus unlikely to 16 information. As a result, the 0.11.1 release is still only suitable
17provide good anonymity or extensive amounts of interesting 17 for early adopters with some reasonable pain tolerance.
18information. As a result, the 0.11.1 release is still only suitable 18 </p>
19for early adopters with some reasonable pain tolerance. 19 <h4>Download links</h4>
20</p>
21
22<h4>Download links</h4>
23 <ul> 20 <ul>
24 <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> 21 <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>
25 <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> 22 <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>
@@ -28,56 +25,79 @@ for early adopters with some reasonable pain tolerance.
28 <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> 25 <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>
29 <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> 26 <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>
30 </ul> 27 </ul>
31 (gnunet-gtk and gnunet-fuse were not released again, as there were no 28 <p>
32 changes and the 0.11.0 versions are expected to continue to work fine 29 (gnunet-gtk and gnunet-fuse were not released again, as there were no
33 with gnunet-0.11.1.) 30 changes and the 0.11.0 versions are expected to continue to work fine
34<p> 31 with gnunet-0.11.1.)
35Note that due to mirror synchronization, not all links might be functional 32 </p>
36early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a> 33 <p>
37</p> 34 Note that due to mirror synchronization, not all links might be functional
38<p> 35 early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
39Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be 36 </p>
40stopped using <tt>gnunet-arm -e</tt>. 37 <p>
41</p> 38 Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be
42 39 stopped using <tt>gnunet-arm -e</tt>.
43<h4>Noteworthy changes in 0.11.1</h4> 40 </p>
44 41 <h4>Noteworthy changes in 0.11.1</h4>
45 <ul> 42 <ul>
46 <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li> 43 <li>
47 <li>REST and GNS proxy configuration options for address binding were added</li> 44 gnunet-qr was rewritten in C, removing our last dependency on Python 2.x
48 <li>gnunet-publish by default no longer includes creation time</li> 45 </li>
49 <li>Unreliable message ordering logic in CADET was fixed</li> 46 <li>
50 <li>Various improvements to build system and documentation</li> 47 REST and GNS proxy configuration options for address binding were added
48 </li>
49 <li>
50 gnunet-publish by default no longer includes creation time
51 </li>
52 <li>
53 Unreliable message ordering logic in CADET was fixed
54 </li>
55 <li>
56 Various improvements to build system and documentation
57 </li>
51 </ul> 58 </ul>
52 The above is just the short list, our bugtracker lists 59 <p>
53 <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312"> 60 The above is just the short list, our bugtracker lists
54 14 individual issues</a> that were resolved since 0.11.0. 61 <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312">
55 62 14 individual issues</a> that were resolved since 0.11.0.
56<h4>Known Issues</h4> 63 </p>
64 <h4>Known Issues</h4>
57 <ul> 65 <ul>
58 <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems 66 <li>
59 which will need to be addressed in the future to achieve acceptable usability, 67 There are known major design issues in the TRANSPORT, ATS and CORE subsystems
60 performance and security.</li> 68 which will need to be addressed in the future to achieve acceptable usability,
61 <li>There are known moderate implementation limitations in CADET that 69 performance and security.
62 negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li> 70 </li>
63 <li>There are known moderate design issues in FS that also impact 71 <li>
64 usability and performance.</li> 72 There are known moderate implementation limitations in CADET that
65 <li>There are minor implementation limitations in SET that create 73 negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.
66 unnecessary attack surface for availability.</li> 74 </li>
67 <li>The RPS subsystem remains experimental.</li> 75 <li>
68 <li>Some high-level tests in the test-suite fail non-deterministically due to 76 There are known moderate design issues in FS that also impact
69 the low-level TRANSPORT issues.</li> 77 usability and performance.
78 </li>
79 <li>
80 There are minor implementation limitations in SET that create
81 unnecessary attack surface for availability.
82 </li>
83 <li>
84 The RPS subsystem remains experimental.
85 </li>
86 <li>
87 Some high-level tests in the test-suite fail non-deterministically due to
88 the low-level TRANSPORT issues.
89 </li>
70 </ul> 90 </ul>
71<p> 91 <p>
72In addition to this list, you may also want to consult our bug tracker 92 In addition to this list, you may also want to consult our bug tracker
73at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists 93 at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists
74about 190 more specific issues. 94 about 190 more specific issues.
75</p> 95 </p>
76 96
77<h4>Thanks</h4> 97 <h4>Thanks</h4>
78<p> 98 <p>
79This release was the work of many people. The following people 99 This release was the work of many people. The following people
80contributed code and were thus easily identified: 100 contributed code and were thus easily identified:
81ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius BΓΌnger. 101 ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
82</p> 102 </p>
83</article> 103</article>