[GNUnet-SVN] r6059 - GNUnet-docs/WWW

[gnunet]

Author: grothoff
Date: 2007-12-29 19:50:01 -0700 (Sat, 29 Dec 2007)
New Revision: 6059

Modified:
   GNUnet-docs/WWW/faq.php3
Log:
fix

Modified: GNUnet-docs/WWW/faq.php3
===================================================================
--- GNUnet-docs/WWW/faq.php3    2007-12-30 02:47:02 UTC (rev 6058)
+++ GNUnet-docs/WWW/faq.php3    2007-12-30 02:50:01 UTC (rev 6059)
@@ -495,12 +495,12 @@
 BP();
 W("GNUnet uses the ports 2086 and 1080 by default.");
 W("Configure your firewall to accept packets to the ports 2086 and 1080 (TCP 
and UDP) for the machine running the GNUnet daemon <tt>gnunetd</tt>.");
-W("If your firewall is a NAT box, forward packets to your GNUnet machine's 
ports 2086 and 1080 and tweak the configuration file gnunetd.conf (sections 
NETWORK, LOAD, UDP, TCP and NAT) to use the external IP of the NAT box.");
+W("If your firewall is a NAT box, forward packets to your GNUnet 
machine&apos;s ports 2086 and 1080 and tweak the configuration file 
gnunetd.conf (sections NETWORK, LOAD, UDP, TCP and NAT) to use the external IP 
of the NAT box.");
 W("Port 2087 is used for communication between <tt>gnunetd</tt> and the client 
tools as <tt>gnunet-gtk</tt>, <tt>gnunet-search</tt> etc.");
 W("There is no need to open port 2087 to the rest of the Internet.");
 P();
-W("Port 2086 is used for GNUnet's own transmission protocol, HTTP encapsulated 
GNUnet packets (\"HTTP transport\") are transmitted through port 1080 by 
default.");
-W("The HTTP transport is not necessarily required and can be disabled in 
GNUnet's configuration file.");
+W("Port 2086 is used for GNUnet&apos;s own transmission protocol, HTTP 
encapsulated GNUnet packets (\"HTTP transport\") are transmitted through port 
1080 by default.");
+W("The HTTP transport is not necessarily required and can be disabled in 
GNUnet&apos;s configuration file.");
 W("Disabling it on firewalled systems is important, because available 
transports are advertised to other peers and activated but broken transports 
result in decreased reachability.");
 EP();
 
@@ -560,7 +560,7 @@
 W("Note that the Debian package list should still be useful for you even if 
you are not running Debian.");
 W("Other distributions are likely to have similar packages.");
 P();
-W("Finally, please note that <tt>configure</tt> will succeed even if a 
suitable version of MySQL or sqLite is not detected.");
+W("Finally, please note that <tt>configure</tt> will succeed even if a 
suitable version of MySQL or SQLite is not detected.");
 W("The reason is, that (theoretically) you might be compiling for a 
client-only system, or you might not care about anonymous file-sharing.");
 W("If you do want to use file-sharing, please read the final lines printed by 
configure to make sure that a suitable database was found.");
 EP();
@@ -846,7 +846,7 @@
 P();
 W("Indexed content is a slightly different story.");
 W("For indexed content, the goal for GNUnet is still to make it difficult for 
the adversary to establish from which machine the content originates 
(anonymity).");
-W("For indexed content GNUnet keeps links to the indexed files, typically in 
<tt>/var/lib/GNUnet/data/shared/</tt>.");
+W("For indexed content GNUnet keeps links to the indexed files, typically in 
<tt>/var/lib/gnunet/data/shared/</tt>.");
 W("GNUnet uses the list to locate the block corresponding to a request.");
 W("Do NOT edit the directory by hand.");
 W("Use <tt>gnunet-unindex</tt> to remove files from the directory.");
@@ -863,17 +863,17 @@
 H4("Why should I insert directories instead of individual files?");
 
 BP();
-W("GNUnet&prime;s ECRS encoding/query strategy doesn&prime;t allow peers to 
benefit from false replies.");
+W("GNUnet&apos;s ECRS encoding/query strategy doesn&apos;t allow peers to 
benefit from false replies.");
 W("Even small blocks of incorrect response data can be detected instantly, 
resulting in no trust gain for the malicious node.");
 W("If you know the correct ECRS URI for the file you want, no intermediate 
node can cheat by false replies.");
 W("However, this leaves the problem of obtaining the URIs in the first place, 
and unfortunately if anyone can insert files under common keywords, false data 
can be inserted as well.");
-W("There doesn&prime;t seem to be any easy solution to this problem.");
+W("There doesn&apos;t seem to be any easy solution to this problem.");
 W("Ranking search results by trust could be one answer in the future.");
 W("Meanwhile, namespaces and directories are a step towards the nonspammable 
direction.");
 P();
 W("Inserting into a namespace requires the user to create a pseudonym first, 
which is equal to a public/private key pair that identifies the namespace.");
 W("(One user can create any number of pseudonyms.)");
-W("Then, pointers to files or directories can be inserted into the 
pseudonym&prime;s namespace, signed by the private key of the pseudonym.");
+W("Then, pointers to files or directories can be inserted into the 
pseudonym&apos;s namespace, signed by the private key of the pseudonym.");
 W("The signed blocks will be verified by each peer before the blocks are 
accepted or passed along.");
 W("The verification works by checking the validity of the cryptographic 
signature against the public key included in the namespace block, and by 
checking that hashing the public key results in the correct namespace 
identifier.");
 W("Thus, only the user with the private key to the namespace can publish into 
it, making it a nonspammable, secure publishing channel that other users can 
limit their searches to.");
@@ -883,7 +883,7 @@
 W("The directories can contain arbitrary number of pointers to namespaces 
(SBlocks), pointers to other directories and pointers to files.");
 W("With directories, users can build networks of content, where not only 
inserted files, but also interesting other content or namespaces can be pointed 
to, just as in WWW.");
 W("Additionally, directories have two nice properties.");
-W("First, they are immutable, meaning that they can&prime;t be tampered with, 
but contain exactly those pointers the publisher intended.");
+W("First, they are immutable, meaning that they can&apos;t be tampered with, 
but contain exactly those pointers the publisher intended.");
 W("The second property is that identical files pointed to by two directories 
waste no additional space, even if the directories were built by separate 
users.");
 W("This contrasts strongly to the case where similar files were archived by 
e.g. zip or tar, which could double the space usage over the network
 without any speedups in retrieval time.");