aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlurchi <lurchi@strangeplace.net>2018-11-16 23:16:36 +0100
committerlurchi <lurchi@strangeplace.net>2018-11-16 23:16:36 +0100
commit7326e6162fe0432ccad25aad4963657842476484 (patch)
tree0e87b7dbecd19e360da1487a41672517767564ea
parent253c6b6ceed6aa989b14edc2742f7278c5625747 (diff)
downloadwww-7326e6162fe0432ccad25aad4963657842476484.tar.gz
www-7326e6162fe0432ccad25aad4963657842476484.zip
try to fix html
-rw-r--r--tutorial-debian9.html.j218
1 files changed, 9 insertions, 9 deletions
diff --git a/tutorial-debian9.html.j2 b/tutorial-debian9.html.j2
index 50c1a979..87f04d2d 100644
--- a/tutorial-debian9.html.j2
+++ b/tutorial-debian9.html.j2
@@ -291,9 +291,9 @@ $ gnunet-namestore -z myself -a -e never -p -t PKEY -n alice -V HWTYD3P5D77JVFNV
291<p>Our identity in Bobs namestore is a public record (-p) and never expires (-e never). Now Bob (let's assume he has called his identity myself, too) should be able to resolve our "ccc" record, too!</p> 291<p>Our identity in Bobs namestore is a public record (-p) and never expires (-e never). Now Bob (let's assume he has called his identity myself, too) should be able to resolve our "ccc" record, too!</p>
292 292
293<p><code> 293<p><code>
294$ gnunet-gns -u ccc.alice.myself 294$ gnunet-gns -u ccc.alice.myself<br>
295ccc.alice.myself: 295ccc.alice.myself:<br>
296Got `A' record: 195.54.164.39 296Got `A' record: 195.54.164.39
297</code></p> 297</code></p>
298 298
299<p>It can continue like this. A friend of Bob would be able to resolve our records too because Bob published our identity in a public record. Bobs friend would simply use "ccc.alice.bob.myself" to resolve our "ccc" record. 299<p>It can continue like this. A friend of Bob would be able to resolve our records too because Bob published our identity in a public record. Bobs friend would simply use "ccc.alice.bob.myself" to resolve our "ccc" record.
@@ -316,19 +316,19 @@ $ gnunet-gns-proxy-setup-ca
316$ gnunet-namestore -z myself -a -e "1 d" -p -t LEHO -n ccc -C www.ccc.de 316$ gnunet-namestore -z myself -a -e "1 d" -p -t LEHO -n ccc -C www.ccc.de
317</code></p> 317</code></p>
318 318
319Now let's start gnunet-gns-proxy. 319<p>Now let's start gnunet-gns-proxy.</p>
320 320
321<p><code> 321<p><code>
322$ gnunet-gns-proxy 322$ gnunet-gns-proxy
323</code></p> 323</code></p>
324 324
325<p>Our browser has to be configured so it uses our proxy. In firefox we have to set theese options under "about:config":</p> 325<p>Our browser has to be configured so it uses our proxy. In Firefox we have to set theese options under "about:config":</p>
326 326
327<p><code> 327<p><code>
328network.proxy.socks: localhost 328network.proxy.socks: localhost<br>
329network.proxy.socks_port: 7777 329network.proxy.socks_port: 7777<br>
330network.proxy.socks_remote_dns true 330network.proxy.socks_remote_dns true<br>
331network.proxy.socks.type: 1 331network.proxy.socks.type: 1<br>
332</code></p> 332</code></p>
333 333
334<p>Now we should be able to resolve our GNS names in the browser! We just have to type "https://ccc.myself" into the address bar. If our friend Bob prepared his system, too, he can resolve our record by typing "ccc.alice.myself".</p> 334<p>Now we should be able to resolve our GNS names in the browser! We just have to type "https://ccc.myself" into the address bar. If our friend Bob prepared his system, too, he can resolve our record by typing "ccc.alice.myself".</p>