Browse code

Change hidden -> onion. (See #24285)

Renamed files, made new files with old names for redirects, updated
links to use new URLs.

kat authored on19/11/2017 22:01:11
Showing1 changed files
... ...
@@ -1,258 +1,7 @@
1 1
 ## translation metadata
2 2
 # Revision: $Revision$
3
-# Translation-Priority: 3-low
3
+# Status: obsolete
4 4
 
5
-#include "head.wmi" TITLE="Tor Project: Onion Service Configuration Instructions" CHARSET="UTF-8"
6
-<div id="content" class="clearfix">
7
-  <div id="breadcrumbs">
8
-    <a href="<page index>">Home &raquo; </a>
9
-    <a href="<page docs/documentation>">Documentation &raquo; </a>
10
-    <a href="<page docs/tor-hidden-service>">Tor Onion Service</a>
11
-  </div>
12
-  <div id="maincol">
13
-    <h1>Configuring Onion Services for <a href="<page index>">Tor</a></h1>
14
-    <hr>
5
+#include "head.wmi" TITLE="Redirecting" REDIRECT="docs/tor-onion-service"
15 6
 
16
-    <p>Tor allows clients and relays to offer onion services. That is,
17
-    you can offer a web server, SSH server, etc., without revealing your
18
-    IP address to its users. In fact, because you don't use any public address,
19
-    you can run an onion service from behind your firewall.
20
-    </p>
21
-
22
-    <p>If you have Tor installed, you can see onion services in action
23
-    by visiting this <a href="http://duskgytldkxiuqc6.onion/">sample
24
-    site</a>.
25
-    </p>
26
-
27
-    <p>
28
-    This page describes the steps for setting up your own onion service
29
-    website. For the technical details of how the onion service protocol
30
-    works, see our <a href="<page docs/hidden-services>">onion service
31
-    protocol</a> page.
32
-    </p>
33
-
34
-    <hr>
35
-    <a id="zero"></a>
36
-    <h2><a class="anchor" href="#zero">Step Zero: Get Tor working</a></h2>
37
-    <br>
38
-
39
-    <p>Before you start, you need to make sure:</p>
40
-    <ol>
41
-    <li>Tor is up and running,</li>
42
-    <li>You actually set it up correctly.</li>
43
-    </ol>
44
-
45
-    <p>Windows users should follow the <a
46
-    href="<page docs/tor-doc-windows>">Windows
47
-    howto</a>, OS X users should follow the <a
48
-    href="<page docs/tor-doc-osx>">OS
49
-    X howto</a>, and Linux/BSD/Unix users should follow the <a
50
-    href="<page docs/tor-doc-unix>">Unix howto</a>.
51
-    </p>
52
-
53
-    <hr>
54
-    <a id="one"></a>
55
-    <h2><a class="anchor" href="#one">Step One: Install a web server locally</a></h2>
56
-    <br>
57
-
58
-    <p>
59
-    First, you need to set up a web server locally. Setting up a web
60
-    server can be complex. We're not going to cover how to set up a web
61
-    server here. If you get stuck or want to do more, find a friend who
62
-    can help you. We recommend you install a new separate web server for
63
-    your onion service, since even if you already have one installed,
64
-    you may be using it (or want to use it later) for a normal website.
65
-    </p>
66
-
67
-    <p>
68
-    You need to configure your web server so it doesn't give away any
69
-    information about you, your computer, or your location. Be sure to
70
-    bind the web server only to localhost (if people could get to it
71
-    directly, they could confirm that your computer is the one offering
72
-    the onion service). Be sure that its error messages don't list
73
-    your hostname or other hints. Consider putting the web server in a
74
-    sandbox or VM to limit the damage from code vulnerabilities.
75
-    </p>
76
-
77
-    <p>
78
-    Once your web server is set up, make
79
-    sure it works: open your browser and go to <a
80
-    href="http://localhost:8080/">http://localhost:8080/</a>, where
81
-    8080 is the webserver port you chose during setup (you can choose any
82
-    port, 8080 is just an example). Then try putting a file in the main
83
-    html directory, and make sure it shows up when you access the site.
84
-    </p>
85
-
86
-    <hr>
87
-    <a id="two"></a>
88
-    <h2><a class="anchor" href="#two">Step Two: Configure your onion service</a></h2>
89
-    <br>
90
-
91
-    <p>Next, you need to configure your onion service to point to your
92
-    local web server.
93
-    </p>
94
-
95
-    <p>First, open your torrc file in your favorite text editor. (See
96
-    <a href="<page docs/faq>#torrc">the torrc FAQ entry</a> to learn
97
-    what this means.) Go to the middle section and look for the line</p>
98
-
99
-    <pre>
100
-    \############### This section is just for location-hidden services ###
101
-    </pre>
102
-
103
-    <p>
104
-    This section of the file consists of groups of lines, each representing
105
-    one onion service. Right now they are all commented out (the lines
106
-    start with #), so onion services are disabled. Each group of lines
107
-    consists of one <var>HiddenServiceDir</var> line, and one or more
108
-    <var>HiddenServicePort</var> lines:</p>
109
-    <ul>
110
-	<li><var>HiddenServiceDir</var> is a directory where Tor will store
111
-	information about that onion service.  In particular, Tor will create a
112
-	file here named <var>hostname</var> which will tell you the onion URL.  You
113
-	don't need to add any files to this directory. Make sure this is not the
114
-	same directory as the hidserv directory you created when setting up thttpd,
115
-	as your HiddenServiceDir contains secret information!</li>
116
-	<li><var>HiddenServicePort</var> lets you specify a virtual port (that is,
117
-	what port people accessing the onion service will think they're using) and
118
-	an IP address and port for redirecting connections to this virtual
119
-	port.</li> </ul>
120
-
121
-    <p>Add the following lines to your torrc:
122
-    </p>
123
-
124
-    <pre>
125
-    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
126
-    HiddenServicePort 80 127.0.0.1:8080
127
-    </pre>
128
-
129
-	<p>You're going to want to change the <var>HiddenServiceDir</var> line, so
130
-	it points to an actual directory that is readable/writeable by the user
131
-	that will be running Tor. The above line should work if you're using the OS
132
-	X Tor package. On Unix, try "/home/username/hidden_service/" and fill in
133
-	your own username in place of "username". On Windows you might pick:</p>
134
-	<pre> HiddenServiceDir C:\Users\username\Documents\tor\hidden_service
135
-	HiddenServicePort 80 127.0.0.1:8080 </pre>
136
-
137
-    <p>Note that since 0.2.6, both <var>SocksPort</var> and <var>HiddenServicePort</var> support Unix sockets. 
138
-    This means that you can point the <var>HiddenServicePort</var> to a Unix socket:</p>
139
-    <pre>
140
-    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
141
-    HiddenServicePort 80 unix:/path/to/socket
142
-    </pre>
143
-
144
-    <p>Now save the torrc and restart your tor.</p>
145
-
146
-	<p>If Tor starts up again, great. Otherwise, something is wrong. First look
147
-	at your logfiles for hints. It will print some warnings or error messages.
148
-	That should give you an idea what went wrong. Typically there are typos in
149
-	the torrc or wrong directory permissions (See <a href="<page
150
-	docs/faq>#Logs">the logging FAQ entry</a> if you don't know how to enable
151
-	or find your log file.) </p>
152
-
153
-	<p>When Tor starts, it will automatically create the
154
-	<var>HiddenServiceDir</var> that you specified (if necessary), and it will
155
-	create two files there.</p>
156
-
157
-    <dl>
158
-    <dt><var>private_key</var></dt>
159
-    <dd>First, Tor will generate a new public/private keypair for your onion
160
-    service. It is written into a file called "private_key". Don't share this key
161
-    with others -- if you do they will be able to impersonate your onion
162
-    service.</dd>
163
-    <dt><var>hostname</var></dt>
164
-    <dd>The other file Tor will create is called "hostname". This contains
165
-    a short summary of your public key -- it will look something like
166
-    <tt>duskgytldkxiuqc6.onion</tt>. This is the public name for your service,
167
-    and you can tell it to people, publish it on websites, put it on business
168
-    cards, etc.</dd>
169
-    </dl>
170
-
171
-    <p>If Tor runs as a different user than you, for example on
172
-    OS X, Debian, or Red Hat, then you may need to become root to be able
173
-    to view these files.</p>
174
-
175
-    <p>Now that you've restarted Tor, it is busy picking introduction points
176
-    in the Tor network, and generating an <em>onion service
177
-    descriptor</em>. This is a signed list of introduction points along with
178
-    the service's full public key. It anonymously publishes this descriptor
179
-    to the directory servers, and other people anonymously fetch it from the
180
-    directory servers when they're trying to access your service.
181
-    </p>
182
-
183
-    <p>Try it now: paste the contents of the hostname file into your web
184
-    browser. If it works, you'll get the html page you set up in step one.
185
-    If it doesn't work, look in your logs for some hints, and keep playing
186
-    with it until it works.
187
-    </p>
188
-
189
-    <hr>
190
-    <a id="three"></a>
191
-    <h2><a class="anchor" href="#three">Step Three: More advanced tips</a></h2>
192
-    <br>
193
-
194
-    <p>If you plan to keep your service available for a long time, you might
195
-    want to make a backup copy of the <var>private_key</var> file somewhere.
196
-    </p>
197
-
198
-    <p>If you want to forward multiple virtual ports for a single onion
199
-    service, just add more <var>HiddenServicePort</var> lines.
200
-    If you want to run multiple onion services from the same Tor
201
-    client, just add another <var>HiddenServiceDir</var> line. All the following
202
-    <var>HiddenServicePort</var> lines refer to this <var>HiddenServiceDir</var> line, until
203
-    you add another <var>HiddenServiceDir</var> line:
204
-    </p>
205
-
206
-    <pre>
207
-    HiddenServiceDir /usr/local/etc/tor/hidden_service/
208
-    HiddenServicePort 80 127.0.0.1:8080
209
-
210
-    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
211
-    HiddenServicePort 6667 127.0.0.1:6667
212
-    HiddenServicePort 22 127.0.0.1:22
213
-    </pre>
214
-
215
-    <p>Onion services operators need to practice proper operational security
216
-    and system administration to maintain security. For some security
217
-    suggestions please make sure you read over Riseup's <a
218
-	href="https://help.riseup.net/en/security/network-security/tor/onionservices-best-practices">"Tor
219
-	Hidden (Onion) Services Best Practices" document</a>. Also, here are some
220
-	more anonymity issues you should keep in mind:
221
-
222
-    </p>
223
-    <ul>
224
-    <li>As mentioned above, be careful of letting your web server reveal
225
-    identifying information about you, your computer, or your location.
226
-    For example, readers can probably determine whether it's thttpd or
227
-    Apache, and learn something about your operating system.</li>
228
-    <li>If your computer isn't online all the time, your onion service
229
-    won't be either. This leaks information to an observant adversary.</li>
230
-    <li>It is generally a better idea to host onion services on a Tor client
231
-    rather than a Tor relay, since relay uptime and other properties are
232
-    publicly visible.</li>
233
-    <li>The longer an onion service is online, the higher the risk that its
234
-    location is discovered. The most prominent attacks are building a
235
-    profile of the onion service's availability and matching induced
236
-    traffic patterns.</li>
237
-    </ul>
238
-
239
-    <p>Another common issue is whether to use HTTPS on your relay or
240
-    not. Have a look at this <a
241
-    href="https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs">post</a> on the Tor Blog to learn more about these issues.
242
-    </p>
243
-
244
-    <p>Finally, feel free to use the <a
245
-    href="https://lists.torproject.org/pipermail/tor-onions/">[tor-onions]
246
-    mailing list</a> to discuss the secure administration and operation of
247
-    Tor onion services.</p>
248
-
249
-  </div>
250
-  <!-- END MAINCOL -->
251
-  <div id = "sidecol">
252
-#include "side.wmi"
253
-#include "info.wmi"
254
-  </div>
255
-  <!-- END SIDECOL -->
256
-</div>
257
-<!-- END CONTENT -->
258 7
 #include <foot.wmi>
Browse code

Change hidden service to onion service. (See #24285)

kat authored on16/11/2017 19:08:34
Showing1 changed files
... ...
@@ -2,32 +2,32 @@
2 2
 # Revision: $Revision$
3 3
 # Translation-Priority: 3-low
4 4
 
5
-#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
5
+#include "head.wmi" TITLE="Tor Project: Onion Service Configuration Instructions" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8 8
     <a href="<page index>">Home &raquo; </a>
9 9
     <a href="<page docs/documentation>">Documentation &raquo; </a>
10
-    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
10
+    <a href="<page docs/tor-hidden-service>">Tor Onion Service</a>
11 11
   </div>
12 12
   <div id="maincol">
13
-    <h1>Configuring Hidden Services for <a href="<page index>">Tor</a></h1>
13
+    <h1>Configuring Onion Services for <a href="<page index>">Tor</a></h1>
14 14
     <hr>
15 15
 
16
-    <p>Tor allows clients and relays to offer hidden services. That is,
16
+    <p>Tor allows clients and relays to offer onion services. That is,
17 17
     you can offer a web server, SSH server, etc., without revealing your
18 18
     IP address to its users. In fact, because you don't use any public address,
19
-    you can run a hidden service from behind your firewall.
19
+    you can run an onion service from behind your firewall.
20 20
     </p>
21 21
 
22
-    <p>If you have Tor installed, you can see hidden services in action
22
+    <p>If you have Tor installed, you can see onion services in action
23 23
     by visiting this <a href="http://duskgytldkxiuqc6.onion/">sample
24 24
     site</a>.
25 25
     </p>
26 26
 
27 27
     <p>
28
-    This page describes the steps for setting up your own hidden service
29
-    website. For the technical details of how the hidden service protocol
30
-    works, see our <a href="<page docs/hidden-services>">hidden service
28
+    This page describes the steps for setting up your own onion service
29
+    website. For the technical details of how the onion service protocol
30
+    works, see our <a href="<page docs/hidden-services>">onion service
31 31
     protocol</a> page.
32 32
     </p>
33 33
 
... ...
@@ -57,10 +57,10 @@
57 57
 
58 58
     <p>
59 59
     First, you need to set up a web server locally. Setting up a web
60
-    server can be complex. We're not going to cover how to setup a web
60
+    server can be complex. We're not going to cover how to set up a web
61 61
     server here. If you get stuck or want to do more, find a friend who
62 62
     can help you. We recommend you install a new separate web server for
63
-    your hidden service, since even if you already have one installed,
63
+    your onion service, since even if you already have one installed,
64 64
     you may be using it (or want to use it later) for a normal website.
65 65
     </p>
66 66
 
... ...
@@ -69,7 +69,7 @@
69 69
     information about you, your computer, or your location. Be sure to
70 70
     bind the web server only to localhost (if people could get to it
71 71
     directly, they could confirm that your computer is the one offering
72
-    the hidden service). Be sure that its error messages don't list
72
+    the onion service). Be sure that its error messages don't list
73 73
     your hostname or other hints. Consider putting the web server in a
74 74
     sandbox or VM to limit the damage from code vulnerabilities.
75 75
     </p>
... ...
@@ -85,10 +85,10 @@
85 85
 
86 86
     <hr>
87 87
     <a id="two"></a>
88
-    <h2><a class="anchor" href="#two">Step Two: Configure your hidden service</a></h2>
88
+    <h2><a class="anchor" href="#two">Step Two: Configure your onion service</a></h2>
89 89
     <br>
90 90
 
91
-    <p>Next, you need to configure your hidden service to point to your
91
+    <p>Next, you need to configure your onion service to point to your
92 92
     local web server.
93 93
     </p>
94 94
 
... ...
@@ -102,21 +102,21 @@
102 102
 
103 103
     <p>
104 104
     This section of the file consists of groups of lines, each representing
105
-    one hidden service. Right now they are all commented out (the lines
106
-    start with #), so hidden services are disabled. Each group of lines
105
+    one onion service. Right now they are all commented out (the lines
106
+    start with #), so onion services are disabled. Each group of lines
107 107
     consists of one <var>HiddenServiceDir</var> line, and one or more
108 108
     <var>HiddenServicePort</var> lines:</p>
109 109
     <ul>
110
-    <li><var>HiddenServiceDir</var> is a directory where Tor will store information
111
-    about that hidden service.  In particular, Tor will create a file here named
112
-    <var>hostname</var> which will tell you the onion URL.  You don't need to
113
-    add any files to this directory. Make sure this is not the same directory
114
-    as the hidserv directory you created when setting up thttpd, as your
115
-    HiddenServiceDir contains secret information!</li>
116
-    <li><var>HiddenServicePort</var> lets you specify a virtual port (that is, what
117
-    port people accessing the hidden service will think they're using) and an
118
-    IP address and port for redirecting connections to this virtual port.</li>
119
-    </ul>
110
+	<li><var>HiddenServiceDir</var> is a directory where Tor will store
111
+	information about that onion service.  In particular, Tor will create a
112
+	file here named <var>hostname</var> which will tell you the onion URL.  You
113
+	don't need to add any files to this directory. Make sure this is not the
114
+	same directory as the hidserv directory you created when setting up thttpd,
115
+	as your HiddenServiceDir contains secret information!</li>
116
+	<li><var>HiddenServicePort</var> lets you specify a virtual port (that is,
117
+	what port people accessing the onion service will think they're using) and
118
+	an IP address and port for redirecting connections to this virtual
119
+	port.</li> </ul>
120 120
 
121 121
     <p>Add the following lines to your torrc:
122 122
     </p>
... ...
@@ -126,17 +126,15 @@
126 126
     HiddenServicePort 80 127.0.0.1:8080
127 127
     </pre>
128 128
 
129
-    <p>You're going to want to change the <var>HiddenServiceDir</var> line, so it points
130
-    to an actual directory that is readable/writeable by the user that will
131
-    be running Tor. The above line should work if you're using the OS X Tor
132
-    package. On Unix, try "/home/username/hidden_service/" and fill in your own
133
-    username in place of "username". On Windows you might pick:</p>
134
-    <pre>
135
-    HiddenServiceDir C:\Users\username\Documents\tor\hidden_service
136
-    HiddenServicePort 80 127.0.0.1:8080
137
-    </pre>
129
+	<p>You're going to want to change the <var>HiddenServiceDir</var> line, so
130
+	it points to an actual directory that is readable/writeable by the user
131
+	that will be running Tor. The above line should work if you're using the OS
132
+	X Tor package. On Unix, try "/home/username/hidden_service/" and fill in
133
+	your own username in place of "username". On Windows you might pick:</p>
134
+	<pre> HiddenServiceDir C:\Users\username\Documents\tor\hidden_service
135
+	HiddenServicePort 80 127.0.0.1:8080 </pre>
138 136
 
139
-    <p>Note that since 0.2.6, both <var>SocksPort</var> and <var>HiddenServicePort</var> support Unix socket. 
137
+    <p>Note that since 0.2.6, both <var>SocksPort</var> and <var>HiddenServicePort</var> support Unix sockets. 
140 138
     This means that you can point the <var>HiddenServicePort</var> to a Unix socket:</p>
141 139
     <pre>
142 140
     HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
... ...
@@ -145,22 +143,22 @@
145 143
 
146 144
     <p>Now save the torrc and restart your tor.</p>
147 145
 
148
-    <p>If Tor starts up again, great. Otherwise, something is wrong. First look at
149
-    your logfiles for hints. It will print some warnings or error messages. That
150
-    should give you an idea what went wrong. Typically there are typos in the torrc
151
-    or wrong directory permissions (See <a href="<page docs/faq>#Logs">the
152
-    logging FAQ entry</a> if you don't know how to enable or find your
153
-    log file.)
154
-    </p>
146
+	<p>If Tor starts up again, great. Otherwise, something is wrong. First look
147
+	at your logfiles for hints. It will print some warnings or error messages.
148
+	That should give you an idea what went wrong. Typically there are typos in
149
+	the torrc or wrong directory permissions (See <a href="<page
150
+	docs/faq>#Logs">the logging FAQ entry</a> if you don't know how to enable
151
+	or find your log file.) </p>
155 152
 
156
-    <p>When Tor starts, it will automatically create the <var>HiddenServiceDir</var>
157
-    that you specified (if necessary), and it will create two files there.</p>
153
+	<p>When Tor starts, it will automatically create the
154
+	<var>HiddenServiceDir</var> that you specified (if necessary), and it will
155
+	create two files there.</p>
158 156
 
159 157
     <dl>
160 158
     <dt><var>private_key</var></dt>
161
-    <dd>First, Tor will generate a new public/private keypair for your hidden
159
+    <dd>First, Tor will generate a new public/private keypair for your onion
162 160
     service. It is written into a file called "private_key". Don't share this key
163
-    with others -- if you do they will be able to impersonate your hidden
161
+    with others -- if you do they will be able to impersonate your onion
164 162
     service.</dd>
165 163
     <dt><var>hostname</var></dt>
166 164
     <dd>The other file Tor will create is called "hostname". This contains
... ...
@@ -175,7 +173,7 @@
175 173
     to view these files.</p>
176 174
 
177 175
     <p>Now that you've restarted Tor, it is busy picking introduction points
178
-    in the Tor network, and generating a <em>hidden service
176
+    in the Tor network, and generating an <em>onion service
179 177
     descriptor</em>. This is a signed list of introduction points along with
180 178
     the service's full public key. It anonymously publishes this descriptor
181 179
     to the directory servers, and other people anonymously fetch it from the
... ...
@@ -197,9 +195,9 @@
197 195
     want to make a backup copy of the <var>private_key</var> file somewhere.
198 196
     </p>
199 197
 
200
-    <p>If you want to forward multiple virtual ports for a single hidden
198
+    <p>If you want to forward multiple virtual ports for a single onion
201 199
     service, just add more <var>HiddenServicePort</var> lines.
202
-    If you want to run multiple hidden services from the same Tor
200
+    If you want to run multiple onion services from the same Tor
203 201
     client, just add another <var>HiddenServiceDir</var> line. All the following
204 202
     <var>HiddenServicePort</var> lines refer to this <var>HiddenServiceDir</var> line, until
205 203
     you add another <var>HiddenServiceDir</var> line:
... ...
@@ -214,12 +212,12 @@
214 212
     HiddenServicePort 22 127.0.0.1:22
215 213
     </pre>
216 214
 
217
-    <p>Hidden services operators need to practice proper operational security
215
+    <p>Onion services operators need to practice proper operational security
218 216
     and system administration to maintain security. For some security
219 217
     suggestions please make sure you read over Riseup's <a
220
-    href="https://help.riseup.net/en/security/network-security/tor/onionservices-best-practices">"Tor
221
-    hidden services best practices" document</a>. Also, here are some more
222
-    anonymity issues you should keep in mind:
218
+	href="https://help.riseup.net/en/security/network-security/tor/onionservices-best-practices">"Tor
219
+	Hidden (Onion) Services Best Practices" document</a>. Also, here are some
220
+	more anonymity issues you should keep in mind:
223 221
 
224 222
     </p>
225 223
     <ul>
... ...
@@ -227,27 +225,26 @@
227 225
     identifying information about you, your computer, or your location.
228 226
     For example, readers can probably determine whether it's thttpd or
229 227
     Apache, and learn something about your operating system.</li>
230
-    <li>If your computer isn't online all the time, your hidden service
228
+    <li>If your computer isn't online all the time, your onion service
231 229
     won't be either. This leaks information to an observant adversary.</li>
232
-    <li>It is generally a better idea to host hidden services on a Tor client
230
+    <li>It is generally a better idea to host onion services on a Tor client
233 231
     rather than a Tor relay, since relay uptime and other properties are
234 232
     publicly visible.</li>
235
-    <li>The longer a hidden is online, the higher the risk that its
233
+    <li>The longer an onion service is online, the higher the risk that its
236 234
     location is discovered. The most prominent attacks are building a
237
-    profile of the hidden service's availability and matching induced
235
+    profile of the onion service's availability and matching induced
238 236
     traffic patterns.</li>
239 237
     </ul>
240 238
 
241 239
     <p>Another common issue is whether to use HTTPS on your relay or
242 240
     not. Have a look at this <a
243
-    href="https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs">post</a>
244
-    on the Tor Blog to learn more about these issues.
241
+    href="https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs">post</a> on the Tor Blog to learn more about these issues.
245 242
     </p>
246 243
 
247 244
     <p>Finally, feel free to use the <a
248 245
     href="https://lists.torproject.org/pipermail/tor-onions/">[tor-onions]
249 246
     mailing list</a> to discuss the secure administration and operation of
250
-    Tor hidden services.</p>
247
+    Tor onion services.</p>
251 248
 
252 249
   </div>
253 250
   <!-- END MAINCOL -->
Browse code

Update hidden service doc w/ unix socket info

hiromipaw authored on08/08/2017 11:26:56
Showing1 changed files
... ...
@@ -136,6 +136,13 @@
136 136
     HiddenServicePort 80 127.0.0.1:8080
137 137
     </pre>
138 138
 
139
+    <p>Note that since 0.2.6, both <var>SocksPort</var> and <var>HiddenServicePort</var> support Unix socket. 
140
+    This means that you can point the <var>HiddenServicePort</var> to a Unix socket:</p>
141
+    <pre>
142
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
143
+    HiddenServicePort 80 unix:/path/to/socket
144
+    </pre>
145
+
139 146
     <p>Now save the torrc and restart your tor.</p>
140 147
 
141 148
     <p>If Tor starts up again, great. Otherwise, something is wrong. First look at
Browse code

HS configuration page: Mention riseup's guide and [tor-onions].

George Kadianakis authored on05/02/2016 19:29:17
Showing1 changed files
... ...
@@ -207,7 +207,13 @@
207 207
     HiddenServicePort 22 127.0.0.1:22
208 208
     </pre>
209 209
 
210
-    <p>There are some anonymity issues you should keep in mind too:
210
+    <p>Hidden services operators need to practice proper operational security
211
+    and system administration to maintain security. For some security
212
+    suggestions please make sure you read over Riseup's <a
213
+    href="https://help.riseup.net/en/security/network-security/tor/onionservices-best-practices">"Tor
214
+    hidden services best practices" document</a>. Also, here are some more
215
+    anonymity issues you should keep in mind:
216
+
211 217
     </p>
212 218
     <ul>
213 219
     <li>As mentioned above, be careful of letting your web server reveal
... ...
@@ -230,6 +236,12 @@
230 236
     href="https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs">post</a>
231 237
     on the Tor Blog to learn more about these issues.
232 238
     </p>
239
+
240
+    <p>Finally, feel free to use the <a
241
+    href="https://lists.torproject.org/pipermail/tor-onions/">[tor-onions]
242
+    mailing list</a> to discuss the secure administration and operation of
243
+    Tor hidden services.</p>
244
+
233 245
   </div>
234 246
   <!-- END MAINCOL -->
235 247
   <div id = "sidecol">
Browse code

Link to blog post to document https hs issues

Sebastian Hahn authored on11/02/2015 06:46:56
Showing1 changed files
... ...
@@ -216,16 +216,20 @@
216 216
     Apache, and learn something about your operating system.</li>
217 217
     <li>If your computer isn't online all the time, your hidden service
218 218
     won't be either. This leaks information to an observant adversary.</li>
219
-    <li>It is generally a better idea to host hidden services on a Tor client 
219
+    <li>It is generally a better idea to host hidden services on a Tor client
220 220
     rather than a Tor relay, since relay uptime and other properties are
221 221
     publicly visible.</li>
222
-    <!-- increased risks over time -->
222
+    <li>The longer a hidden is online, the higher the risk that its
223
+    location is discovered. The most prominent attacks are building a
224
+    profile of the hidden service's availability and matching induced
225
+    traffic patterns.</li>
223 226
     </ul>
224 227
 
225
-    <hr>
226
-
227
-    <p>If you have suggestions for improving this document, please <a
228
-    href="<page about/contact>">send them to us</a>. Thanks!</p>
228
+    <p>Another common issue is whether to use HTTPS on your relay or
229
+    not. Have a look at this <a
230
+    href="https://blog.torproject.org/blog/facebook-hidden-services-and-https-certs">post</a>
231
+    on the Tor Blog to learn more about these issues.
232
+    </p>
229 233
   </div>
230 234
   <!-- END MAINCOL -->
231 235
   <div id = "sidecol">
... ...
@@ -235,4 +239,4 @@
235 239
   <!-- END SIDECOL -->
236 240
 </div>
237 241
 <!-- END CONTENT -->
238
-#include <foot.wmi>  
242
+#include <foot.wmi>
Browse code

put back one, since it doesn't need to be rotated

Roger Dingledine authored on19/04/2014 04:19:51
Showing1 changed files
... ...
@@ -19,6 +19,11 @@
19 19
     you can run a hidden service from behind your firewall.
20 20
     </p>
21 21
 
22
+    <p>If you have Tor installed, you can see hidden services in action
23
+    by visiting this <a href="http://duskgytldkxiuqc6.onion/">sample
24
+    site</a>.
25
+    </p>
26
+
22 27
     <p>
23 28
     This page describes the steps for setting up your own hidden service
24 29
     website. For the technical details of how the hidden service protocol
Browse code

remove sample hidden services since keys need to be rotated.

Andrew Lewman authored on19/04/2014 03:30:22
Showing1 changed files
... ...
@@ -19,20 +19,6 @@
19 19
     you can run a hidden service from behind your firewall.
20 20
     </p>
21 21
 
22
-    <p>If you have Tor installed, you can see hidden services
23
-    in action by visiting one of our official hidden services:
24
-    <ul>
25
-    <li><a href="http://idnxcnkne4qt76tg.onion/">The Tor Project Website</a></li>
26
-    <li><a href="http://j6im4v42ur6dpic3.onion/">The Tor Package Archive</a></li>
27
-    <li><a href="http://p3igkncehackjtib.onion/">The Tor Media Archive</a></li>
28
-    </ul>
29
-
30
-    Others run reliable hidden services, such as <a
31
-    href="http://3g2upl4pq6kufc4m.onion/">The Duck Duck
32
-    Go</a> search engine and someone hosting a <a
33
-    href="http://duskgytldkxiuqc6.onion/">sample site</a>.
34
-    </p>
35
-
36 22
     <p>
37 23
     This page describes the steps for setting up your own hidden service
38 24
     website. For the technical details of how the hidden service protocol
Browse code

HS websites are also actual websites. changed to normal

Moritz Bartl authored on16/06/2013 14:34:03
Showing1 changed files
... ...
@@ -70,7 +70,7 @@
70 70
     server here. If you get stuck or want to do more, find a friend who
71 71
     can help you. We recommend you install a new separate web server for
72 72
     your hidden service, since even if you already have one installed,
73
-    you may be using it (or want to use it later) for an actual website.
73
+    you may be using it (or want to use it later) for a normal website.
74 74
     </p>
75 75
 
76 76
     <p>
Browse code

recommend hosting HS on tor clients rather than tor relays

Moritz Bartl authored on07/04/2013 21:22:56
Showing1 changed files
... ...
@@ -225,6 +225,9 @@
225 225
     Apache, and learn something about your operating system.</li>
226 226
     <li>If your computer isn't online all the time, your hidden service
227 227
     won't be either. This leaks information to an observant adversary.</li>
228
+    <li>It is generally a better idea to host hidden services on a Tor client 
229
+    rather than a Tor relay, since relay uptime and other properties are
230
+    publicly visible.</li>
228 231
     <!-- increased risks over time -->
229 232
     </ul>
230 233
 
Browse code

finish the process of not recommending a particular web server for hidden service operators

Roger Dingledine authored on23/04/2012 06:27:55
Showing1 changed files
... ...
@@ -73,6 +73,16 @@
73 73
     you may be using it (or want to use it later) for an actual website.
74 74
     </p>
75 75
 
76
+    <p>
77
+    You need to configure your web server so it doesn't give away any
78
+    information about you, your computer, or your location. Be sure to
79
+    bind the web server only to localhost (if people could get to it
80
+    directly, they could confirm that your computer is the one offering
81
+    the hidden service). Be sure that its error messages don't list
82
+    your hostname or other hints. Consider putting the web server in a
83
+    sandbox or VM to limit the damage from code vulnerabilities.
84
+    </p>
85
+
76 86
     <p>
77 87
     Once your web server is set up, make
78 88
     sure it works: open your browser and go to <a
... ...
@@ -80,10 +90,6 @@
80 90
     8080 is the webserver port you chose during setup (you can choose any
81 91
     port, 8080 is just an example). Then try putting a file in the main
82 92
     html directory, and make sure it shows up when you access the site.
83
-    The reason we bind the web server only to localhost is to make sure
84
-    it isn't publically accessible. If people could get to it directly,
85
-    they could confirm that your computer is the one offering the
86
-    hidden service.
87 93
     </p>
88 94
 
89 95
     <hr>
... ...
@@ -193,16 +199,6 @@
193 199
     want to make a backup copy of the <var>private_key</var> file somewhere.
194 200
     </p>
195 201
 
196
-    <p>We avoided recommending Apache above, a) because many people might
197
-    already be running it for a public web server on their computer, and b)
198
-    because it's big
199
-    and has lots of places where it might reveal your IP address or other
200
-    identifying information, for example in 404 pages. For people who need
201
-    more functionality, though, Apache may be the right answer. Can
202
-    somebody make us a checklist of ways to lock down your Apache when you're
203
-    using it as a hidden service? Savant probably has these problems too.
204
-    </p>
205
-
206 202
     <p>If you want to forward multiple virtual ports for a single hidden
207 203
     service, just add more <var>HiddenServicePort</var> lines.
208 204
     If you want to run multiple hidden services from the same Tor
Browse code

Delete the troubleshooting paragraph that I wrote back when people were commonly not configuring their browsers to use a proxy. Now that everybody is using Torbutton, "you didn't configure your browser correctly" shouldn't be the issue. And also the faq entry no longer helps you configure your browser correctly.

Roger Dingledine authored on23/04/2012 06:12:22
Showing1 changed files
... ...
@@ -32,14 +32,6 @@
32 32
     Go</a> search engine and someone hosting a <a
33 33
     href="http://duskgytldkxiuqc6.onion/">sample site</a>.
34 34
     </p>
35
-    <p>
36
-    It will typically take 10-60 seconds to load (or to decide that the
37
-    service is currently unreachable). If it fails immediately and your
38
-    browser pops up an alert saying that "www.duskgytldkxiuqc6.onion could
39
-    not be found, please check the name and try again" then you haven't
40
-    configured Tor correctly; see <a href="<page docs/faq>#DoesntWork">the
41
-    it-doesn't-work FAQ entry</a> for some help.
42
-    </p>
43 35
 
44 36
     <p>
45 37
     This page describes the steps for setting up your own hidden service
Browse code

clean up the directions some more.

Andrew Lewman authored on16/04/2012 16:11:26
Showing1 changed files
... ...
@@ -12,13 +12,13 @@
12 12
   <div id="maincol">
13 13
     <h1>Configuring Hidden Services for <a href="<page index>">Tor</a></h1>
14 14
     <hr>
15
-    
15
+
16 16
     <p>Tor allows clients and relays to offer hidden services. That is,
17 17
     you can offer a web server, SSH server, etc., without revealing your
18 18
     IP address to its users. In fact, because you don't use any public address,
19 19
     you can run a hidden service from behind your firewall.
20 20
     </p>
21
-    
21
+
22 22
     <p>If you have Tor installed, you can see hidden services
23 23
     in action by visiting one of our official hidden services:
24 24
     <ul>
... ...
@@ -42,7 +42,7 @@
42 42
     </p>
43 43
 
44 44
     <p>
45
-    This howto describes the steps for setting up your own hidden service
45
+    This page describes the steps for setting up your own hidden service
46 46
     website. For the technical details of how the hidden service protocol
47 47
     works, see our <a href="<page docs/hidden-services>">hidden service
48 48
     protocol</a> page.
... ...
@@ -52,14 +52,13 @@
52 52
     <a id="zero"></a>
53 53
     <h2><a class="anchor" href="#zero">Step Zero: Get Tor working</a></h2>
54 54
     <br>
55
-    
55
+
56 56
     <p>Before you start, you need to make sure:</p>
57 57
     <ol>
58 58
     <li>Tor is up and running,</li>
59 59
     <li>You actually set it up correctly.</li>
60 60
     </ol>
61
-    
62
-    
61
+
63 62
     <p>Windows users should follow the <a
64 63
     href="<page docs/tor-doc-windows>">Windows
65 64
     howto</a>, OS X users should follow the <a
... ...
@@ -72,46 +71,46 @@
72 71
     <a id="one"></a>
73 72
     <h2><a class="anchor" href="#one">Step One: Install a web server locally</a></h2>
74 73
     <br>
75
-    
74
+
76 75
     <p>
77 76
     First, you need to set up a web server locally. Setting up a web
78
-    server can be tricky, so we're just going to go over a few basics
79
-    here. If you get stuck or want to do more, find a friend who can
80
-    help you. We recommend you install a new separate web server for
77
+    server can be complex. We're not going to cover how to setup a web
78
+    server here. If you get stuck or want to do more, find a friend who
79
+    can help you. We recommend you install a new separate web server for
81 80
     your hidden service, since even if you already have one installed,
82 81
     you may be using it (or want to use it later) for an actual website.
83 82
     </p>
84 83
 
85 84
     <p>
86
-    Once you've got your web server set up, make
85
+    Once your web server is set up, make
87 86
     sure it works: open your browser and go to <a
88
-    href="http://localhost:5222/">http://localhost:5222/</a>, where
89
-    5222 is the port that you picked above. Then try putting a file in
90
-    the main html directory, and make sure it shows up when you access
91
-    the site.  The reason we bind the web server only to localhost is to
92
-    make sure it isn't publically accessible. If people could get to it
93
-    directly, they could confirm that your computer is the one offering
94
-    the hidden service.
87
+    href="http://localhost:8080/">http://localhost:8080/</a>, where
88
+    8080 is the webserver port you chose during setup (you can choose any
89
+    port, 8080 is just an example). Then try putting a file in the main
90
+    html directory, and make sure it shows up when you access the site.
91
+    The reason we bind the web server only to localhost is to make sure
92
+    it isn't publically accessible. If people could get to it directly,
93
+    they could confirm that your computer is the one offering the
94
+    hidden service.
95 95
     </p>
96 96
 
97 97
     <hr>
98 98
     <a id="two"></a>
99 99
     <h2><a class="anchor" href="#two">Step Two: Configure your hidden service</a></h2>
100 100
     <br>
101
-    
101
+
102 102
     <p>Next, you need to configure your hidden service to point to your
103 103
     local web server.
104 104
     </p>
105
-    
106
-    <p>First, open your torrc file in your favorite text editor. (See <a
107
-    href="<page docs/faq>#torrc">the
108
-    torrc FAQ entry</a> to learn what this means.) Go to the middle section and
109
-    look for the line</p>
110
-    
105
+
106
+    <p>First, open your torrc file in your favorite text editor. (See
107
+    <a href="<page docs/faq>#torrc">the torrc FAQ entry</a> to learn
108
+    what this means.) Go to the middle section and look for the line</p>
109
+
111 110
     <pre>
112 111
     \############### This section is just for location-hidden services ###
113 112
     </pre>
114
-    
113
+
115 114
     <p>
116 115
     This section of the file consists of groups of lines, each representing
117 116
     one hidden service. Right now they are all commented out (the lines
... ...
@@ -129,15 +128,15 @@
129 128
     port people accessing the hidden service will think they're using) and an
130 129
     IP address and port for redirecting connections to this virtual port.</li>
131 130
     </ul>
132
-    
131
+
133 132
     <p>Add the following lines to your torrc:
134 133
     </p>
135
-    
134
+
136 135
     <pre>
137 136
     HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
138
-    HiddenServicePort 80 127.0.0.1:5222
137
+    HiddenServicePort 80 127.0.0.1:8080
139 138
     </pre>
140
-    
139
+
141 140
     <p>You're going to want to change the <var>HiddenServiceDir</var> line, so it points
142 141
     to an actual directory that is readable/writeable by the user that will
143 142
     be running Tor. The above line should work if you're using the OS X Tor
... ...
@@ -145,13 +144,11 @@
145 144
     username in place of "username". On Windows you might pick:</p>
146 145
     <pre>
147 146
     HiddenServiceDir C:\Users\username\Documents\tor\hidden_service
148
-    HiddenServicePort 80 127.0.0.1:5222
147
+    HiddenServicePort 80 127.0.0.1:8080
149 148
     </pre>
150
-    
151
-    <p>Now save the torrc, shut down
152
-    your Tor, and then start it again.
153
-    </p>
154
-    
149
+
150
+    <p>Now save the torrc and restart your tor.</p>
151
+
155 152
     <p>If Tor starts up again, great. Otherwise, something is wrong. First look at
156 153
     your logfiles for hints. It will print some warnings or error messages. That
157 154
     should give you an idea what went wrong. Typically there are typos in the torrc
... ...
@@ -159,10 +156,10 @@
159 156
     logging FAQ entry</a> if you don't know how to enable or find your
160 157
     log file.)
161 158
     </p>
162
-    
159
+
163 160
     <p>When Tor starts, it will automatically create the <var>HiddenServiceDir</var>
164 161
     that you specified (if necessary), and it will create two files there.</p>
165
-    
162
+
166 163
     <dl>
167 164
     <dt><var>private_key</var></dt>
168 165
     <dd>First, Tor will generate a new public/private keypair for your hidden
... ...
@@ -176,11 +173,11 @@
176 173
     and you can tell it to people, publish it on websites, put it on business
177 174
     cards, etc.</dd>
178 175
     </dl>
179
-    
176
+
180 177
     <p>If Tor runs as a different user than you, for example on
181 178
     OS X, Debian, or Red Hat, then you may need to become root to be able
182 179
     to view these files.</p>
183
-    
180
+
184 181
     <p>Now that you've restarted Tor, it is busy picking introduction points
185 182
     in the Tor network, and generating a <em>hidden service
186 183
     descriptor</em>. This is a signed list of introduction points along with
... ...
@@ -188,22 +185,22 @@
188 185
     to the directory servers, and other people anonymously fetch it from the
189 186
     directory servers when they're trying to access your service.
190 187
     </p>
191
-    
188
+
192 189
     <p>Try it now: paste the contents of the hostname file into your web
193 190
     browser. If it works, you'll get the html page you set up in step one.
194 191
     If it doesn't work, look in your logs for some hints, and keep playing
195 192
     with it until it works.
196 193
     </p>
197
-    
194
+
198 195
     <hr>
199 196
     <a id="three"></a>
200 197
     <h2><a class="anchor" href="#three">Step Three: More advanced tips</a></h2>
201 198
     <br>
202
-    
199
+
203 200
     <p>If you plan to keep your service available for a long time, you might
204 201
     want to make a backup copy of the <var>private_key</var> file somewhere.
205 202
     </p>
206
-    
203
+
207 204
     <p>We avoided recommending Apache above, a) because many people might
208 205
     already be running it for a public web server on their computer, and b)
209 206
     because it's big
... ...
@@ -213,7 +210,7 @@
213 210
     somebody make us a checklist of ways to lock down your Apache when you're
214 211
     using it as a hidden service? Savant probably has these problems too.
215 212
     </p>
216
-    
213
+
217 214
     <p>If you want to forward multiple virtual ports for a single hidden
218 215
     service, just add more <var>HiddenServicePort</var> lines.
219 216
     If you want to run multiple hidden services from the same Tor
... ...
@@ -221,16 +218,16 @@
221 218
     <var>HiddenServicePort</var> lines refer to this <var>HiddenServiceDir</var> line, until
222 219
     you add another <var>HiddenServiceDir</var> line:
223 220
     </p>
224
-    
221
+
225 222
     <pre>
226 223
     HiddenServiceDir /usr/local/etc/tor/hidden_service/
227 224
     HiddenServicePort 80 127.0.0.1:8080
228
-    
225
+
229 226
     HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
230 227
     HiddenServicePort 6667 127.0.0.1:6667
231 228
     HiddenServicePort 22 127.0.0.1:22
232 229
     </pre>
233
-    
230
+
234 231
     <p>There are some anonymity issues you should keep in mind too:
235 232
     </p>
236 233
     <ul>
... ...
@@ -242,9 +239,9 @@
242 239
     won't be either. This leaks information to an observant adversary.</li>
243 240
     <!-- increased risks over time -->
244 241
     </ul>
245
-    
242
+
246 243
     <hr>
247
-    
244
+
248 245
     <p>If you have suggestions for improving this document, please <a
249 246
     href="<page about/contact>">send them to us</a>. Thanks!</p>
250 247
   </div>
Browse code

update hidden service examples.

Andrew Lewman authored on12/04/2012 14:34:34
Showing1 changed files
... ...
@@ -20,15 +20,34 @@
20 20
     </p>
21 21
     
22 22
     <p>If you have Tor installed, you can see hidden services
23
-    in action by visiting <a href="http://duskgytldkxiuqc6.onion/">our
24
-    example hidden service</a>.
23
+    in action by visiting one of our official hidden services:
24
+    <ul>
25
+    <li><a href="http://idnxcnkne4qt76tg.onion/">The Tor Project Website</a></li>
26
+    <li><a href="http://j6im4v42ur6dpic3.onion/">The Tor Package Archive</a></li>
27
+    <li><a href="http://p3igkncehackjtib.onion/">The Tor Media Archive</a></li>
28
+    </ul>
29
+
30
+    Others run reliable hidden services, such as <a
31
+    href="http://3g2upl4pq6kufc4m.onion/">The Duck Duck
32
+    Go</a> search engine and someone hosting a <a
33
+    href="http://duskgytldkxiuqc6.onion/">sample site</a>.
25 34
     </p>
26
-    
27
-    <p>This howto describes the steps for setting up your own hidden service
35
+    <p>
36
+    It will typically take 10-60 seconds to load (or to decide that the
37
+    service is currently unreachable). If it fails immediately and your
38
+    browser pops up an alert saying that "www.duskgytldkxiuqc6.onion could
39
+    not be found, please check the name and try again" then you haven't
40
+    configured Tor correctly; see <a href="<page docs/faq>#DoesntWork">the
41
+    it-doesn't-work FAQ entry</a> for some help.
42
+    </p>
43
+
44
+    <p>
45
+    This howto describes the steps for setting up your own hidden service
28 46
     website. For the technical details of how the hidden service protocol
29
-    works, see our <a href="<page docs/hidden-services>">hidden service protocol</a> page.
47
+    works, see our <a href="<page docs/hidden-services>">hidden service
48
+    protocol</a> page.
30 49
     </p>
31
-    
50
+
32 51
     <hr>
33 52
     <a id="zero"></a>
34 53
     <h2><a class="anchor" href="#zero">Step Zero: Get Tor working</a></h2>
... ...
@@ -48,66 +67,33 @@
48 67
     X howto</a>, and Linux/BSD/Unix users should follow the <a
49 68
     href="<page docs/tor-doc-unix>">Unix howto</a>.
50 69
     </p>
51
-    
52
-    <p>Once you've got Tor installed and configured,
53
-    you can see hidden services in action by following this link to <a
54
-    href="http://duskgytldkxiuqc6.onion/">our example hidden service</a>
55
-    or the <a
56
-    href="http://3g2upl4pq6kufc4m.onion/">DuckDuckGo search engine hidden service</a>.
57
-    It will typically take 10-60 seconds to load (or to decide that it
58
-    is currently unreachable). If it fails immediately and your browser
59
-    pops up an alert saying that "www.duskgytldkxiuqc6.onion could not
60
-    be found, please check the name and try again" then you haven't
61
-    configured Tor correctly; see <a
62
-    href="<page docs/faq>#DoesntWork">the
63
-    it-doesn't-work FAQ entry</a> for some help.
64
-    </p>
65
-    
70
+
66 71
     <hr>
67 72
     <a id="one"></a>
68 73
     <h2><a class="anchor" href="#one">Step One: Install a web server locally</a></h2>
69 74
     <br>
70 75
     
71
-    <p>First, you need to set up a web server locally. Setting up a web
72
-    server can be tricky,
73
-    so we're just going to go over a few basics here. If you get stuck
74
-    or want to do more, find a friend who can help you. We recommend you
75
-    install a new separate web server for your hidden service, since even
76
-    if you already have one installed, you may be using it (or want to use
77
-    it later) for an actual website.
78
-    </p>
79
-    
80
-    <p>If you're on Unix or OS X and you're comfortable with
81
-    the command-line, by far the best way to go is to install <a
82
-    href="http://www.acme.com/software/thttpd/">thttpd</a>. Just grab the
83
-    latest tarball, untar it (it will create its own directory), and run
84
-    <kbd>./configure &amp;&amp; make</kbd>. Then <kbd>mkdir hidserv; cd
85
-    hidserv</kbd>, and run
86
-    <kbd>../thttpd -p 5222 -h localhost</kbd>. It will give you back your prompt,
87
-    and now you're running a webserver on port 5222. You can put files to
88
-    serve in the hidserv directory.
89
-    </p>
90
-    
91
-    <p>If you're on Windows, you might pick <a
92
-    href="http://savant.sourceforge.net/">Savant</a> or <a
93
-    href="http://httpd.apache.org/">Apache</a>, and be sure to configure it
94
-    to bind only to localhost. You should also figure out what port you're
95
-    listening on, because you'll use it below.
96
-    </p>
97
-    
98
-    <p>(The reason we bind the web server only to localhost is to make
99
-    sure it isn't publically accessible. If people could get to it directly,
100
-    they could confirm that your computer is the one offering the hidden
101
-    service.)
76
+    <p>
77
+    First, you need to set up a web server locally. Setting up a web
78
+    server can be tricky, so we're just going to go over a few basics
79
+    here. If you get stuck or want to do more, find a friend who can
80
+    help you. We recommend you install a new separate web server for
81
+    your hidden service, since even if you already have one installed,
82
+    you may be using it (or want to use it later) for an actual website.
102 83
     </p>
103
-    
104
-    <p>Once you've got your web server set up, make sure it works: open your
105
-    browser and go to <a
106
-    href="http://localhost:5222/">http://localhost:5222/</a>, where 5222 is
107
-    the port that you picked above. Then try putting a file in the main html
108
-    directory, and make sure it shows up when you access the site.
84
+
85
+    <p>
86
+    Once you've got your web server set up, make
87
+    sure it works: open your browser and go to <a
88
+    href="http://localhost:5222/">http://localhost:5222/</a>, where
89
+    5222 is the port that you picked above. Then try putting a file in
90
+    the main html directory, and make sure it shows up when you access
91
+    the site.  The reason we bind the web server only to localhost is to
92
+    make sure it isn't publically accessible. If people could get to it
93
+    directly, they could confirm that your computer is the one offering
94
+    the hidden service.
109 95
     </p>
110
-    
96
+
111 97
     <hr>
112 98
     <a id="two"></a>
113 99
     <h2><a class="anchor" href="#two">Step Two: Configure your hidden service</a></h2>
Browse code

Remove backslash from Windows HiddenServiceDir example

Sebastian Hahn authored on17/03/2012 13:55:07
Showing1 changed files
... ...
@@ -158,7 +158,7 @@
158 158
     package. On Unix, try "/home/username/hidden_service/" and fill in your own
159 159
     username in place of "username". On Windows you might pick:</p>
160 160
     <pre>
161
-    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
161
+    HiddenServiceDir C:\Users\username\Documents\tor\hidden_service
162 162
     HiddenServicePort 80 127.0.0.1:5222
163 163
     </pre>
164 164
     
Browse code

fix the faq anchors that have been migrated already. leave ten or twenty broken anchors for the old faq.

Roger Dingledine authored on07/02/2011 10:40:23
Showing1 changed files
... ...
@@ -59,7 +59,7 @@
59 59
     pops up an alert saying that "www.duskgytldkxiuqc6.onion could not
60 60
     be found, please check the name and try again" then you haven't
61 61
     configured Tor correctly; see <a
62
-    href="<wikifaq>#ItDoesntWork">the
62
+    href="<page docs/faq>#DoesntWork">the
63 63
     it-doesn't-work FAQ entry</a> for some help.
64 64
     </p>
65 65
     
Browse code

revise #Logs entry. fix several broken anchors to this faq entry.

Roger Dingledine authored on07/02/2011 10:19:10
Showing1 changed files
... ...
@@ -169,8 +169,7 @@
169 169
     <p>If Tor starts up again, great. Otherwise, something is wrong. First look at
170 170
     your logfiles for hints. It will print some warnings or error messages. That
171 171
     should give you an idea what went wrong. Typically there are typos in the torrc
172
-    or wrong directory permissions (See <a
173
-    href="<wikifaq>#Logs">the
172
+    or wrong directory permissions (See <a href="<page docs/faq>#Logs">the
174 173
     logging FAQ entry</a> if you don't know how to enable or find your
175 174
     log file.)
176 175
     </p>
Browse code

change links to the #torrc faq entry, fixing two broken links in the process

Roger Dingledine authored on07/02/2011 09:06:17
Showing1 changed files
... ...
@@ -118,7 +118,7 @@
118 118
     </p>
119 119
     
120 120
     <p>First, open your torrc file in your favorite text editor. (See <a
121
-    href="<wikifaq>#torrc">the
121
+    href="<page docs/faq>#torrc">the
122 122
     torrc FAQ entry</a> to learn what this means.) Go to the middle section and
123 123
     look for the line</p>
124 124
     
Browse code

change the test hidserv link to DDG, since I've been told no less than 5 different wl hidservs, none of which work.

Andrew Lewman authored on08/12/2010 18:31:51
Showing1 changed files
... ...
@@ -53,12 +53,12 @@
53 53
     you can see hidden services in action by following this link to <a
54 54
     href="http://duskgytldkxiuqc6.onion/">our example hidden service</a>
55 55
     or the <a
56
-    href="http://gaddbiwdftapglkq.onion/">Wikileaks hidden service</a>.
57
-    It will typically take 10-60 seconds to load
58
-    (or to decide that it is currently unreachable). If it fails
59
-    immediately and your browser pops up an alert saying that
60
-    "www.duskgytldkxiuqc6.onion could not be found, please check the name and
61
-    try again" then you haven't configured Tor correctly; see <a
56
+    href="http://3g2upl4pq6kufc4m.onion/">DuckDuckGo search engine hidden service</a>.
57
+    It will typically take 10-60 seconds to load (or to decide that it
58
+    is currently unreachable). If it fails immediately and your browser
59
+    pops up an alert saying that "www.duskgytldkxiuqc6.onion could not
60
+    be found, please check the name and try again" then you haven't
61
+    configured Tor correctly; see <a
62 62
     href="<wikifaq>#ItDoesntWork">the
63 63
     it-doesn't-work FAQ entry</a> for some help.
64 64
     </p>
Browse code

looks like we never set the keywords either

Roger Dingledine authored on27/10/2010 12:31:57
Showing1 changed files
... ...
@@ -1,5 +1,5 @@
1 1
 ## translation metadata
2
-# Revision: $Revision: 22314 $
2
+# Revision: $Revision$
3 3
 # Translation-Priority: 3-low
4 4
 
5 5
 #include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
Browse code

We decided to go with HTML in favor of XHTML.

Sebastian Hahn authored on10/10/2010 03:34:47
Showing1 changed files
... ...
@@ -11,7 +11,7 @@
11 11
   </div>
12 12
   <div id="maincol">
13 13
     <h1>Configuring Hidden Services for <a href="<page index>">Tor</a></h1>
14
-    <hr />
14
+    <hr>
15 15
     
16 16
     <p>Tor allows clients and relays to offer hidden services. That is,
17 17
     you can offer a web server, SSH server, etc., without revealing your
... ...
@@ -29,10 +29,10 @@
29 29
     works, see our <a href="<page docs/hidden-services>">hidden service protocol</a> page.
30 30
     </p>
31 31
     
32
-    <hr />
32
+    <hr>
33 33
     <a id="zero"></a>
34 34
     <h2><a class="anchor" href="#zero">Step Zero: Get Tor working</a></h2>
35
-    <br />
35
+    <br>
36 36
     
37 37
     <p>Before you start, you need to make sure:</p>
38 38
     <ol>
... ...
@@ -63,10 +63,10 @@
63 63
     it-doesn't-work FAQ entry</a> for some help.
64 64
     </p>
65 65
     
66
-    <hr />
66
+    <hr>
67 67
     <a id="one"></a>
68 68
     <h2><a class="anchor" href="#one">Step One: Install a web server locally</a></h2>
69
-    <br />
69
+    <br>
70 70
     
71 71
     <p>First, you need to set up a web server locally. Setting up a web
72 72
     server can be tricky,
... ...
@@ -108,10 +108,10 @@
108 108
     directory, and make sure it shows up when you access the site.
109 109
     </p>
110 110
     
111
-    <hr />
111
+    <hr>
112 112
     <a id="two"></a>
113 113
     <h2><a class="anchor" href="#two">Step Two: Configure your hidden service</a></h2>
114
-    <br />
114
+    <br>
115 115
     
116 116
     <p>Next, you need to configure your hidden service to point to your
117 117
     local web server.
... ...
@@ -210,10 +210,10 @@
210 210
     with it until it works.
211 211
     </p>
212 212
     
213
-    <hr />
213
+    <hr>
214 214
     <a id="three"></a>
215 215
     <h2><a class="anchor" href="#three">Step Three: More advanced tips</a></h2>
216
-    <br />
216
+    <br>
217 217
     
218 218
     <p>If you plan to keep your service available for a long time, you might
219 219
     want to make a backup copy of the <var>private_key</var> file somewhere.
... ...
@@ -258,7 +258,7 @@
258 258
     <!-- increased risks over time -->
259 259
     </ul>
260 260
     
261
-    <hr />
261
+    <hr>
262 262
     
263 263
     <p>If you have suggestions for improving this document, please <a
264 264
     href="<page about/contact>">send them to us</a>. Thanks!</p>
Browse code

clean up wiki and faq references.

Andrew Lewman authored on08/10/2010 16:54:16
Showing1 changed files
... ...
@@ -59,7 +59,7 @@
59 59
     immediately and your browser pops up an alert saying that
60 60
     "www.duskgytldkxiuqc6.onion could not be found, please check the name and
61 61
     try again" then you haven't configured Tor correctly; see <a
62
-    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">the
62
+    href="<wikifaq>#ItDoesntWork">the
63 63
     it-doesn't-work FAQ entry</a> for some help.
64 64
     </p>
65 65
     
... ...
@@ -118,7 +118,7 @@
118 118
     </p>
119 119
     
120 120
     <p>First, open your torrc file in your favorite text editor. (See <a
121
-    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">the
121
+    href="<wikifaq>#torrc">the
122 122
     torrc FAQ entry</a> to learn what this means.) Go to the middle section and
123 123
     look for the line</p>
124 124
     
... ...
@@ -170,7 +170,7 @@
170 170
     your logfiles for hints. It will print some warnings or error messages. That
171 171
     should give you an idea what went wrong. Typically there are typos in the torrc
172 172
     or wrong directory permissions (See <a
173
-    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">the
173
+    href="<wikifaq>#Logs">the
174 174
     logging FAQ entry</a> if you don't know how to enable or find your
175 175
     log file.)
176 176
     </p>
Browse code

change all of the breadcrumbs from page home to page index.

Andrew Lewman authored on12/08/2010 17:17:47
Showing1 changed files
... ...
@@ -5,12 +5,12 @@
5 5
 #include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 6
 <div id="content" class="clearfix">
7 7
   <div id="breadcrumbs">
8
-    <a href="<page home>">Home &raquo; </a>
8
+    <a href="<page index>">Home &raquo; </a>
9 9
     <a href="<page docs/documentation>">Documentation &raquo; </a>
10 10
     <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 11
   </div>
12 12
   <div id="maincol">
13
-    <h1>Configuring Hidden Services for <a href="<page home>">Tor</a></h1>
13
+    <h1>Configuring Hidden Services for <a href="<page index>">Tor</a></h1>
14 14
     <hr />
15 15
     
16 16
     <p>Tor allows clients and relays to offer hidden services. That is,
Browse code

first cut of the new, shiny tor website as wml.

Andrew Lewman authored on09/07/2010 03:55:22
Showing1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,274 @@
1
+## translation metadata
2
+# Revision: $Revision: 22314 $
3
+# Translation-Priority: 3-low
4
+
5
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6
+<div id="content" class="clearfix">
7
+  <div id="breadcrumbs">
8
+    <a href="<page home>">Home &raquo; </a>
9
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11
+  </div>
12
+  <div id="maincol">
13
+    <h1>Configuring Hidden Services for <a href="<page home>">Tor</a></h1>
14
+    <hr />
15
+    
16
+    <p>Tor allows clients and relays to offer hidden services. That is,
17
+    you can offer a web server, SSH server, etc., without revealing your
18
+    IP address to its users. In fact, because you don't use any public address,
19
+    you can run a hidden service from behind your firewall.
20
+    </p>
21
+    
22
+    <p>If you have Tor installed, you can see hidden services
23
+    in action by visiting <a href="http://duskgytldkxiuqc6.onion/">our
24
+    example hidden service</a>.
25
+    </p>
26
+    
27
+    <p>This howto describes the steps for setting up your own hidden service
28
+    website. For the technical details of how the hidden service protocol
29
+    works, see our <a href="<page docs/hidden-services>">hidden service protocol</a> page.
30
+    </p>
31
+    
32
+    <hr />
33
+    <a id="zero"></a>
34
+    <h2><a class="anchor" href="#zero">Step Zero: Get Tor working</a></h2>
35
+    <br />
36
+    
37
+    <p>Before you start, you need to make sure:</p>
38
+    <ol>
39
+    <li>Tor is up and running,</li>
40
+    <li>You actually set it up correctly.</li>
41
+    </ol>
42
+    
43
+    
44
+    <p>Windows users should follow the <a
45
+    href="<page docs/tor-doc-windows>">Windows
46
+    howto</a>, OS X users should follow the <a
47
+    href="<page docs/tor-doc-osx>">OS
48
+    X howto</a>, and Linux/BSD/Unix users should follow the <a
49
+    href="<page docs/tor-doc-unix>">Unix howto</a>.
50
+    </p>
51
+    
52
+    <p>Once you've got Tor installed and configured,
53
+    you can see hidden services in action by following this link to <a
54
+    href="http://duskgytldkxiuqc6.onion/">our example hidden service</a>
55
+    or the <a
56
+    href="http://gaddbiwdftapglkq.onion/">Wikileaks hidden service</a>.
57
+    It will typically take 10-60 seconds to load
58
+    (or to decide that it is currently unreachable). If it fails
59
+    immediately and your browser pops up an alert saying that
60
+    "www.duskgytldkxiuqc6.onion could not be found, please check the name and
61
+    try again" then you haven't configured Tor correctly; see <a
62
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">the
63
+    it-doesn't-work FAQ entry</a> for some help.
64
+    </p>
65
+    
66
+    <hr />
67
+    <a id="one"></a>
68
+    <h2><a class="anchor" href="#one">Step One: Install a web server locally</a></h2>
69
+    <br />
70
+    
71
+    <p>First, you need to set up a web server locally. Setting up a web
72
+    server can be tricky,
73
+    so we're just going to go over a few basics here. If you get stuck
74
+    or want to do more, find a friend who can help you. We recommend you
75
+    install a new separate web server for your hidden service, since even
76
+    if you already have one installed, you may be using it (or want to use
77
+    it later) for an actual website.
78
+    </p>
79
+    
80
+    <p>If you're on Unix or OS X and you're comfortable with
81
+    the command-line, by far the best way to go is to install <a
82
+    href="http://www.acme.com/software/thttpd/">thttpd</a>. Just grab the
83
+    latest tarball, untar it (it will create its own directory), and run
84
+    <kbd>./configure &amp;&amp; make</kbd>. Then <kbd>mkdir hidserv; cd
85
+    hidserv</kbd>, and run
86
+    <kbd>../thttpd -p 5222 -h localhost</kbd>. It will give you back your prompt,
87
+    and now you're running a webserver on port 5222. You can put files to
88
+    serve in the hidserv directory.
89
+    </p>
90
+    
91
+    <p>If you're on Windows, you might pick <a
92
+    href="http://savant.sourceforge.net/">Savant</a> or <a
93
+    href="http://httpd.apache.org/">Apache</a>, and be sure to configure it
94
+    to bind only to localhost. You should also figure out what port you're
95
+    listening on, because you'll use it below.
96
+    </p>
97
+    
98
+    <p>(The reason we bind the web server only to localhost is to make
99
+    sure it isn't publically accessible. If people could get to it directly,
100
+    they could confirm that your computer is the one offering the hidden
101
+    service.)
102
+    </p>
103
+    
104
+    <p>Once you've got your web server set up, make sure it works: open your
105
+    browser and go to <a
106
+    href="http://localhost:5222/">http://localhost:5222/</a>, where 5222 is
107
+    the port that you picked above. Then try putting a file in the main html
108
+    directory, and make sure it shows up when you access the site.
109
+    </p>
110
+    
111
+    <hr />
112
+    <a id="two"></a>
113
+    <h2><a class="anchor" href="#two">Step Two: Configure your hidden service</a></h2>
114
+    <br />
115
+    
116
+    <p>Next, you need to configure your hidden service to point to your
117
+    local web server.
118
+    </p>
119
+    
120
+    <p>First, open your torrc file in your favorite text editor. (See <a
121
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">the
122
+    torrc FAQ entry</a> to learn what this means.) Go to the middle section and
123
+    look for the line</p>
124
+    
125
+    <pre>
126
+    \############### This section is just for location-hidden services ###
127
+    </pre>