[or-cvs] make the hidden-service section of tor-doc obsolete

[arma@xxxxxxxx]

Update of /home2/or/cvsroot/tor/doc
In directory moria:/home/arma/work/onion/cvs/tor/doc

Modified Files:
	tor-doc.html 
Log Message:
make the hidden-service section of tor-doc obsolete


Index: tor-doc.html
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor-doc.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- tor-doc.html	22 Jul 2005 21:45:21 -0000	1.89
+++ tor-doc.html	23 Jul 2005 11:02:33 -0000	1.90
@@ -378,79 +378,12 @@
 <a name="hidden-service"></a>
 <h2>Configuring a hidden service</h2>
 
-<p>Tor allows clients and servers to offer hidden services. That is,
-you can offer a web server, SSH server, etc., without revealing your IP to its
-users. You can even have your application listen on localhost only, yet
-remote Tor connections can access it. This works via Tor's rendezvous
-point design: both sides build a Tor circuit out, and they meet in
-the middle.</p>
-
-<p>If you're using Tor and <a href="http://www.privoxy.org/";>Privoxy</a>,
-you can <a href="http://6sxoyfb3h2nvok2d.onion/";>go to the hidden wiki</a>
-to see hidden services in action.</p>
-
-<p>To set up a hidden service, edit the middle part of your torrc. (See
-<a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#torrc";>this
-FAQ entry</a> for help.) Then run Tor. It will
-create each HiddenServiceDir you have configured, and it will create a
-'hostname' file which specifies the url (xyz.onion) for that service. You
-can tell people the url, and they can connect to it via their Tor client,
-assuming they're using a proxy (such as Privoxy) that speaks SOCKS 4A.</p>
-
-<p>Let's consider an example.
-Assume you want to set up a hidden service to allow people to access your
-Apache web server through Tor.  By doing this, they can access your server
-but won't know who they are connecting to.  You want clients to use the
-standard port 80 when accessing your server. However, if your Apache
-server is actually running on port 8080 locally, client connections need
-to be redirected.</p>
-
-<p><b>HiddenServiceDir</b> is a directory where Tor will store information
-about that hidden service.  In particular, Tor will create a file here named
-<i>hostname</i> which will tell you the onion URL.  You don't need to add any
-files to this directory.</p>
-
-<p><b>HiddenServicePort</b> is where you specify a virtual port and where
-to redirect connections to this virtual port.  For instance, you tell
-Tor there's a virtual port 80 and then redirect traffic to your local
-webserver at 127.0.0.1:8080.</p>
-
-<p>Example lines from a torrc file</p>
-
-<pre>
-HiddenServiceDir /usr/local/etc/tor/hidden_service/
-HiddenServicePort 80 127.0.0.1:8080
-</pre>
-
-<p>This tells Tor to store its files in <tt>/usr/local/etc/tor/hidden_service/</tt>
-and allow people to connect to your onion address on port 80.  It
-will then redirect requests to your localhost webserver on port 8080.
+<p>
+We've moved this section over to the new <a
+href="http://tor.eff.org/doc/tor-hidden-service.html";>Tor Hidden Service
+Howto</a>. Hope you like it.
 </p>
 
-<p>To let people access your hidden service, look at the file
-<tt>/usr/local/etc/tor/hidden_service/hostname</tt> which will tell you what the
-hostname is (such as xyz.onion).  Then, as long as they have Tor and Privoxy
-configured, they can access your webserver with a web browser by connecting
-to http://xyz.onion/</p>
-
-<p>You can have multiple tor hidden services by repeating Dir and Ports:</p>
-
-<pre>
-HiddenServiceDir /usr/local/etc/tor/hidden_service/
-HiddenServicePort 80 127.0.0.1:8080
-
-HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
-HiddenServicePort 6667 127.0.0.1:6667
-HiddenServicePort 22 127.0.0.1:22
-</pre>
-
-<p>The above example will allow people to connect to the hostname in
-<tt>/usr/local/etc/tor/hidden_service/hostname</tt> for an HTTP server and
-to a different hostname in
-<tt>/usr/local/etc/tor/other_hidden_service/hostname</tt> for an IRC and
-SSH server. To an end user, this appears to be two separate hosts with
-one running an HTTP server and another running an IRC/SSH server.</p>
-
 <a name="own-network"></a>
 <h2>Setting up your own network</h2>