aboutsummaryrefslogtreecommitdiff
path: root/rss.xml
diff options
context:
space:
mode:
Diffstat (limited to 'rss.xml')
-rw-r--r--rss.xml313
1 files changed, 210 insertions, 103 deletions
diff --git a/rss.xml b/rss.xml
index 2961c10a..4d50af63 100644
--- a/rss.xml
+++ b/rss.xml
@@ -8,121 +8,228 @@
8 <title>GNUnet Hacker Meeting 2018 at La Decentrale</title> 8 <title>GNUnet Hacker Meeting 2018 at La Decentrale</title>
9 <link>https://gnunet.org/#gnunet-hacker-meeting-2018-2</link> 9 <link>https://gnunet.org/#gnunet-hacker-meeting-2018-2</link>
10 <description> 10 <description>
11 Second GNUnet Hacker Meeting 2018 at La Decentrale (https://decentrale.ch/), Switzerland 11 <article>
12 12 <a name="gnunet-hacker-meeting-2018-2"></a>
13 The GNUnet hackers met for the second time this year. The primary goal was 13 <h3>Second GNUnet Hacker Meeting 2018 at <a href="https://decentrale.ch/">La Décentrale</a>, Switzerland</h3>
14 to squash bugs to bring out a new release. Aside from this we worked hard on 14 <p>
15 improving the documentation and to launch this new website. 15 The GNUnet hackers met for the second time this year. The primary goal
16 was to squash bugs to bring out a new release. Aside from this we
17 worked hard on improving the documentation and to launch this new
18 website.
19 </p>
20 </article>
16 </description> 21 </description>
17 </item> 22 </item>
18 <item> 23 <item>
19 <title>2019-02: Topics for GSoC 2019</title> 24 <title>2019-02: Topics for GSoC 2019</title>
20 <link>https://gnunet.org/#gsoc2019</link> 25 <link>https://gnunet.org/#gsoc2019</link>
21 <description> 26 <description>
22 2019-02: Topics for GSoC 2019 27 <article>
23Android Port 28 <h3>
24 29 <a NAME="gsoc2019"></a>2019-02: Topics for GSoC 2019
25It is time for GNUnet to run properly on Android. Note that 30 </h3>
26GNUnet is written in C, and this is not about rewriting 31 <section>
27GNUnet in Java, but about getting the C code to run on Android. 32 <h4>Android Port</h4>
28 33 <p>
29Mentor: Hartmut Goebel (https://www.goebel-consult.de/) 34 It is time for GNUnet to run properly on Android. Note that
30 35 GNUnet is written in C, and this is not about rewriting
31Help with Continuous Integration setup 36 GNUnet in Java, but about getting the C code to run on Android.
32 37 <br>
33There is a push for migrating our CI to Gitlab. The CI should 38 Mentor: <a href="https://www.goebel-consult.de/">Hartmut Goebel</a>
34eventually not just run "make check" on various platforms, but also 39 </p>
35perform tests with multiple peers running in different VMs with 40 </section>
36specific network topologies (i.e. NAT) between them being simulated. 41
37The CI should also be integrated with Gauger for performance 42 <section>
38regression analysis. Running jobs only when dependencies have changed 43 <h4>Help with Continuous Integration setup</h4>
39and scripting more granular triggers or ideally automatic dependency 44 <p>
40discovery (as done by the autotools) is also important. 45 There is a push for migrating our CI to Gitlab. The CI should
41 46 eventually not just run "make check" on various platforms, but also
42Mentor: TBD 47 perform tests with multiple peers running in different VMs with
43 48 specific network topologies (i.e. NAT) between them being simulated.
44Migrate gnunet-qr from Python 2.7 to C using libzbar 49 The CI should also be integrated with Gauger for performance
45 50 regression analysis. Running jobs only when dependencies have changed
46Python 2.7 is reaching its end-of-life, and we want to get rid 51 and scripting more granular triggers or ideally automatic dependency
47of the dependency on Python. The existing gnunet-qr tool is a 52 discovery (as done by the autotools) is also important.
48rather simple wrapper around python-zbar, which itself wraps 53 <br>
49libzbar. The goal of this project is to directly use libzbar 54 Mentor: TBD
50to scan QR codes for GNUnet / the GNU Name System (see 55 </p>
51also #5562 (https://bugs.gnunet.org/view.php?id=5562). 56 </section>
52 57
53Mentor: Christian Grothoff 58 <section>
54 59 <h4>Migrate gnunet-qr from Python 2.7 to C using libzbar</h4>
55reclaimID alternative GNS-based encryption 60 <p>
56 61 Python 2.7 is reaching its end-of-life, and we want to get rid
57reclaimID is a decentralized identity system build on top of the GNU 62 of the dependency on Python. The existing gnunet-qr tool is a
58Name System. 63 rather simple wrapper around python-zbar, which itself wraps
59Currently, it uses an encryption scheme called attribute-based encryption. 64 libzbar. The goal of this project is to directly use libzbar
60However, through the clever use of GNS's built in record encryption, 65 to scan QR codes for GNUnet / the GNU Name System (see
61it is possible to... 66 also <a href="https://bugs.gnunet.org/view.php?id=5562">#5562</a>).
62 67 <br>
63... improve performance by reducing encryption overhead. 68 Mentor: Christian Grothoff
64... reduce dependencies. 69 </p>
65 70 </section>
66This project also includes two separate, smaller tasks: 71
67 72 <section>
68* Performance improvements to the out-of-band authorization flow (OpenID Connect) 73 <h4>re:claimID OpenID Connect performance improvements</h4>
69* A webextension which allows reclaimID to be used without the need of a GNS proxy. 74 <p>
70 75 reclaimID is a decentralized identity system build on top of the GNU
71The two smaller tasks are optional and may be dropped in case the student 76 Name System.
72encounters any unforseen complications when implementing the main task. 77 Upon authorization, the user provides a requesting party (RP) such as a website
73 78 with an authorization ticket (e.g. piggybacked in an OpenID authorization code).
74Mentor: Martin Schanzenbach 79 The RP uses information contained in this ticket to
80 <ol>
81 <li> Retrieve the decryption key from GNS</li>
82 <li> Retrieve the user attributes from GNS</li>
83 </ol>
84 The GNS lookups ensure that the RP receives up-to-date attributes and functional
85 decryption keys. However, in particular the RP-specific encryption key
86 resolution can be slow and even fail depending on the network topology.
87 We propose that in an initial exchange, in particular OpenID authorization code
88 flows, we try to incorporate key and maybe even an attribute set in the ticket
89 exchange.
90
91 In order to mitigate this issue, this project is meant to investigate and implement how...
92 <ol>
93 <li> ... decryption keys can be added to an initial exchange in OpenID.</li>
94 <li> ... initial set(s) of attributes can be piggybacked in OpenID.</li>
95 </ol>
96 <br/>
97 Mentor: Martin Schanzenbach
98 </p>
99 </section>
100
101 <section>
102 <h4>re:claimID alternative GNS-based encryption</h4>
103 <p>
104 re:claimID is a decentralized identity system build on top of the GNU
105 Name System.
106 The initial design and implementation of re:claimID includes an attribute-based
107 encryption module in order to prevent unauthorized access to attributes in the
108 name system.
109 Our motivation for re:claimID was for it to be name system agnostic, which
110 means the design theoretically also works for other name systems such as
111 namecoin.
112 Other name systems often do not have built-in mechanisms in order to do this.
113 Hence, we implemented an ABE access control layer. Our ABE implementation
114 requires two third party libraries: libpbc and libgabe. While we could merge
115 libgabe into the gnunet service implementation of re:claimID, libpbc is a
116 rather large, third party library which lacks packaging in distributions and
117 for platforms.
118 On the other hand, GNS supports record data encryption using symmetric keys as
119 labels.
120 If we make the access control layer of re:claimID more generic in order to
121 support both ABE and GNS encryption, we could reduce the required depenencies.
122 This would result in gnunet packages to include re:claimID by default.
123
124 In short, the goals are to...
125 <ol>
126 <li> ... improve performance by reducing encryption overhead.</li>
127 <li> ... reduce dependencies.</li>
128 </ol>
129 <br/>
130 Mentor: Martin Schanzenbach
131 </p>
132 </section>
133 </article>
75 </description> 134 </description>
76 </item> 135 </item>
77 <item> 136 <item>
78 <title>2019-02: GNUnet 0.11.0 released</title> 137 <title>2019-02: GNUnet 0.11.0 released</title>
79 <link>https://gnunet.org/#gnunet-0.11.0-release</link> 138 <link>https://gnunet.org/#gnunet-0.11.0-release</link>
80 <description> 139 <description>
81 2019-02: GNUnet 0.11.0 released 140 <article>
82 141 <h3>
83 We are pleased to announce the release of GNUnet 0.11.0. 142 <a name="gnunet-0.11.0-release">2019-02: GNUnet 0.11.0 released</a>
84 143 </h3>
85 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. 144
86Download links 145 <p>
87 146 We are pleased to announce the release of GNUnet 0.11.0.
88 http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz 147 <p>
89 http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig 148
90 http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz 149 <p>
91 http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig 150 This is a major release after about five years of development. In
92 http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz 151 terms of usability, users should be aware that there are still a large
93 http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig 152 number of known open issues in particular with respect to ease of use,
94 153 but also some critical privacy issues especially for mobile users.
95Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try http://ftp.gnu.org/gnu/gnunet/ 154 Also, the nascent network is tiny (about 200 peers) and thus unlikely to
96 155 provide good anonymity or extensive amounts of interesting
97Note that GNUnet is now started using gnunet-arm -s. GNUnet should be stopped using gnunet-arm -e. 156 information. As a result, the 0.11.0 release is still only suitable
98Noteworthy changes in 0.11.0 157 for early adopters with some reasonable pain tolerance.
99 158 </p>
100 The Web site and manuals have undergone significant rework. You can find an archive of the old Web site at old.gnunet.org. 159
101 The code now builds again on macOS. GNUnet on macOS is experimental. While it builds and seems to run fine, some tests are known to fail. 160 <h4>Download links</h4>
102 Build process now works properly with libidn2 161 <ul>
103 Except for gnunet-qr, all Python code was migrated to Python 3.7. 162 <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>
104 Fixed security issues in secret sharing cryptography logic 163 <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>
105 Services running out of file descriptors on accept() no longer busy wait 164 <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>
106 Fixed crash in gnunet-gns2dns proxy 165 <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>
107 GNS responses are now padded to minimize information disclosure from the size 166 <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>
108 Fixed API issues and (rare) crash bugs in CADET 167 <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>
109 The experimental SecuShare code is not included in the release, you can now find it in the gnunet-secushare Git repository. 168 </ul>
110 The Ascension tool (separate download) now allows importing DNS zones into GNS via AXFR. 169 <p>
111 GNUnet now includes a decentralised identity attribute sharing service: reclaimID. A ready-to-use client can be found in an external repo. 170 Note that due to mirror synchronization, not all links might be functional
112 The code now builds again on NetBSD. GNUnet on NetBSD is experimental. 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. 171 early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
113 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. 172 </p>
114 173 <p>
115The above is just the short list, our bugtracker lists over 100 individual issues that were resolved since 0.11.0pre66. 174 Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be
116Known Issues 175 stopped using <tt>gnunet-arm -e</tt>.
117 176 </p>
118 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. 177
119 There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order. 178 <h4>Noteworthy changes in 0.11.0</h4>
120 There are known moderate design issues in FS that also impact usability and performance. 179
121 There are minor implementation limitations in SET that create unnecessary attack surface for availability. 180 <ul>
122 The RPS subsystem remains experimental. 181 <li>The Web site and manuals have undergone significant rework. You can find an
123 Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues. 182 archive of the old Web site at <a href="https://old.gnunet.org/">old.gnunet.org</a>.</li>
124 183 <li>The code now builds again on macOS. GNUnet on macOS is <i>experimental</i>.
125In addition to this list, you may also want to consult our bug tracker at bugs.gnunet.org which lists about 150 more specific issues. 184 While it builds and seems to run fine, some tests are known to fail.</li>
185 <li>Build process now works properly with libidn2</li>
186 <li>Except for <tt>gnunet-qr</tt>, all Python code was migrated to Python 3.7.</li>
187 <li>Fixed security issues in secret sharing cryptography logic</li>
188 <li>Services running out of file descriptors on <tt>accept()</tt> no longer busy wait</li>
189 <li>Fixed crash in gnunet-gns2dns proxy</li>
190 <li>GNS responses are now padded to minimize information disclosure from the size</li>
191 <li>Fixed API issues and (rare) crash bugs in CADET</li>
192 <li>The experimental SecuShare code is not included in the release, you can
193 now find it in the <a href="https://git.gnunet.org/gnunet-secushare/">gnunet-secushare</a>
194 Git repository.</li>
195 <li>The Ascension tool (separate download) now allows importing DNS zones into GNS via AXFR.</li>
196 <li>GNUnet now includes a decentralised identity attribute sharing service:
197 reclaimID. A ready-to-use client can be found in an
198 <a href="https://gitlab.com/reclaimid/client">external repo</a>.</li>
199 <li>The code now builds again on NetBSD. GNUnet on NetBSD is <i>experimental</i>.
200 While it builds and seems to run fine, full support requires more
201 changes in the core of GNUnet
202 It will soon be available via pkgsrc.
203 <li>Many things changed on the build system side. If you package
204 GNUnet for an operating system or otherwise package manager,
205 make sure that you read the README.</li>
206 </ul>
207 The above is just the short list, our bugtracker lists
208 <a href="https://bugs.gnunet.org/changelog_page.php?version_id=258">
209 over 100 individual issues</a> that were resolved since 0.11.0pre66.
210
211 <h4>Known Issues</h4>
212 <ul>
213 <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems
214 which will need to be addressed in the future to achieve acceptable usability,
215 performance and security.</li>
216 <li>There are known moderate implementation limitations in CADET that
217 negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
218 <li>There are known moderate design issues in FS that also impact
219 usability and performance.</li>
220 <li>There are minor implementation limitations in SET that create
221 unnecessary attack surface for availability.</li>
222 <li>The RPS subsystem remains experimental.</li>
223 <li>Some high-level tests in the test-suite fail non-deterministically due to
224 the low-level TRANSPORT issues.</li>
225 </ul>
226 <p>
227 In addition to this list, you may also want to consult our bug tracker
228 at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists
229 about 150 more specific issues.
230 </p>
231 </p>
232 </article>
126 </description> 233 </description>
127 </item> 234 </item>
128 </channel> 235 </channel>