Multiple users
This commit is contained in:
Bob Mottram
parent
22324c48f5
commit
6d02c62c95
|
|
@ -12,6 +12,7 @@
|
|||
#+ATTR_HTML: :border -1
|
||||
| [[file:index.html][Home]] |
|
||||
| [[Why not supply a disk image download?]] |
|
||||
| [[Can I add more users to the system?]] |
|
||||
| [[Is metadata protected?]] |
|
||||
| [[Why isn't dynamic DNS working?]] |
|
||||
| [[How do I get a domain name?]] |
|
||||
|
|
@ -23,6 +24,8 @@
|
|||
|
||||
* Why not supply a disk image download?
|
||||
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.
|
||||
* Can I add more users to the system?
|
||||
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.
|
||||
* Is metadata protected?
|
||||
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.
|
||||
* Why isn't dynamic DNS working?
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title></title>
|
||||
<!-- 2015-03-01 Sun 14:02 -->
|
||||
<!-- 2015-03-07 Sat 13:17 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="generator" content="Org-mode" />
|
||||
<meta name="author" content="Bob Mottram" />
|
||||
|
|
@ -15,7 +15,8 @@
|
|||
<!--/*--><![CDATA[/*><!--*/
|
||||
.title { text-align: center; }
|
||||
.todo { font-family: monospace; color: red; }
|
||||
.done { color: green; }
|
||||
.done { font-family: monospace; color: green; }
|
||||
.priority { font-family: monospace; color: orange; }
|
||||
.tag { background-color: #eee; font-family: monospace;
|
||||
padding: 2px; font-size: 80%; font-weight: normal; }
|
||||
.timestamp { color: #bebebe; }
|
||||
|
|
@ -173,31 +174,35 @@ for the JavaScript code in this tag.
|
|||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-2">Is metadata protected?</a></td>
|
||||
<td class="left"><a href="#unnumbered-2">Can I add more users to the system?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-3">Why isn't dynamic DNS working?</a></td>
|
||||
<td class="left"><a href="#unnumbered-3">Is metadata protected?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-4">How do I get a domain name?</a></td>
|
||||
<td class="left"><a href="#unnumbered-4">Why isn't dynamic DNS working?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-5">How do I get a "real" SSL certificate?</a></td>
|
||||
<td class="left"><a href="#unnumbered-5">How do I get a domain name?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-6">Why use self-signed certificates?</a></td>
|
||||
<td class="left"><a href="#unnumbered-6">How do I get a "real" SSL certificate?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-7">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
||||
<td class="left"><a href="#unnumbered-7">Why use self-signed certificates?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-8">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
||||
<td class="left"><a href="#unnumbered-8">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#unnumbered-9">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -212,16 +217,24 @@ Shipping a Freedombone disk image ready to install on a flash disk would be easy
|
|||
</div>
|
||||
</div>
|
||||
<div id="outline-container-unnumbered-2" class="outline-2">
|
||||
<h2 id="unnumbered-2">Is metadata protected?</h2>
|
||||
<h2 id="unnumbered-2">Can I add more users to the system?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-2">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-unnumbered-3" class="outline-2">
|
||||
<h2 id="unnumbered-3">Is metadata protected?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-3">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-unnumbered-3" class="outline-2">
|
||||
<h2 id="unnumbered-3">Why isn't dynamic DNS working?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-3">
|
||||
<div id="outline-container-unnumbered-4" class="outline-2">
|
||||
<h2 id="unnumbered-4">Why isn't dynamic DNS working?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-4">
|
||||
<p>
|
||||
If you run the command:
|
||||
</p>
|
||||
|
|
@ -289,9 +302,9 @@ http://httpbin.org/ip
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-unnumbered-4" class="outline-2">
|
||||
<h2 id="unnumbered-4">How do I get a domain name?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-4">
|
||||
<div id="outline-container-unnumbered-5" class="outline-2">
|
||||
<h2 id="unnumbered-5">How do I get a domain name?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-5">
|
||||
<p>
|
||||
Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
|
||||
</p>
|
||||
|
|
@ -359,9 +372,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-unnumbered-5" class="outline-2">
|
||||
<h2 id="unnumbered-5">How do I get a "real" SSL certificate?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-5">
|
||||
<div id="outline-container-unnumbered-6" class="outline-2">
|
||||
<h2 id="unnumbered-6">How do I get a "real" SSL certificate?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-6">
|
||||
<p>
|
||||
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).
|
||||
</p>
|
||||
|
|
@ -536,14 +549,14 @@ Save and exit, then restart the web server.
|
|||
</div>
|
||||
|
||||
<p>
|
||||
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>.
|
||||
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>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-unnumbered-6" class="outline-2">
|
||||
<h2 id="unnumbered-6">Why use self-signed certificates?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-6">
|
||||
<div id="outline-container-unnumbered-7" class="outline-2">
|
||||
<h2 id="unnumbered-7">Why use self-signed certificates?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-7">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -557,17 +570,17 @@ For now a self-signed certificate will probably in most cases protect your commu
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-unnumbered-7" class="outline-2">
|
||||
<h2 id="unnumbered-7">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-7">
|
||||
<div id="outline-container-unnumbered-8" class="outline-2">
|
||||
<h2 id="unnumbered-8">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-8">
|
||||
<p>
|
||||
<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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-unnumbered-8" class="outline-2">
|
||||
<h2 id="unnumbered-8">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-8">
|
||||
<div id="outline-container-unnumbered-9" class="outline-2">
|
||||
<h2 id="unnumbered-9">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
||||
<div class="outline-text-2" id="text-unnumbered-9">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue