free
/
freedombone
关注 1
点赞 0
派生 0
代码 工单 0 合并请求 0 版本发布 0 百科 动态
浏览代码

Note about https everywhere

Bob Mottram 9 年前
父节点
7bc0e8db17
当前提交
1f484f408c
共有 2 个文件被更改，包括 79 次插入 和 65 次删除
分列视图 显示文件统计
  1. 3
    0
      doc/EN/faq.org
  2. 76
    65
      website/EN/faq.html

+ 3
- 0
doc/EN/faq.org 查看文件 

@@ -19,6 +19,7 @@
19 19 
 #+BEGIN_CENTER
20 20 
 #+ATTR_HTML: :border -1
21 21 
 | [[I don't have a static IP address. Can I still install this system?]]            |
22 
+| [[Why can't I access my .onion site with a Tor browser?]]                         |
22 23 
 | [[What is the best hardware to run this system on?]]                              |
23 24 
 | [[Can I add more users to the system?]]                                           |
24 25 
 | [[How do I remove a user from the system?]]                                       |
 
@@ -40,6 +41,8 @@
40 41 
 Yes. The minimum requirements are to have some hardware that you can install Debian onto and also that you have administrator access to your internet router so that you can forward ports to the system which has Freedombone installed.
41 42
42 43 
 The lack of a static IP address can be worked around by using a dynamic DNS service. Freedombone uses [[http://troglobit.com/inadyn.html][inadyn]], which supports a variety of dynamic DNS providers.
44 
+* Why can't I access my .onion site with a Tor browser?
45 
+By default the Tor browser has [[https://www.eff.org/HTTPS-everywhere][https everywhere]] enabled and this can clash with onion addresses. Really this is a browser bug, which ought to be fixed. If you notice that "https" has been automatically prepended to your onion address then go to the https everywhere settings and disable it. https isn't needed for ontion sites since onion services already have their own public key encryption (the onion address is the public key).
43 46 
 * What is the best hardware to run this system on?
44 47 
 It was originally designed to run on the Beaglebone Black, but that should be regarded as the most minimal system, because it's single core and has by today's standards a small amount of memory. Obviously the more powerful the hardware is the faster things like web pages (blog, social networking, etc) will be served but the more electricity such a system will require if you're running it 24/7. A good compromise between performance and energy consumption is something like an old netbook. The battery of an old netbook or laptop even gives you [[https://en.wikipedia.org/wiki/Uninterruptible_power_supply][UPS capability]] to keep the system going during brief power outages or cable re-arrangements, and that means using full disk encryption on the server also becomes more practical.
45 48

+ 76
- 65
website/EN/faq.html 查看文件 

@@ -3,15 +3,15 @@
3 3 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5 
 <head>
6 
-<title></title>
7 
-<!-- 2016-01-07 Thu 19:23 -->
6 
+<!-- 2016-01-15 Fri 10:06 -->
8 7 
 <meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 
+<meta  name="viewport" content="width=device-width, initial-scale=1" />
9 
+<title></title>
9 10 
 <meta  name="generator" content="Org-mode" />
10 11 
 <meta  name="author" content="Bob Mottram" />
11 12 
 <meta  name="description" content="Turn the Beaglebone Black into a personal communications server"
12 13 
  />
13 14 
 <meta  name="keywords" content="freedombox, debian, beaglebone, hubzilla, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
14 
-<meta  name="viewport" content="width=device-width, initial-scale=1" />
15 15 
 <style type="text/css">
16 16 
  <!--/*--><![CDATA[/*><!--*/
17 17 
   .title  { text-align: center;
 
@@ -75,8 +75,7 @@
75 75 
   td.org-left   { text-align: left;   }
76 76 
   td.org-center { text-align: center; }
77 77 
   dt { font-weight: bold; }
78 
-  .footpara:nth-child(2) { display: inline; }
79 
-  .footpara { display: block; }
78 
+  .footpara { display: inline; }
80 79 
   .footdef  { margin-bottom: 1em; }
81 80 
   .figure { padding: 1em; }
82 81 
   .figure p { text-align: center; }
 
@@ -151,7 +150,7 @@ for the JavaScript code in this tag.
151 150 
 <a name="top" id="top"></a>
152 151 
 </div>
153 152 
 <div id="content">
154 
-<div class="center">
153 
+<div class="org-center">
155 154
156 155 
 <div class="figure">
157 156 
 <p><img src="images/logo.png" alt="logo.png" />
 
@@ -163,7 +162,7 @@ for the JavaScript code in this tag.
163 162 
 <h1>Frequently Asked Questions</h1>
164 163 
 </center>
165 164
166 
-<div class="center">
165 
+<div class="org-center">
167 166 
 <table border="-1" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
168 167
169 168 
 
@@ -176,63 +175,67 @@ for the JavaScript code in this tag.
176 175 
 </tr>
177 176
178 177 
 <tr>
179 
-<td class="org-left"><a href="#orgheadline2">What is the best hardware to run this system on?</a></td>
178 
+<td class="org-left"><a href="#orgheadline2">Why can't I access my .onion site with a Tor browser?</a></td>
180 179 
 </tr>
181 180
182 181 
 <tr>
183 
-<td class="org-left"><a href="#orgheadline3">Can I add more users to the system?</a></td>
182 
+<td class="org-left"><a href="#orgheadline3">What is the best hardware to run this system on?</a></td>
184 183 
 </tr>
185 184
186 185 
 <tr>
187 
-<td class="org-left"><a href="#orgheadline4">How do I remove a user from the system?</a></td>
186 
+<td class="org-left"><a href="#orgheadline4">Can I add more users to the system?</a></td>
188 187 
 </tr>
189 188
190 189 
 <tr>
191 
-<td class="org-left"><a href="#orgheadline5">How do I reset the tripwire?</a></td>
190 
+<td class="org-left"><a href="#orgheadline5">How do I remove a user from the system?</a></td>
192 191 
 </tr>
193 192
194 193 
 <tr>
195 
-<td class="org-left"><a href="#orgheadline6">Is metadata protected?</a></td>
194 
+<td class="org-left"><a href="#orgheadline6">How do I reset the tripwire?</a></td>
196 195 
 </tr>
197 196
198 197 
 <tr>
199 
-<td class="org-left"><a href="#orgheadline7">How do I create email processing rules?</a></td>
198 
+<td class="org-left"><a href="#orgheadline7">Is metadata protected?</a></td>
200 199 
 </tr>
201 200
202 201 
 <tr>
203 
-<td class="org-left"><a href="#orgheadline8">Why isn't dynamic DNS working?</a></td>
202 
+<td class="org-left"><a href="#orgheadline8">How do I create email processing rules?</a></td>
204 203 
 </tr>
205 204
206 205 
 <tr>
207 
-<td class="org-left"><a href="#orgheadline9">How do I change my encryption settings?</a></td>
206 
+<td class="org-left"><a href="#orgheadline9">Why isn't dynamic DNS working?</a></td>
208 207 
 </tr>
209 208
210 209 
 <tr>
211 
-<td class="org-left"><a href="#orgheadline10">How do I get a domain name?</a></td>
210 
+<td class="org-left"><a href="#orgheadline10">How do I change my encryption settings?</a></td>
212 211 
 </tr>
213 212
214 213 
 <tr>
215 
-<td class="org-left"><a href="#orgheadline11">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
214 
+<td class="org-left"><a href="#orgheadline11">How do I get a domain name?</a></td>
216 215 
 </tr>
217 216
218 217 
 <tr>
219 
-<td class="org-left"><a href="#orgheadline12">How do I renew a Let's Encrypt certificate?</a></td>
218 
+<td class="org-left"><a href="#orgheadline12">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
220 219 
 </tr>
221 220
222 221 
 <tr>
223 
-<td class="org-left"><a href="#orgheadline13">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
222 
+<td class="org-left"><a href="#orgheadline13">How do I renew a Let's Encrypt certificate?</a></td>
224 223 
 </tr>
225 224
226 225 
 <tr>
227 
-<td class="org-left"><a href="#orgheadline14">Why use self-signed certificates?</a></td>
226 
+<td class="org-left"><a href="#orgheadline14">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
228 227 
 </tr>
229 228
230 229 
 <tr>
231 
-<td class="org-left"><a href="#orgheadline15">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
230 
+<td class="org-left"><a href="#orgheadline15">Why use self-signed certificates?</a></td>
232 231 
 </tr>
233 232
234 233 
 <tr>
235 
-<td class="org-left"><a href="#orgheadline16">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
234 
+<td class="org-left"><a href="#orgheadline16">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
235 
+</tr>
236 
+
237 
+<tr>
238 
+<td class="org-left"><a href="#orgheadline17">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
236 239 
 </tr>
237 240 
 </tbody>
238 241 
 </table>
 
@@ -251,9 +254,17 @@ The lack of a static IP address can be worked around by using a dynamic DNS serv
251 254 
 </div>
252 255 
 </div>
253 256 
 <div id="outline-container-orgheadline2" class="outline-2">
254 
-<h2 id="orgheadline2">What is the best hardware to run this system on?</h2>
257 
+<h2 id="orgheadline2">Why can't I access my .onion site with a Tor browser?</h2>
255 258 
 <div class="outline-text-2" id="text-orgheadline2">
256 259 
 <p>
260 
+By default the Tor browser has <a href="https://www.eff.org/HTTPS-everywhere">https everywhere</a> enabled and this can clash with onion addresses. Really this is a browser bug, which ought to be fixed. If you notice that "https" has been automatically prepended to your onion address then go to the https everywhere settings and disable it. https isn't needed for ontion sites since onion services already have their own public key encryption (the onion address is the public key).
261 
+</p>
262 
+</div>
263 
+</div>
264 
+<div id="outline-container-orgheadline3" class="outline-2">
265 
+<h2 id="orgheadline3">What is the best hardware to run this system on?</h2>
266 
+<div class="outline-text-2" id="text-orgheadline3">
267 
+<p>
257 268 
 It was originally designed to run on the Beaglebone Black, but that should be regarded as the most minimal system, because it's single core and has by today's standards a small amount of memory. Obviously the more powerful the hardware is the faster things like web pages (blog, social networking, etc) will be served but the more electricity such a system will require if you're running it 24/7. A good compromise between performance and energy consumption is something like an old netbook. The battery of an old netbook or laptop even gives you <a href="https://en.wikipedia.org/wiki/Uninterruptible_power_supply">UPS capability</a> to keep the system going during brief power outages or cable re-arrangements, and that means using full disk encryption on the server also becomes more practical.
258 269 
 </p>
259 270 
 
@@ -262,9 +273,9 @@ It was originally designed to run on the Beaglebone Black, but that should be re
262 273 
 </p>
263 274 
 </div>
264 275 
 </div>
265 
-<div id="outline-container-orgheadline3" class="outline-2">
266 
-<h2 id="orgheadline3">Can I add more users to the system?</h2>
267 
-<div class="outline-text-2" id="text-orgheadline3">
276 
+<div id="outline-container-orgheadline4" class="outline-2">
277 
+<h2 id="orgheadline4">Can I add more users to the system?</h2>
278 
+<div class="outline-text-2" id="text-orgheadline4">
268 279 
 <p>
269 280 
 Yes. Freedombone can support a small number of users, for a "<i>friends and family</i>" type of home installation. This gives them access to an email account, XMPP, SIP phone and the blog (depending on whether the variant which you installed includes those).
270 281 
 </p>
 
@@ -289,9 +300,9 @@ Another point is that Freedombone installations are not intended to support many
289 300 
 </p>
290 301 
 </div>
291 302 
 </div>
292 
-<div id="outline-container-orgheadline4" class="outline-2">
293 
-<h2 id="orgheadline4">How do I remove a user from the system?</h2>
294 
-<div class="outline-text-2" id="text-orgheadline4">
303 
+<div id="outline-container-orgheadline5" class="outline-2">
304 
+<h2 id="orgheadline5">How do I remove a user from the system?</h2>
305 
+<div class="outline-text-2" id="text-orgheadline5">
295 306 
 <p>
296 307 
 To remove a user:
297 308 
 </p>
 
@@ -308,9 +319,9 @@ Select <i>Manage Users</i> and then <i>Delete a user</i>. Note that this will de
308 319 
 </p>
309 320 
 </div>
310 321 
 </div>
311 
-<div id="outline-container-orgheadline5" class="outline-2">
312 
-<h2 id="orgheadline5">How do I reset the tripwire?</h2>
313 
-<div class="outline-text-2" id="text-orgheadline5">
322 
+<div id="outline-container-orgheadline6" class="outline-2">
323 
+<h2 id="orgheadline6">How do I reset the tripwire?</h2>
324 
+<div class="outline-text-2" id="text-orgheadline6">
314 325 
 <p>
315 326 
 The tripwire will be automatically reset once per week. If you want to reset it earlier then do the following:
316 327 
 </p>
 
@@ -327,17 +338,17 @@ Select "reset tripwire" using cursors and space bar then enter.
327 338 
 </p>
328 339 
 </div>
329 340 
 </div>
330 
-<div id="outline-container-orgheadline6" class="outline-2">
331 
-<h2 id="orgheadline6">Is metadata protected?</h2>
332 
-<div class="outline-text-2" id="text-orgheadline6">
341 
+<div id="outline-container-orgheadline7" class="outline-2">
342 
+<h2 id="orgheadline7">Is metadata protected?</h2>
343 
+<div class="outline-text-2" id="text-orgheadline7">
333 344 
 <p>
334 345 
 Even when using Freedombone metadata analysis by third parties is still possible. This can be mitigated by accessing your blog, or other web services, via their <i>onion addresses</i>, rather than via more conventional domain names. In that case your ISP and any government which they might be compelled to report back to will know when your system is being accessed, but not necessarily <i>which</i> services are being accessed <i>or by whom</i>. So for instance using a Tor browser and the onion address people may be able to safely read your blog or wiki and be reasonably confident that metadata isn't being gathered about what they read (or more concisely the metadata which can be gathered by a third party may just not be very useful or personally identifiable). On the other hand if you access the system via conventional domain names and dynamic DNS then it's safe to assume that metadata can and will be collected by third parties.
335 346 
 </p>
336 347 
 </div>
337 348 
 </div>
338 
-<div id="outline-container-orgheadline7" class="outline-2">
339 
-<h2 id="orgheadline7">How do I create email processing rules?</h2>
340 
-<div class="outline-text-2" id="text-orgheadline7">
349 
+<div id="outline-container-orgheadline8" class="outline-2">
350 
+<h2 id="orgheadline8">How do I create email processing rules?</h2>
351 
+<div class="outline-text-2" id="text-orgheadline8">
341 352 
 <div class="org-src-container">
342 353
343 354 
 <pre class="src src-bash">ssh username@domainname -p 2222
 
@@ -395,9 +406,9 @@ Spamassassin is also available and within Mutt you can use the S (shift+s) key t
395 406 
 </p>
396 407 
 </div>
397 408 
 </div>
398 
-<div id="outline-container-orgheadline8" class="outline-2">
399 
-<h2 id="orgheadline8">Why isn't dynamic DNS working?</h2>
400 
-<div class="outline-text-2" id="text-orgheadline8">
409 
+<div id="outline-container-orgheadline9" class="outline-2">
410 
+<h2 id="orgheadline9">Why isn't dynamic DNS working?</h2>
411 
+<div class="outline-text-2" id="text-orgheadline9">
401 412 
 <p>
402 413 
 If you run the command:
403 414 
 </p>
 
@@ -465,9 +476,9 @@ http://httpbin.org/ip
465 476 
 </div>
466 477 
 </div>
467 478
468 
-<div id="outline-container-orgheadline9" class="outline-2">
469 
-<h2 id="orgheadline9">How do I change my encryption settings?</h2>
470 
-<div class="outline-text-2" id="text-orgheadline9">
479 
+<div id="outline-container-orgheadline10" class="outline-2">
480 
+<h2 id="orgheadline10">How do I change my encryption settings?</h2>
481 
+<div class="outline-text-2" id="text-orgheadline10">
471 482 
 <p>
472 483 
 Suppose that some new encryption vulnerability has been announced and that you need to change your encryption settings. Maybe an algorithm thought to be secure is now no longer so and you need to remove it. You can change your settings by doing the following:
473 484 
 </p>
 
@@ -484,9 +495,9 @@ Then select <i>Security Settings</i>. You will then be able to edit the crypto s
484 495 
 </p>
485 496 
 </div>
486 497 
 </div>
487 
-<div id="outline-container-orgheadline10" class="outline-2">
488 
-<h2 id="orgheadline10">How do I get a domain name?</h2>
489 
-<div class="outline-text-2" id="text-orgheadline10">
498 
+<div id="outline-container-orgheadline11" class="outline-2">
499 
+<h2 id="orgheadline11">How do I get a domain name?</h2>
500 
+<div class="outline-text-2" id="text-orgheadline11">
490 501 
 <p>
491 502 
 Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
492 503 
 </p>
 
@@ -554,9 +565,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
554 565 
 </div>
555 566 
 </div>
556 567
557 
-<div id="outline-container-orgheadline11" class="outline-2">
558 
-<h2 id="orgheadline11">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
559 
-<div class="outline-text-2" id="text-orgheadline11">
568 
+<div id="outline-container-orgheadline12" class="outline-2">
569 
+<h2 id="orgheadline12">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
570 
+<div class="outline-text-2" id="text-orgheadline12">
560 571 
 <p>
561 572 
 If you did the full install or selected the social variant then the system will have tried to obtain a Let's Encrypt certificate automatically during the install process. If this failed for any reason, or if you have created a new site which you need a certificate for then do the following:
562 573 
 </p>
 
@@ -577,9 +588,9 @@ One thing to be aware of is that Let's Encrypt doesn't support many dynamic DNS
577 588 
 </p>
578 589 
 </div>
579 590 
 </div>
580 
-<div id="outline-container-orgheadline12" class="outline-2">
581 
-<h2 id="orgheadline12">How do I renew a Let's Encrypt certificate?</h2>
582 
-<div class="outline-text-2" id="text-orgheadline12">
591 
+<div id="outline-container-orgheadline13" class="outline-2">
592 
+<h2 id="orgheadline13">How do I renew a Let's Encrypt certificate?</h2>
593 
+<div class="outline-text-2" id="text-orgheadline13">
583 594 
 <p>
584 595 
 Normally certificates will be automatically renewed once per month, so you don't need to be concerned about it. If anything goes wrong with the automatic renewal then you should receive a warning email.
585 596 
 </p>
 
@@ -600,9 +611,9 @@ Select <b>Security settings</b> then <b>Renew Let's Encrypt certificate</b>.
600 611 
 </p>
601 612 
 </div>
602 613 
 </div>
603 
-<div id="outline-container-orgheadline13" class="outline-2">
604 
-<h2 id="orgheadline13">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
605 
-<div class="outline-text-2" id="text-orgheadline13">
614 
+<div id="outline-container-orgheadline14" class="outline-2">
615 
+<h2 id="orgheadline14">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
616 
+<div class="outline-text-2" id="text-orgheadline14">
606 617 
 <p>
607 618 
 Most likely it's because Let's Encrypt doesn't support your particular domain or subdomain. Currently free subdomains tend not to work. You'll need to buy a domain name, link it to your dynamic DNS account and then do:
608 619 
 </p>
 
@@ -619,9 +630,9 @@ Select <b>Security settings</b> then <b>Create a new Let's Encrypt certificate</
619 630 
 </p>
620 631 
 </div>
621 632 
 </div>
622 
-<div id="outline-container-orgheadline14" class="outline-2">
623 
-<h2 id="orgheadline14">Why use self-signed certificates?</h2>
624 
-<div class="outline-text-2" id="text-orgheadline14">
633 
+<div id="outline-container-orgheadline15" class="outline-2">
634 
+<h2 id="orgheadline15">Why use self-signed certificates?</h2>
635 
+<div class="outline-text-2" id="text-orgheadline15">
625 636 
 <p>
626 637 
 Almost everywhere on the web you will read that self-signed certificates are worthless. They bring up <i>scary-scary looking</i> browser warnings and gurus will advise you not to use them. Self-signed certificates are quite useful though. What the scary warnings mean - and it would be good if they explained this more clearly - is that you have an encrypted connection established but there is <i>no certainty about who that connection is with</i>.
627 638 
 </p>
 
@@ -643,17 +654,17 @@ For now a self-signed certificate will probably in most cases protect your commu
643 654 
 </p>
644 655 
 </div>
645 656 
 </div>
646 
-<div id="outline-container-orgheadline15" class="outline-2">
647 
-<h2 id="orgheadline15">Why not use the services of $company instead? They took the Seppuku pledge</h2>
648 
-<div class="outline-text-2" id="text-orgheadline15">
657 
+<div id="outline-container-orgheadline16" class="outline-2">
658 
+<h2 id="orgheadline16">Why not use the services of $company instead? They took the Seppuku pledge</h2>
659 
+<div class="outline-text-2" id="text-orgheadline16">
649 660 
 <p>
650 661 
 <a href="http://seppuku.cryptostorm.org/">That pledge</a> is utterly worthless. Years ago people trusted Google in the same sort of way, because they promised not be be evil and because a lot of the engineers working for them seemed like honest types who were "<i>on our side</i>". Post-<a href="https://en.wikipedia.org/wiki/Nymwars">nymwars</a> and post-<a href="https://en.wikipedia.org/wiki/PRISM_(surveillance_program)">PRISM</a> we know exactly how much Google cared about the privacy and security of its users. But Google is only one particular example. In general don't trust pledges made by companies, even if the people running them seem really sincere.
651 662 
 </p>
652 663 
 </div>
653 664 
 </div>
654 
-<div id="outline-container-orgheadline16" class="outline-2">
655 
-<h2 id="orgheadline16">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
656 
-<div class="outline-text-2" id="text-orgheadline16">
665 
+<div id="outline-container-orgheadline17" class="outline-2">
666 
+<h2 id="orgheadline17">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
667 
+<div class="outline-text-2" id="text-orgheadline17">
657 668 
 <p>
658 669 
 Welcome to the world of email. Email is really the archetypal decentralized service, developed during the early days of the internet. In principle anyone can run an email server, and that's exactly what you're doing with Freedombone. Email is very useful, but it has a big problem, and that's that the protocols are totally insecure. That made it easy for spammers to do their thing, and in response highly elaborate spam filtering and blocking systems were developed. Chances are that your emails are being blocked in this way. Sometimes the blocking is so indisciminate that entire countries are excluded. What can you do about it? Unless you control the block list at the receiving end probably you can't do anything. There is zero accountability for such blocking, and you can't just contact someone and say "hey, I'm not a spammer". This system works well for the big internet companies because it effectively centralises email to a few well-known brand names and keeps any independent servers out.
659 670 
 </p>