Kaynağa Gözat

Multiple users

Bob Mottram 10 yıl önce
ebeveyn
işleme
6d02c62c95
2 değiştirilmiş dosya ile 44 ekleme ve 28 silme
  1. 3
    0
      doc/EN/faq.org
  2. 41
    28
      website/EN/faq.html

+ 3
- 0
doc/EN/faq.org Dosyayı Görüntüle

@@ -12,6 +12,7 @@
12 12
 #+ATTR_HTML: :border -1
13 13
 | [[file:index.html][Home]]                                                                       |
14 14
 | [[Why not supply a disk image download?]]                                      |
15
+| [[Can I add more users to the system?]]                                        |
15 16
 | [[Is metadata protected?]]                                                     |
16 17
 | [[Why isn't dynamic DNS working?]]                                             |
17 18
 | [[How do I get a domain name?]]                                                |
@@ -23,6 +24,8 @@
23 24
 
24 25
 * Why not supply a disk image download?
25 26
 Shipping a Freedombone disk image ready to install on a flash disk would be easy, but disk images are relatively opaque. It would be quite easy to hide something nasty within a disk image and the user might never know. To guard against that possibility installing via the *freedombone* command is a lot more transparent, since it's really just a bash script. You can check the script code to see exactly what it's doing, and the packages are all downloaded from standard Debian repos (you can even choose which one you trust) or git repos. Doing it this way the system is fully auditable, whereas when shipping a disk image it's harder to be confident that no nefarious extras have been added.
27
+* Can I add more users to the system?
28
+Like any other GNU/Linux system you can add more users. It's easy to add users to Owncloud, XMPP or RedMatrix. However, Freedombone is designed primarily to be a single user system (i.e. a personal server) and if there are multiple users then the number of them is expected to be small - perhaps five or less. Freedombone is not intended to be "/web scale/" in terms of supporting tens or hundreds of users on a single server. Instead, each server can host a small number of users and then the servers federate together as a network of peers.
26 29
 * Is metadata protected?
27 30
 Even when using Freedombone metadata analysis by third parties is still possible. They might have a much harder time knowing what the content is, but they can potentially construct extensive dossiers based upon who communicated with your server when.  Metadata leakage is a general problem with most current web systems and it is hoped that more secure technology will become available in future. But for now if metadata protection is your main concern using Freedombone won't help.
28 31
 * Why isn't dynamic DNS working?

+ 41
- 28
website/EN/faq.html Dosyayı Görüntüle

@@ -4,7 +4,7 @@
4 4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5
 <head>
6 6
 <title></title>
7
-<!-- 2015-03-01 Sun 14:02 -->
7
+<!-- 2015-03-07 Sat 13:17 -->
8 8
 <meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
9 9
 <meta  name="generator" content="Org-mode" />
10 10
 <meta  name="author" content="Bob Mottram" />
@@ -15,7 +15,8 @@
15 15
  <!--/*--><![CDATA[/*><!--*/
16 16
   .title  { text-align: center; }
17 17
   .todo   { font-family: monospace; color: red; }
18
-  .done   { color: green; }
18
+  .done   { font-family: monospace; color: green; }
19
+  .priority { font-family: monospace; color: orange; }
19 20
   .tag    { background-color: #eee; font-family: monospace;
20 21
             padding: 2px; font-size: 80%; font-weight: normal; }
21 22
   .timestamp { color: #bebebe; }
@@ -173,31 +174,35 @@ for the JavaScript code in this tag.
173 174
 </tr>
174 175
 
175 176
 <tr>
176
-<td class="left"><a href="#unnumbered-2">Is metadata protected?</a></td>
177
+<td class="left"><a href="#unnumbered-2">Can I add more users to the system?</a></td>
177 178
 </tr>
178 179
 
179 180
 <tr>
180
-<td class="left"><a href="#unnumbered-3">Why isn't dynamic DNS working?</a></td>
181
+<td class="left"><a href="#unnumbered-3">Is metadata protected?</a></td>
181 182
 </tr>
182 183
 
183 184
 <tr>
184
-<td class="left"><a href="#unnumbered-4">How do I get a domain name?</a></td>
185
+<td class="left"><a href="#unnumbered-4">Why isn't dynamic DNS working?</a></td>
185 186
 </tr>
186 187
 
187 188
 <tr>
188
-<td class="left"><a href="#unnumbered-5">How do I get a "real" SSL certificate?</a></td>
189
+<td class="left"><a href="#unnumbered-5">How do I get a domain name?</a></td>
189 190
 </tr>
190 191
 
191 192
 <tr>
192
-<td class="left"><a href="#unnumbered-6">Why use self-signed certificates?</a></td>
193
+<td class="left"><a href="#unnumbered-6">How do I get a "real" SSL certificate?</a></td>
193 194
 </tr>
194 195
 
195 196
 <tr>
196
-<td class="left"><a href="#unnumbered-7">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
197
+<td class="left"><a href="#unnumbered-7">Why use self-signed certificates?</a></td>
197 198
 </tr>
198 199
 
199 200
 <tr>
200
-<td class="left"><a href="#unnumbered-8">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
201
+<td class="left"><a href="#unnumbered-8">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
202
+</tr>
203
+
204
+<tr>
205
+<td class="left"><a href="#unnumbered-9">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
201 206
 </tr>
202 207
 </tbody>
203 208
 </table>
@@ -212,17 +217,25 @@ Shipping a Freedombone disk image ready to install on a flash disk would be easy
212 217
 </div>
213 218
 </div>
214 219
 <div id="outline-container-unnumbered-2" class="outline-2">
215
-<h2 id="unnumbered-2">Is metadata protected?</h2>
220
+<h2 id="unnumbered-2">Can I add more users to the system?</h2>
216 221
 <div class="outline-text-2" id="text-unnumbered-2">
217 222
 <p>
218
-Even when using Freedombone metadata analysis by third parties is still possible. They might have a much harder time knowing what the content is, but they can potentially construct extensive dossiers based upon who communicated with your server when.  Metadata leakage is a general problem with most current web systems and it is hoped that more secure technology will become available in future. But for now if metadata protection is your main concern using Freedombone won't help.
223
+Like any other GNU/Linux system you can add more users. It's easy to add users to Owncloud, XMPP or RedMatrix. However, Freedombone is designed primarily to be a single user system (i.e. a personal server) and if there are multiple users then the number of them is expected to be small - perhaps five or less. Freedombone is not intended to be "<i>web scale</i>" in terms of supporting tens or hundreds of users on a single server. Instead, each server can host a small number of users and then the servers federate together as a network of peers.
219 224
 </p>
220 225
 </div>
221 226
 </div>
222 227
 <div id="outline-container-unnumbered-3" class="outline-2">
223
-<h2 id="unnumbered-3">Why isn't dynamic DNS working?</h2>
228
+<h2 id="unnumbered-3">Is metadata protected?</h2>
224 229
 <div class="outline-text-2" id="text-unnumbered-3">
225 230
 <p>
231
+Even when using Freedombone metadata analysis by third parties is still possible. They might have a much harder time knowing what the content is, but they can potentially construct extensive dossiers based upon who communicated with your server when.  Metadata leakage is a general problem with most current web systems and it is hoped that more secure technology will become available in future. But for now if metadata protection is your main concern using Freedombone won't help.
232
+</p>
233
+</div>
234
+</div>
235
+<div id="outline-container-unnumbered-4" class="outline-2">
236
+<h2 id="unnumbered-4">Why isn't dynamic DNS working?</h2>
237
+<div class="outline-text-2" id="text-unnumbered-4">
238
+<p>
226 239
 If you run the command:
227 240
 </p>
228 241
 
@@ -289,9 +302,9 @@ http://httpbin.org/ip
289 302
 </div>
290 303
 </div>
291 304
 
292
-<div id="outline-container-unnumbered-4" class="outline-2">
293
-<h2 id="unnumbered-4">How do I get a domain name?</h2>
294
-<div class="outline-text-2" id="text-unnumbered-4">
305
+<div id="outline-container-unnumbered-5" class="outline-2">
306
+<h2 id="unnumbered-5">How do I get a domain name?</h2>
307
+<div class="outline-text-2" id="text-unnumbered-5">
295 308
 <p>
296 309
 Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
297 310
 </p>
@@ -359,9 +372,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
359 372
 </div>
360 373
 </div>
361 374
 
362
-<div id="outline-container-unnumbered-5" class="outline-2">
363
-<h2 id="unnumbered-5">How do I get a "real" SSL certificate?</h2>
364
-<div class="outline-text-2" id="text-unnumbered-5">
375
+<div id="outline-container-unnumbered-6" class="outline-2">
376
+<h2 id="unnumbered-6">How do I get a "real" SSL certificate?</h2>
377
+<div class="outline-text-2" id="text-unnumbered-6">
365 378
 <p>
366 379
 You can obtain a free "official" (as in recognised by default by web browsers) SSL certificate from <a href="https://www.startssl.com/">StartSSL</a>. You will first need to have bought a domain name, since it's not possible to obtain one for a freedns subdomain, so see <i>Using your own domain</i> for details of how to do that.  You should also have tested that you can send email to the domain and receive it on the Freedombone (via Mutt or any other email client).
367 380
 </p>
@@ -536,14 +549,14 @@ Save and exit, then restart the web server.
536 549
 </div>
537 550
 
538 551
 <p>
539
-Now visit your web site at <a href="https://mydomainname.com/">https://mydomainname.com/</a> and you should notice that there is no certificate warning displayed.  You will now be able to install systems which don't allow the use of self-signed certificates, such as <a href="https://redmatrix.me/&JS=1">Red Matrix</a>.
552
+Now visit your web site at <a href="https://mydomainname.com/">https://mydomainname.com/</a> and you should notice that there is no certificate warning displayed.  You will now be able to install systems which don't allow the use of self-signed certificates, such as <a href="https://redmatrix.me/&amp;JS=1">Red Matrix</a>.
540 553
 </p>
541 554
 </div>
542 555
 </div>
543 556
 
544
-<div id="outline-container-unnumbered-6" class="outline-2">
545
-<h2 id="unnumbered-6">Why use self-signed certificates?</h2>
546
-<div class="outline-text-2" id="text-unnumbered-6">
557
+<div id="outline-container-unnumbered-7" class="outline-2">
558
+<h2 id="unnumbered-7">Why use self-signed certificates?</h2>
559
+<div class="outline-text-2" id="text-unnumbered-7">
547 560
 <p>
548 561
 Almost everywhere on the web you will read that self-signed certificates are worthless. They bring up scary looking 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>. The usual solution to this is to get a "real" SSL certificate from one of the certificate authorities, but it's far from clear that such authorities can be trusted. There have been various scandals involving such organisations, and it does not seem plausible to assume that they are somehow immune to the sort of treatment which <a href="http://en.wikipedia.org/wiki/Lavabit">Lavabit</a> received. So although most internet users have been trained to look for the lock icon as an indication that the connection is secured that belief may not always be well founded.
549 562
 </p>
@@ -557,17 +570,17 @@ For now a self-signed certificate will probably in most cases protect your commu
557 570
 </p>
558 571
 </div>
559 572
 </div>
560
-<div id="outline-container-unnumbered-7" class="outline-2">
561
-<h2 id="unnumbered-7">Why not use the services of $company instead? They took the Seppuku pledge</h2>
562
-<div class="outline-text-2" id="text-unnumbered-7">
573
+<div id="outline-container-unnumbered-8" class="outline-2">
574
+<h2 id="unnumbered-8">Why not use the services of $company instead? They took the Seppuku pledge</h2>
575
+<div class="outline-text-2" id="text-unnumbered-8">
563 576
 <p>
564 577
 <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.
565 578
 </p>
566 579
 </div>
567 580
 </div>
568
-<div id="outline-container-unnumbered-8" class="outline-2">
569
-<h2 id="unnumbered-8">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
570
-<div class="outline-text-2" id="text-unnumbered-8">
581
+<div id="outline-container-unnumbered-9" class="outline-2">
582
+<h2 id="unnumbered-9">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
583
+<div class="outline-text-2" id="text-unnumbered-9">
571 584
 <p>
572 585
 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.
573 586
 </p>