|
|
@@ -3,7 +3,7 @@
|
|
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
|
|
-<!-- 2016-06-23 Thu 17:25 -->
|
|
|
6
|
+<!-- 2016-06-23 Thu 17:28 -->
|
|
7
|
7
|
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
|
8
|
8
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
9
|
9
|
<title></title>
|
|
|
@@ -171,19 +171,19 @@ for the JavaScript code in this tag.
|
|
171
|
171
|
</colgroup>
|
|
172
|
172
|
<tbody>
|
|
173
|
173
|
<tr>
|
|
174
|
|
-<td class="org-left"><a href="#org5d53bd6">I don't have a static IP address. Can I still install this system?</a></td>
|
|
|
174
|
+<td class="org-left"><a href="#org1d3ab7c">I don't have a static IP address. Can I still install this system?</a></td>
|
|
175
|
175
|
</tr>
|
|
176
|
176
|
|
|
177
|
177
|
<tr>
|
|
178
|
|
-<td class="org-left"><a href="#orgeed951f">Why not support building images for Raspberry Pi?</a></td>
|
|
|
178
|
+<td class="org-left"><a href="#org192c9fa">Why not support building images for Raspberry Pi?</a></td>
|
|
179
|
179
|
</tr>
|
|
180
|
180
|
|
|
181
|
181
|
<tr>
|
|
182
|
|
-<td class="org-left"><a href="#org518d664">Why use Github?</a></td>
|
|
|
182
|
+<td class="org-left"><a href="#orga0d2da2">Why use Github?</a></td>
|
|
183
|
183
|
</tr>
|
|
184
|
184
|
|
|
185
|
185
|
<tr>
|
|
186
|
|
-<td class="org-left"><a href="#org6f9d9e9">Keys and emails should not be stored on servers. Why do you do that?</a></td>
|
|
|
186
|
+<td class="org-left"><a href="#org53c166e">Keys and emails should not be stored on servers. Why do you do that?</a></td>
|
|
187
|
187
|
</tr>
|
|
188
|
188
|
|
|
189
|
189
|
<tr>
|
|
|
@@ -191,83 +191,83 @@ for the JavaScript code in this tag.
|
|
191
|
191
|
</tr>
|
|
192
|
192
|
|
|
193
|
193
|
<tr>
|
|
194
|
|
-<td class="org-left"><a href="#org6276ec1">Why can't I access my .onion site with a Tor browser?</a></td>
|
|
|
194
|
+<td class="org-left"><a href="#org87ed884">Why can't I access my .onion site with a Tor browser?</a></td>
|
|
195
|
195
|
</tr>
|
|
196
|
196
|
|
|
197
|
197
|
<tr>
|
|
198
|
|
-<td class="org-left"><a href="#org5cde815">What is the best hardware to run this system on?</a></td>
|
|
|
198
|
+<td class="org-left"><a href="#org621113c">What is the best hardware to run this system on?</a></td>
|
|
199
|
199
|
</tr>
|
|
200
|
200
|
|
|
201
|
201
|
<tr>
|
|
202
|
|
-<td class="org-left"><a href="#org8a55c6f">Can I add more users to the system?</a></td>
|
|
|
202
|
+<td class="org-left"><a href="#org36b6c2a">Can I add more users to the system?</a></td>
|
|
203
|
203
|
</tr>
|
|
204
|
204
|
|
|
205
|
205
|
<tr>
|
|
206
|
|
-<td class="org-left"><a href="#orgdc06783">Why not use Signal for mobile chat?</a></td>
|
|
|
206
|
+<td class="org-left"><a href="#orgd747625">Why not use Signal for mobile chat?</a></td>
|
|
207
|
207
|
</tr>
|
|
208
|
208
|
|
|
209
|
209
|
<tr>
|
|
210
|
|
-<td class="org-left"><a href="#org61fd356">What is the most secure chat app to use on mobile?</a></td>
|
|
|
210
|
+<td class="org-left"><a href="#orgca1e6b9">What is the most secure chat app to use on mobile?</a></td>
|
|
211
|
211
|
</tr>
|
|
212
|
212
|
|
|
213
|
213
|
<tr>
|
|
214
|
|
-<td class="org-left"><a href="#orgb130d15">How do I remove a user from the system?</a></td>
|
|
|
214
|
+<td class="org-left"><a href="#org2ec102d">How do I remove a user from the system?</a></td>
|
|
215
|
215
|
</tr>
|
|
216
|
216
|
|
|
217
|
217
|
<tr>
|
|
218
|
|
-<td class="org-left"><a href="#orgf592313">How do I reset the tripwire?</a></td>
|
|
|
218
|
+<td class="org-left"><a href="#org342cf1c">How do I reset the tripwire?</a></td>
|
|
219
|
219
|
</tr>
|
|
220
|
220
|
|
|
221
|
221
|
<tr>
|
|
222
|
|
-<td class="org-left"><a href="#org3372f2a">Is metadata protected?</a></td>
|
|
|
222
|
+<td class="org-left"><a href="#org59a89db">Is metadata protected?</a></td>
|
|
223
|
223
|
</tr>
|
|
224
|
224
|
|
|
225
|
225
|
<tr>
|
|
226
|
|
-<td class="org-left"><a href="#org3c8f887">How do I create email processing rules?</a></td>
|
|
|
226
|
+<td class="org-left"><a href="#org15832a">How do I create email processing rules?</a></td>
|
|
227
|
227
|
</tr>
|
|
228
|
228
|
|
|
229
|
229
|
<tr>
|
|
230
|
|
-<td class="org-left"><a href="#orgf4dca3f">Why isn't dynamic DNS working?</a></td>
|
|
|
230
|
+<td class="org-left"><a href="#org4b5ee4">Why isn't dynamic DNS working?</a></td>
|
|
231
|
231
|
</tr>
|
|
232
|
232
|
|
|
233
|
233
|
<tr>
|
|
234
|
|
-<td class="org-left"><a href="#orga5c8552">How do I change my encryption settings?</a></td>
|
|
|
234
|
+<td class="org-left"><a href="#org9794585">How do I change my encryption settings?</a></td>
|
|
235
|
235
|
</tr>
|
|
236
|
236
|
|
|
237
|
237
|
<tr>
|
|
238
|
|
-<td class="org-left"><a href="#org63db5c8">How do I get a domain name?</a></td>
|
|
|
238
|
+<td class="org-left"><a href="#orga064d94">How do I get a domain name?</a></td>
|
|
239
|
239
|
</tr>
|
|
240
|
240
|
|
|
241
|
241
|
<tr>
|
|
242
|
|
-<td class="org-left"><a href="#orgdfe03d7">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
|
|
|
242
|
+<td class="org-left"><a href="#orgdfc40b">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
|
|
243
|
243
|
</tr>
|
|
244
|
244
|
|
|
245
|
245
|
<tr>
|
|
246
|
|
-<td class="org-left"><a href="#org1836ba3">How do I renew a Let's Encrypt certificate?</a></td>
|
|
|
246
|
+<td class="org-left"><a href="#org7f7ddb7">How do I renew a Let's Encrypt certificate?</a></td>
|
|
247
|
247
|
</tr>
|
|
248
|
248
|
|
|
249
|
249
|
<tr>
|
|
250
|
|
-<td class="org-left"><a href="#org7fcac9e">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
|
|
|
250
|
+<td class="org-left"><a href="#orgdfe7bea">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
|
|
251
|
251
|
</tr>
|
|
252
|
252
|
|
|
253
|
253
|
<tr>
|
|
254
|
|
-<td class="org-left"><a href="#org4092726">Why use self-signed certificates?</a></td>
|
|
|
254
|
+<td class="org-left"><a href="#org6b4c194">Why use self-signed certificates?</a></td>
|
|
255
|
255
|
</tr>
|
|
256
|
256
|
|
|
257
|
257
|
<tr>
|
|
258
|
|
-<td class="org-left"><a href="#org1eadbae">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
|
|
258
|
+<td class="org-left"><a href="#orga3f84a2">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
|
259
|
259
|
</tr>
|
|
260
|
260
|
|
|
261
|
261
|
<tr>
|
|
262
|
|
-<td class="org-left"><a href="#orge2c17a0">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
|
|
262
|
+<td class="org-left"><a href="#org997489b">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
|
263
|
263
|
</tr>
|
|
264
|
264
|
</tbody>
|
|
265
|
265
|
</table>
|
|
266
|
266
|
</div>
|
|
267
|
267
|
|
|
268
|
|
-<div id="outline-container-org5d53bd6" class="outline-2">
|
|
269
|
|
-<h2 id="org5d53bd6">I don't have a static IP address. Can I still install this system?</h2>
|
|
270
|
|
-<div class="outline-text-2" id="text-org5d53bd6">
|
|
|
268
|
+<div id="outline-container-org1d3ab7c" class="outline-2">
|
|
|
269
|
+<h2 id="org1d3ab7c">I don't have a static IP address. Can I still install this system?</h2>
|
|
|
270
|
+<div class="outline-text-2" id="text-org1d3ab7c">
|
|
271
|
271
|
<p>
|
|
272
|
272
|
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.
|
|
273
|
273
|
</p>
|
|
|
@@ -277,9 +277,9 @@ The lack of a static IP address can be worked around by using a dynamic DNS serv
|
|
277
|
277
|
</p>
|
|
278
|
278
|
</div>
|
|
279
|
279
|
</div>
|
|
280
|
|
-<div id="outline-container-orgeed951f" class="outline-2">
|
|
281
|
|
-<h2 id="orgeed951f">Why not support building images for Raspberry Pi?</h2>
|
|
282
|
|
-<div class="outline-text-2" id="text-orgeed951f">
|
|
|
280
|
+<div id="outline-container-org192c9fa" class="outline-2">
|
|
|
281
|
+<h2 id="org192c9fa">Why not support building images for Raspberry Pi?</h2>
|
|
|
282
|
+<div class="outline-text-2" id="text-org192c9fa">
|
|
283
|
283
|
<p>
|
|
284
|
284
|
The FreedomBox project supports Raspberry Pi builds, and the image build system for Freedombone is based on the same system. However, although the Raspberry Pi can run a version of Debian it requires a closed proprietary blob in order to boot the hardware. Who knows what that blob might contain or what exploits it could facilitate. From an adversarial point of view if you were trying to deliver "bulk equipment interference" then it doesn't get any better than piggybacking on something which has control of the boot process, and hence all subsequently run processes.
|
|
285
|
285
|
</p>
|
|
|
@@ -289,9 +289,9 @@ So although the Raspberry Pi is cheap and hugely popular it's not supported by t
|
|
289
|
289
|
</p>
|
|
290
|
290
|
</div>
|
|
291
|
291
|
</div>
|
|
292
|
|
-<div id="outline-container-org518d664" class="outline-2">
|
|
293
|
|
-<h2 id="org518d664">Why use Github?</h2>
|
|
294
|
|
-<div class="outline-text-2" id="text-org518d664">
|
|
|
292
|
+<div id="outline-container-orga0d2da2" class="outline-2">
|
|
|
293
|
+<h2 id="orga0d2da2">Why use Github?</h2>
|
|
|
294
|
+<div class="outline-text-2" id="text-orga0d2da2">
|
|
295
|
295
|
<p>
|
|
296
|
296
|
Github is paradoxically a centralized, closed and proprietary system which happens to mostly host free and open source projects. Up until now it has been relatively benign, but at some point in the name of "growth" it will likely start becoming more evil, or just become like SourceForge - which was also once much loved by FOSS developers, but turned into a den of malvertizing.
|
|
297
|
297
|
</p>
|
|
|
@@ -309,9 +309,9 @@ Currently many of the repositories used for applications which are not yet packa
|
|
309
|
309
|
</p>
|
|
310
|
310
|
</div>
|
|
311
|
311
|
</div>
|
|
312
|
|
-<div id="outline-container-org6f9d9e9" class="outline-2">
|
|
313
|
|
-<h2 id="org6f9d9e9">Keys and emails should not be stored on servers. Why do you do that?</h2>
|
|
314
|
|
-<div class="outline-text-2" id="text-org6f9d9e9">
|
|
|
312
|
+<div id="outline-container-org53c166e" class="outline-2">
|
|
|
313
|
+<h2 id="org53c166e">Keys and emails should not be stored on servers. Why do you do that?</h2>
|
|
|
314
|
+<div class="outline-text-2" id="text-org53c166e">
|
|
315
|
315
|
<p>
|
|
316
|
316
|
Ordinarily this is good advice. However, the threat model for a device in your home is different from the one for a generic server in a massive warehouse. Compare and contrast:
|
|
317
|
317
|
</p>
|
|
|
@@ -369,17 +369,17 @@ In the home environment a box with a good firewall and no GUI components install
|
|
369
|
369
|
</div>
|
|
370
|
370
|
</div>
|
|
371
|
371
|
|
|
372
|
|
-<div id="outline-container-org6276ec1" class="outline-2">
|
|
373
|
|
-<h2 id="org6276ec1">Why can't I access my .onion site with a Tor browser?</h2>
|
|
374
|
|
-<div class="outline-text-2" id="text-org6276ec1">
|
|
|
372
|
+<div id="outline-container-org87ed884" class="outline-2">
|
|
|
373
|
+<h2 id="org87ed884">Why can't I access my .onion site with a Tor browser?</h2>
|
|
|
374
|
+<div class="outline-text-2" id="text-org87ed884">
|
|
375
|
375
|
<p>
|
|
376
|
376
|
Probably you need to add the site to the NoScript whitelist. Typically click/press on the noscript icon (or select from the menu on mobile) then select <i>whitelist</i> and add the site URL. You may also need to disable HTTPS Everywhere when using onion addresses, which don't use https.
|
|
377
|
377
|
</p>
|
|
378
|
378
|
</div>
|
|
379
|
379
|
</div>
|
|
380
|
|
-<div id="outline-container-org5cde815" class="outline-2">
|
|
381
|
|
-<h2 id="org5cde815">What is the best hardware to run this system on?</h2>
|
|
382
|
|
-<div class="outline-text-2" id="text-org5cde815">
|
|
|
380
|
+<div id="outline-container-org621113c" class="outline-2">
|
|
|
381
|
+<h2 id="org621113c">What is the best hardware to run this system on?</h2>
|
|
|
382
|
+<div class="outline-text-2" id="text-org621113c">
|
|
383
|
383
|
<p>
|
|
384
|
384
|
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.
|
|
385
|
385
|
</p>
|
|
|
@@ -389,9 +389,9 @@ It was originally designed to run on the Beaglebone Black, but that should be re
|
|
389
|
389
|
</p>
|
|
390
|
390
|
</div>
|
|
391
|
391
|
</div>
|
|
392
|
|
-<div id="outline-container-org8a55c6f" class="outline-2">
|
|
393
|
|
-<h2 id="org8a55c6f">Can I add more users to the system?</h2>
|
|
394
|
|
-<div class="outline-text-2" id="text-org8a55c6f">
|
|
|
392
|
+<div id="outline-container-org36b6c2a" class="outline-2">
|
|
|
393
|
+<h2 id="org36b6c2a">Can I add more users to the system?</h2>
|
|
|
394
|
+<div class="outline-text-2" id="text-org36b6c2a">
|
|
395
|
395
|
<p>
|
|
396
|
396
|
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).
|
|
397
|
397
|
</p>
|
|
|
@@ -415,9 +415,9 @@ Another point is that Freedombone installations are not intended to support many
|
|
415
|
415
|
</p>
|
|
416
|
416
|
</div>
|
|
417
|
417
|
</div>
|
|
418
|
|
-<div id="outline-container-orgdc06783" class="outline-2">
|
|
419
|
|
-<h2 id="orgdc06783">Why not use Signal for mobile chat?</h2>
|
|
420
|
|
-<div class="outline-text-2" id="text-orgdc06783">
|
|
|
418
|
+<div id="outline-container-orgd747625" class="outline-2">
|
|
|
419
|
+<h2 id="orgd747625">Why not use Signal for mobile chat?</h2>
|
|
|
420
|
+<div class="outline-text-2" id="text-orgd747625">
|
|
421
|
421
|
<p>
|
|
422
|
422
|
Celebrities recommend Signal. It's Free Software so it must be good, right?
|
|
423
|
423
|
</p>
|
|
|
@@ -430,13 +430,13 @@ If you are currently using a proprietary chat app, something without any encrypt
|
|
430
|
430
|
<li><b>It's based on a single server</b> run by Open Whisper Systems. That's a single point of failure and ought to be a big red flag (of the sporting rather than the socialist variety) as a possible locus for concentrated nefariousness.</li>
|
|
431
|
431
|
<li><b>It requires the installation of Google Play</b>. If you already have Google Play installed on a stock Android OS then this doesn't increase your security problems, but for other more secure Android variants it's a massive increase in attack surface.</li>
|
|
432
|
432
|
<li><b>It depends entirely upon the Google message pushing system</b>. That means that Google <i>at least knows who Signal messages are being sent to and may be able to infer the rest via your (insecure) Android phone contact list or via timing correlation of alternating deliveries</i>. Remember that for an adversary metadata in aggregate is much better than having the content of messages. At any time Google could decide that it doesn't want to support Signal, or in adverse circumstances they could be leaned upon by the usual agencies or government cronies.</li>
|
|
433
|
|
-<li>Their privacy policy indicates that they will give whatever server data they have to third parties under some conditions. Of course this is always claimed to be <i>for the very best of reasons</i> - such as combating fraud - but once that sort of disclosure capability exists it may be abused without you ever knowing about it.</li>
|
|
|
433
|
+<li><b>Their privacy policy indicates that they will give whatever server data they have to third parties</b> under some conditions. Of course this is always claimed to be <i>for the very best of reasons</i> - such as combating fraud - but once that sort of disclosure capability exists it may be abused without you ever knowing about it.</li>
|
|
434
|
434
|
</ul>
|
|
435
|
435
|
</div>
|
|
436
|
436
|
</div>
|
|
437
|
|
-<div id="outline-container-org61fd356" class="outline-2">
|
|
438
|
|
-<h2 id="org61fd356">What is the most secure chat app to use on mobile?</h2>
|
|
439
|
|
-<div class="outline-text-2" id="text-org61fd356">
|
|
|
437
|
+<div id="outline-container-orgca1e6b9" class="outline-2">
|
|
|
438
|
+<h2 id="orgca1e6b9">What is the most secure chat app to use on mobile?</h2>
|
|
|
439
|
+<div class="outline-text-2" id="text-orgca1e6b9">
|
|
440
|
440
|
<p>
|
|
441
|
441
|
On mobile there are various options. The apps which are likely to be most secure are ones which have end-to-end encryption enabled by default and which can also be onion routed via Orbot. End-to-end encryption secures the content of the message and onion routing obscures the metadata, making it hard for a passive adversary to know who is communicating with who.
|
|
442
|
442
|
</p>
|
|
|
@@ -450,9 +450,9 @@ There are many other fashionable chat apps with end-to-end security, but often t
|
|
450
|
450
|
</p>
|
|
451
|
451
|
</div>
|
|
452
|
452
|
</div>
|
|
453
|
|
-<div id="outline-container-orgb130d15" class="outline-2">
|
|
454
|
|
-<h2 id="orgb130d15">How do I remove a user from the system?</h2>
|
|
455
|
|
-<div class="outline-text-2" id="text-orgb130d15">
|
|
|
453
|
+<div id="outline-container-org2ec102d" class="outline-2">
|
|
|
454
|
+<h2 id="org2ec102d">How do I remove a user from the system?</h2>
|
|
|
455
|
+<div class="outline-text-2" id="text-org2ec102d">
|
|
456
|
456
|
<p>
|
|
457
|
457
|
To remove a user:
|
|
458
|
458
|
</p>
|
|
|
@@ -468,9 +468,9 @@ Select <i>Administrator controls</i> then <i>Manage Users</i> and then <i>Delete
|
|
468
|
468
|
</p>
|
|
469
|
469
|
</div>
|
|
470
|
470
|
</div>
|
|
471
|
|
-<div id="outline-container-orgf592313" class="outline-2">
|
|
472
|
|
-<h2 id="orgf592313">How do I reset the tripwire?</h2>
|
|
473
|
|
-<div class="outline-text-2" id="text-orgf592313">
|
|
|
471
|
+<div id="outline-container-org342cf1c" class="outline-2">
|
|
|
472
|
+<h2 id="org342cf1c">How do I reset the tripwire?</h2>
|
|
|
473
|
+<div class="outline-text-2" id="text-org342cf1c">
|
|
474
|
474
|
<p>
|
|
475
|
475
|
The tripwire will be automatically reset once per week. If you want to reset it earlier then do the following:
|
|
476
|
476
|
</p>
|
|
|
@@ -486,9 +486,9 @@ Select <i>Administrator controls</i> then "reset tripwire" using cursors and spa
|
|
486
|
486
|
</p>
|
|
487
|
487
|
</div>
|
|
488
|
488
|
</div>
|
|
489
|
|
-<div id="outline-container-org3372f2a" class="outline-2">
|
|
490
|
|
-<h2 id="org3372f2a">Is metadata protected?</h2>
|
|
491
|
|
-<div class="outline-text-2" id="text-org3372f2a">
|
|
|
489
|
+<div id="outline-container-org59a89db" class="outline-2">
|
|
|
490
|
+<h2 id="org59a89db">Is metadata protected?</h2>
|
|
|
491
|
+<div class="outline-text-2" id="text-org59a89db">
|
|
492
|
492
|
<blockquote>
|
|
493
|
493
|
<p>
|
|
494
|
494
|
"<i>We kill people based on metadata</i>"
|
|
|
@@ -504,9 +504,9 @@ Even when using Freedombone metadata analysis by third parties is still possible
|
|
504
|
504
|
</p>
|
|
505
|
505
|
</div>
|
|
506
|
506
|
</div>
|
|
507
|
|
-<div id="outline-container-org3c8f887" class="outline-2">
|
|
508
|
|
-<h2 id="org3c8f887">How do I create email processing rules?</h2>
|
|
509
|
|
-<div class="outline-text-2" id="text-org3c8f887">
|
|
|
507
|
+<div id="outline-container-org15832a" class="outline-2">
|
|
|
508
|
+<h2 id="org15832a">How do I create email processing rules?</h2>
|
|
|
509
|
+<div class="outline-text-2" id="text-org15832a">
|
|
510
|
510
|
<div class="org-src-container">
|
|
511
|
511
|
|
|
512
|
512
|
<pre class="src src-bash">ssh username@domainname -p 2222
|
|
|
@@ -563,9 +563,9 @@ Spamassassin is also available and within Mutt you can use the S (shift+s) key t
|
|
563
|
563
|
</p>
|
|
564
|
564
|
</div>
|
|
565
|
565
|
</div>
|
|
566
|
|
-<div id="outline-container-orgf4dca3f" class="outline-2">
|
|
567
|
|
-<h2 id="orgf4dca3f">Why isn't dynamic DNS working?</h2>
|
|
568
|
|
-<div class="outline-text-2" id="text-orgf4dca3f">
|
|
|
566
|
+<div id="outline-container-org4b5ee4" class="outline-2">
|
|
|
567
|
+<h2 id="org4b5ee4">Why isn't dynamic DNS working?</h2>
|
|
|
568
|
+<div class="outline-text-2" id="text-org4b5ee4">
|
|
569
|
569
|
<p>
|
|
570
|
570
|
If you run the command:
|
|
571
|
571
|
</p>
|
|
|
@@ -633,9 +633,9 @@ http://httpbin.org/ip
|
|
633
|
633
|
</div>
|
|
634
|
634
|
</div>
|
|
635
|
635
|
|
|
636
|
|
-<div id="outline-container-orga5c8552" class="outline-2">
|
|
637
|
|
-<h2 id="orga5c8552">How do I change my encryption settings?</h2>
|
|
638
|
|
-<div class="outline-text-2" id="text-orga5c8552">
|
|
|
636
|
+<div id="outline-container-org9794585" class="outline-2">
|
|
|
637
|
+<h2 id="org9794585">How do I change my encryption settings?</h2>
|
|
|
638
|
+<div class="outline-text-2" id="text-org9794585">
|
|
639
|
639
|
<p>
|
|
640
|
640
|
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:
|
|
641
|
641
|
</p>
|
|
|
@@ -651,9 +651,9 @@ Select <i>Administrator controls</i> then select <i>Security Settings</i>. You w
|
|
651
|
651
|
</p>
|
|
652
|
652
|
</div>
|
|
653
|
653
|
</div>
|
|
654
|
|
-<div id="outline-container-org63db5c8" class="outline-2">
|
|
655
|
|
-<h2 id="org63db5c8">How do I get a domain name?</h2>
|
|
656
|
|
-<div class="outline-text-2" id="text-org63db5c8">
|
|
|
654
|
+<div id="outline-container-orga064d94" class="outline-2">
|
|
|
655
|
+<h2 id="orga064d94">How do I get a domain name?</h2>
|
|
|
656
|
+<div class="outline-text-2" id="text-orga064d94">
|
|
657
|
657
|
<p>
|
|
658
|
658
|
Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
|
|
659
|
659
|
</p>
|
|
|
@@ -721,9 +721,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
|
|
721
|
721
|
</div>
|
|
722
|
722
|
</div>
|
|
723
|
723
|
|
|
724
|
|
-<div id="outline-container-orgdfe03d7" class="outline-2">
|
|
725
|
|
-<h2 id="orgdfe03d7">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
|
|
726
|
|
-<div class="outline-text-2" id="text-orgdfe03d7">
|
|
|
724
|
+<div id="outline-container-orgdfc40b" class="outline-2">
|
|
|
725
|
+<h2 id="orgdfc40b">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
|
|
|
726
|
+<div class="outline-text-2" id="text-orgdfc40b">
|
|
727
|
727
|
<p>
|
|
728
|
728
|
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:
|
|
729
|
729
|
</p>
|
|
|
@@ -743,9 +743,9 @@ One thing to be aware of is that Let's Encrypt doesn't support many dynamic DNS
|
|
743
|
743
|
</p>
|
|
744
|
744
|
</div>
|
|
745
|
745
|
</div>
|
|
746
|
|
-<div id="outline-container-org1836ba3" class="outline-2">
|
|
747
|
|
-<h2 id="org1836ba3">How do I renew a Let's Encrypt certificate?</h2>
|
|
748
|
|
-<div class="outline-text-2" id="text-org1836ba3">
|
|
|
746
|
+<div id="outline-container-org7f7ddb7" class="outline-2">
|
|
|
747
|
+<h2 id="org7f7ddb7">How do I renew a Let's Encrypt certificate?</h2>
|
|
|
748
|
+<div class="outline-text-2" id="text-org7f7ddb7">
|
|
749
|
749
|
<p>
|
|
750
|
750
|
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.
|
|
751
|
751
|
</p>
|
|
|
@@ -765,9 +765,9 @@ Select <i>Administrator controls</i> then <b>Security settings</b> then <b>Renew
|
|
765
|
765
|
</p>
|
|
766
|
766
|
</div>
|
|
767
|
767
|
</div>
|
|
768
|
|
-<div id="outline-container-org7fcac9e" class="outline-2">
|
|
769
|
|
-<h2 id="org7fcac9e">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
|
|
770
|
|
-<div class="outline-text-2" id="text-org7fcac9e">
|
|
|
768
|
+<div id="outline-container-orgdfe7bea" class="outline-2">
|
|
|
769
|
+<h2 id="orgdfe7bea">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
|
|
|
770
|
+<div class="outline-text-2" id="text-orgdfe7bea">
|
|
771
|
771
|
<p>
|
|
772
|
772
|
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:
|
|
773
|
773
|
</p>
|
|
|
@@ -783,9 +783,9 @@ Select <i>Administrator controls</i> then <b>Security settings</b> then <b>Creat
|
|
783
|
783
|
</p>
|
|
784
|
784
|
</div>
|
|
785
|
785
|
</div>
|
|
786
|
|
-<div id="outline-container-org4092726" class="outline-2">
|
|
787
|
|
-<h2 id="org4092726">Why use self-signed certificates?</h2>
|
|
788
|
|
-<div class="outline-text-2" id="text-org4092726">
|
|
|
786
|
+<div id="outline-container-org6b4c194" class="outline-2">
|
|
|
787
|
+<h2 id="org6b4c194">Why use self-signed certificates?</h2>
|
|
|
788
|
+<div class="outline-text-2" id="text-org6b4c194">
|
|
789
|
789
|
<p>
|
|
790
|
790
|
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>.
|
|
791
|
791
|
</p>
|
|
|
@@ -807,17 +807,17 @@ For now a self-signed certificate will probably in most cases protect your commu
|
|
807
|
807
|
</p>
|
|
808
|
808
|
</div>
|
|
809
|
809
|
</div>
|
|
810
|
|
-<div id="outline-container-org1eadbae" class="outline-2">
|
|
811
|
|
-<h2 id="org1eadbae">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
|
812
|
|
-<div class="outline-text-2" id="text-org1eadbae">
|
|
|
810
|
+<div id="outline-container-orga3f84a2" class="outline-2">
|
|
|
811
|
+<h2 id="orga3f84a2">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
|
|
812
|
+<div class="outline-text-2" id="text-orga3f84a2">
|
|
813
|
813
|
<p>
|
|
814
|
814
|
<a href="https://cryptostorm.org/viewtopic.php?f=63&t=2954&sid=7de2d1e699cfde2f574e6a7f6ea5a173">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.
|
|
815
|
815
|
</p>
|
|
816
|
816
|
</div>
|
|
817
|
817
|
</div>
|
|
818
|
|
-<div id="outline-container-orge2c17a0" class="outline-2">
|
|
819
|
|
-<h2 id="orge2c17a0">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
|
820
|
|
-<div class="outline-text-2" id="text-orge2c17a0">
|
|
|
818
|
+<div id="outline-container-org997489b" class="outline-2">
|
|
|
819
|
+<h2 id="org997489b">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
|
|
820
|
+<div class="outline-text-2" id="text-org997489b">
|
|
821
|
821
|
<p>
|
|
822
|
822
|
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 you may not be able to do much unless you can find an email proxy server which is trusted by the receiving server.
|
|
823
|
823
|
</p>
|
Bob Mottram
vor 8 Jahren