blob: beffdcf625417d31b604ee0d5d9efe8b771d5711 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
|
{% extends "common/base.j2" %}
{% block body_content %}
<div class="container">
<h2>{{ _("Tutorial: GNUnet on Debian 9") }}</h2>
<h3>{{ _("Introduction") }}</h3>
<p>
Welcome to the hopefully painless GNUnet tutorial for Debian 9! It provides
very concrete instructions on how to compile, install and configure a current
version of GNUnet. The goal is to support newcomers, either end users or
developers, who want to get in touch with GNUnet for the first time. After
installing GNUnet we will make sure that out new GNUnet installation is working
correctly.
</p>
<p>
<b>Attention: If you came across the official gnunet package for Debian 9,
ignore it! It is ancient and not compatible with current GNUnet
installations.</b>
</p>
<p>
Now let's start!
</p>
<h3>{{ _("Requirements") }}</h3>
<p>
First let's install the following Debian 9 packages to use GNUnet
painlessly. Optional dependencies are listed in Appendix A. They are required
for some experimental GNUnet features.
</p>
<code>
$ sudo apt install git libtool autoconf autopoint \<br>
build-essential libgcrypt-dev libidn11-dev zlib1g-dev \<br>
libunistring-dev libglpk-dev miniupnpc libextractor-dev \<br>
libjansson-dev libcurl4-gnutls-dev gnutls-bin libsqlite3-dev \<br>
openssl libnss3-tools libopus-dev libpulse-dev libogg-dev
</code>
<h3>{{ _("Make an installation directory") }}</h3>
<p>
Next we create a directory in our home directory where we store
the source code later. We should keep this directory after
installation because it contains Makefiles that can be used for
uninstalling GNUnet again (see chapter *Uninstall GNUnet and its
dependencies*).
</p>
<code>
$ mkdir ~/gnunet_installation
</code>
<h3>{{ _("Get the source code") }}</h3>
<p>
We download the GNUnet source code using git. On Debian 9 we need the
sources of another library (libmicrohttpd).
</p>
<p>
<b>Attention: The official libmicrohttpd package for Debian 9 is too old, we need
at least version 0.9.52.</b>
</p>
<code>
$ cd ~/gnunet_installation<br>
$ git clone --depth 1 https://gnunet.org/git/gnunet.git<br>
$ git clone --depth 1 https://gnunet.org/git/gnunet-gtk.git<br>
$ git clone --depth 1 https://gnunet.org/git/libmicrohttpd.git
</code>
<h3>{{ _("Compile and Install") }}</h3>
<p>
Before we can compile GNUnet on Debian 9, we compile and install libmicrohttpd.
</p>
<code>
$ cd ~/gnunet_installation/libmicrohttpd<br>
$ autoreconf -fi<br>
$ sudo apt install libgnutls28-dev<br>
$ ./configure --disable-doc --prefix=/opt/libmicrohttpd<br>
$ make -j$(nproc || echo -n 1)<br>
$ sudo make install<br>
</code>
<p>
Installing GNUnet is not hard. We have two options:
installing a *production version* and installing a *development version*. If
you want to start writing GNUnet applications or join the GNUnet development
choose the development version (it will print more debug output and contains
debug symbols that can be displayed with a debugger). Otherwise choose the
production version.
</p>
<h4>{{ _("Option 1: GNUnet for production / usage") }}</h4>
<code>
$ cd ~/gnunet_installation/gnunet<br>
$ ./bootstrap<br>
$ ./configure --prefix=$GNUNET_PREFIX --disable-documentation --with-microhttpd=/opt/libmicrohttpd<br>
$ sudo addgroup gnunetdns<br>
$ sudo adduser --system --group --disabled-login --home /var/lib/gnunet gnunet<br>
$ make -j$(nproc || echo -n 1)<br>
$ sudo make install
</code>
<h4>{{ _("Option 2: GNUnet for development") }}</h4>
<code>
$ cd ~/gnunet_installation/gnunet<br>
$ ./bootstrap<br>
$ export CFLAGS="-g -Wall -O0"<br>
$ ./configure --prefix=$GNUNET_PREFIX --disable-documentation --enable-logging=verbose --with-microhttpd=/opt/libmicrohttpd<br>
$ make -j$(nproc || echo -n 1)<br>
$ sudo make install
</code>
<h4>{{ _("Option 3: gnunet-gtk") }}</h4>
<p>
Installing the Gtk+-based graphical user
interface can be done on top of either the production or development installation.
</p>
<code>
$ sudo apt install libgtk-3-dev libgladeui-dev libunique-dev libqrencode-dev
$ cd ~/gnunet_installation/gnunet-gtk<br>
$ ./bootstrap<br>
$ export CFLAGS="-g -Wall -O0"<br>
$ ./configure --prefix=$GNUNET_PREFIX --with-gnunet=$GNUNET_PREFIX<br>
$ make -j$(nproc || echo -n 1)<br>
$ sudo make install
</code>
<!--
<h4>{{ _("Install GNUnet plugin for name resolution") }}</h4>
<p>
So now it gets a bit nasty. It's not so bad. All we have to do
is copy a file and edit another one. The file we need to copy
is GNUnet's plugin for the Name Service Switch (NSS) in unix
systems. Different unixes expect it in different locations and
GNUnet's build system does not try to guess. On Debian 9 we
have to do
<code>
$ sudo cp /usr/lib/gnunet/nss/libnss_gns.so.2 /lib/$(uname -m)-linux-gnu/
</code>
</p>
<p>
The next step is activating the GNUnet plugin we just copied
in the NSS config. It is located in `/etc/nsswitch.conf`. It should
contain a line starting with "hosts" similar to this (at least "files"
and "dns" should be there):
</p>
<p>
<code>
$ cat /etc/nsswitch.conf<br>
hosts: files mdns4_minimal [NOTFOUND=return] dns
</code>
</p>
<p>
<b>Attention: Once we modified `/etc/nsswitch.conf` DNS resolution will only
be possible as long as is GNUnet is running. We can leave the next step out,
but then we will not be able to use GNUnet's name resolution in external
applications.</b>
</p>
<p>We save a copy of the original file and then modify the line using sed:</p>
<p>
<code>
$ sudo cp /etc/nsswitch.conf /etc/nsswitch.conf.original<br>
$ sudo sed -i -E 's/^(hosts:.*) dns/\1 gns [NOTFOUND=return] dns/' /etc/nsswitch.conf
</code>
</p>
<p>Now in the line starting with "hosts" should contain an entry "gns [NOTFOUND=return]" before the "dns" entry like this:</p>
<p>
<code>
hosts: files mdns4_minimal [NOTFOUND=return] gns [NOTFOUND=return] dns
</code>
</p>
<p>That's it. It wasn't that nasty, was it?</p>
-->
<h3>{{ _("Configuration") }}</h3>
<p>
Congratulations! GNUnet is now installed! Before we start it we
need to create a configuration file. By default GNUnet looks in
our home directory for the file `~/.config/gnunet.conf`. We can
start with an empty file for now:
</p>
<code>
$ touch ~/.config/gnunet.conf
</code>
<p>
It's reccomended that you increase your bandwidth restrictions
from the acutely low defaults. The example below sets the WAN
and LAN limits to the value "unlimited".
</p>
<code>
$ gnunet-config -s ats -o WAN_QUOTA_IN -V unlimited<br />
$ gnunet-config -s ats -o WAN_QUOTA_OUT -V unlimited<br />
$ gnunet-config -s ats -o LAN_QUOTA_IN -V unlimited<br />
$ gnunet-config -s ats -o LAN_QUOTA_OUT -V unlimited<br />
</code>
<p>
Now we can start it with the command line tool
`gnunet-arm` (Automatic Restart Manager).
</p>
<code>
$ gnunet-arm -s
</code>
<p>
It starts the default GNUnet services. We can list them with the
`-I` option:
</p>
<code>
$ gnunet-arm -I<br>
Running services:<br>
ats (gnunet-service-ats)<br>
revocation (gnunet-service-revocation)<br>
set (gnunet-service-set)<br>
nat (gnunet-service-nat)<br>
transport (gnunet-service-transport)<br>
peerstore (gnunet-service-peerstore)<br>
hostlist (gnunet-daemon-hostlist)<br>
identity (gnunet-service-identity)<br>
namecache (gnunet-service-namecache)<br>
peerinfo (gnunet-service-peerinfo)<br>
datastore (gnunet-service-datastore)<br>
zonemaster (gnunet-service-zonemaster)<br>
zonemaster-monitor (gnunet-service-zonemaster-monitor)<br>
nse (gnunet-service-nse)<br>
cadet (gnunet-service-cadet)<br>
dht (gnunet-service-dht)<br>
core (gnunet-service-core)<br>
gns (gnunet-service-gns)<br>
statistics (gnunet-service-statistics)<br>
topology (gnunet-daemon-topology)<br>
fs (gnunet-service-fs)<br>
namestore (gnunet-service-namestore)<br>
vpn (gnunet-service-vpn)
</code>
<p>
For stopping GNUnet again we can use the `-e` option.
</p>
<code>
$ gnunet-arm -e
</code>
<section>
<h3>{{ _("Use GNUnet!") }}</h3>
<p>
Please head over here: <a href="https://gnunet.org/en/use.html">Use!</a>
<p>
</section>
<h3>{{ _("Uninstall GNUnet and its dependencies") }}</h3>
<code>
$ cd ~/gnunet_installation/gnunet<br>
$ sudo make uninstall<br>
$ cd ~/gnunet_installation/libmicrohttpd<br>
$ sudo make uninstall<br>
$ sudo apt remove git libtool autoconf autopoint build-essential libgcrypt-dev libidn11-dev zlib1g-dev libunistring-dev libglpk-dev miniupnpc libextractor-dev libjansson-dev libcurl4-gnutls-dev libsqlite3-dev<br>
$ sudo apt autoremove<br>
$ sudo userdel -r gnunet<br>
$ sudo groupdel gnunet<br>
$ sudo groupdel gnunetdns<br>
$ sudo mv /etc/nsswitch.conf.original /etc/nsswitch.conf<br>
$ sudo rm /lib/$(uname -m)-linux-gnu/libnss_gns.so.2
</code>
<h3>{{ _("Troubleshooting") }}</h3>
<h4>{{ _("You can't reach other people's nodes") }}</h4>
<p>
Should our computer not have reached the open GNUnet network automatically,
we can manually instruct our node how to reach the nodes of our friends. This
works by exchanging HELLO strings. This is how we get a hello string for our
computer.
</p>
<code>
$ gnunet-peerinfo -gn
</code>
<p>
We can now pass this string to our friends "out of band" (using
whatever existing chat or messaging technology). If the string
contains some private IP networks we don't want to share, we can
carefully edit them out.
</p>
<p>
Once we receive such strings from our friends, we can add them
like this:
</p>
<code>
gnunet-peerinfo -p <string>
</code>
<p>
Now our GNUnet nodes can attempt reaching each other directly. This may
still fail due to NAT traversal issues.
</p>
<!--
<h4>{{ _("OMG you guys broke my internet") }}</h4>
<p>
We can replace `/etc/nsswitch.conf` with the backup we made earlier
(`/etc/nsswitch.conf.original`). Now DNS resolution should work again without a
running GNUnet.
</p>
<code>
$ cp /etc/nsswitch.conf.original /etc/nsswitch.conf
</code>
-->
</div>
{% endblock body_content %}
|