faq
This commit is contained in:
Bob Mottram
parent
baf7179f73
commit
54a585b620
|
|
@ -15,6 +15,7 @@
|
|||
| [[I don't have a static IP address. Can I still install this system?]] |
|
||||
| [[What is the best hardware to run this system on?]] |
|
||||
| [[Can I add more users to the system?]] |
|
||||
| [[How do I remove a user from the system?]] |
|
||||
| [[How do I reset the tripwire?]] |
|
||||
| [[Is metadata protected?]] |
|
||||
| [[How do I create email processing rules?]] |
|
||||
|
|
@ -39,7 +40,21 @@ It was originally designed to run on the Beaglebone Black, but that should be re
|
|||
|
||||
/Out of fashion/ but still working computer hardware tends to be cheap and readily available, yet still good for providing internet services.
|
||||
* 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 Hubzilla. 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.
|
||||
Yes. Freedombone can support a small number of users, for a "/friends and family/" type of home installation. This gives them access to an email account, XMPP and the blog (depending on whether the variant which you installed includes those). To add a user login as root then run the command:
|
||||
|
||||
#+BEGIN_SRC bash
|
||||
freedombone-adduser [username]
|
||||
#+END_SRC
|
||||
|
||||
Something to consider when having more than a single user on the system is the security situation. The original administrator user will have access to all of the data for other users (including their encryption keys), so if you do add extra users they need to have *complete trust* in the administrator.
|
||||
|
||||
Another point is that Freedombone installations are not intended to support many users (maybe ten at most). Large numbers of users may make the system unstable, and the more users you have on one system the more it becomes a single point of failure and also perhaps a honeypot from the standpoint of adversaries. Think of what happened with Lavabit and the moral dilemma which an administrator can be faced with (comply with threats and betray the trust of your users or don't comply and suffer other consequences). Ideally, you never want to put yourself into a situation where you can be forced to betray others.
|
||||
* How do I remove a user from the system?
|
||||
To remove a user login as root then run the command:
|
||||
|
||||
#+BEGIN_SRC bash
|
||||
freedombone-rmuser [username]
|
||||
#+END_SRC
|
||||
* How do I reset the tripwire?
|
||||
You will get a daily email which indicates which files on the system have changed recently. Once per week the system will install any updates and those may also show up on the list, along with any changes due to installed packages or changed settings. Watch out for any files which change unexpectedly, which could indicate an intruder. To reset the tripwire:
|
||||
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -4,32 +4,25 @@
|
|||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title></title>
|
||||
<!-- 2015-09-08 Tue 19:27 -->
|
||||
<!-- 2015-10-27 Tue 11:37 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="generator" content="Org-mode" />
|
||||
<meta name="author" content="Bob Mottram" />
|
||||
<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
|
||||
/>
|
||||
<meta name="keywords" content="freedombox, debian, beaglebone, hubzilla, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<style type="text/css">
|
||||
<!--/*--><![CDATA[/*><!--*/
|
||||
.title { text-align: center;
|
||||
margin-bottom: .2em; }
|
||||
.subtitle { text-align: center;
|
||||
font-size: medium;
|
||||
font-weight: bold;
|
||||
margin-top:0; }
|
||||
.title { text-align: center; }
|
||||
.todo { font-family: monospace; color: red; }
|
||||
.done { font-family: monospace; color: green; }
|
||||
.priority { font-family: monospace; color: orange; }
|
||||
.done { color: green; }
|
||||
.tag { background-color: #eee; font-family: monospace;
|
||||
padding: 2px; font-size: 80%; font-weight: normal; }
|
||||
.timestamp { color: #bebebe; }
|
||||
.timestamp-kwd { color: #5f9ea0; }
|
||||
.org-right { margin-left: auto; margin-right: 0px; text-align: right; }
|
||||
.org-left { margin-left: 0px; margin-right: auto; text-align: left; }
|
||||
.org-center { margin-left: auto; margin-right: auto; text-align: center; }
|
||||
.right { margin-left: auto; margin-right: 0px; text-align: right; }
|
||||
.left { margin-left: 0px; margin-right: auto; text-align: left; }
|
||||
.center { margin-left: auto; margin-right: auto; text-align: center; }
|
||||
.underline { text-decoration: underline; }
|
||||
#postamble p, #preamble p { font-size: 90%; margin: .2em; }
|
||||
p.verse { margin-left: 3%; }
|
||||
|
|
@ -68,12 +61,12 @@
|
|||
caption.t-above { caption-side: top; }
|
||||
caption.t-bottom { caption-side: bottom; }
|
||||
td, th { vertical-align:top; }
|
||||
th.org-right { text-align: center; }
|
||||
th.org-left { text-align: center; }
|
||||
th.org-center { text-align: center; }
|
||||
td.org-right { text-align: right; }
|
||||
td.org-left { text-align: left; }
|
||||
td.org-center { text-align: center; }
|
||||
th.right { text-align: center; }
|
||||
th.left { text-align: center; }
|
||||
th.center { text-align: center; }
|
||||
td.right { text-align: right; }
|
||||
td.left { text-align: left; }
|
||||
td.center { text-align: center; }
|
||||
dt { font-weight: bold; }
|
||||
.footpara:nth-child(2) { display: inline; }
|
||||
.footpara { display: block; }
|
||||
|
|
@ -98,10 +91,6 @@
|
|||
{ background-color: #ffff00; color: #000000; font-weight: bold; }
|
||||
/*]]>*/-->
|
||||
</style>
|
||||
<link rel="stylesheet" type="text/css"
|
||||
href="http://sachachua.com/blog/wp-content/themes/sacha-v3/foundation/css/foundation.min.css"></link>
|
||||
<link rel="stylesheet" type="text/css" href="http://sachachua.com/org-export.css"></link>
|
||||
<link rel="stylesheet" type="text/css" href="http://sachachua.com/blog/wp-content/themes/sacha-v3/style.css"></link>
|
||||
<script type="text/javascript">
|
||||
/*
|
||||
@licstart The following is the entire license notice for the
|
||||
|
|
@ -150,10 +139,8 @@ for the JavaScript code in this tag.
|
|||
</script>
|
||||
</head>
|
||||
<body>
|
||||
<div id="preamble" class="status">
|
||||
<a name="top" id="top"></a>
|
||||
</div>
|
||||
<div id="content">
|
||||
<h1 class="title"></h1>
|
||||
<div class="center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -167,87 +154,91 @@ for the JavaScript code in this tag.
|
|||
|
||||
|
||||
<colgroup>
|
||||
<col class="org-left" />
|
||||
<col class="left" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td class="org-left"><a href="index.html">Home</a></td>
|
||||
<td class="left"><a href="index.html">Home</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline1">Why not supply a disk image download?</a></td>
|
||||
<td class="left"><a href="#sec-1">1</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline2">I don't have a static IP address. Can I still install this system?</a></td>
|
||||
<td class="left"><a href="#sec-2">2</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline3">What is the best hardware to run this system on?</a></td>
|
||||
<td class="left"><a href="#sec-3">3</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline4">Can I add more users to the system?</a></td>
|
||||
<td class="left"><a href="#sec-4">4</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline5">How do I reset the tripwire?</a></td>
|
||||
<td class="left"><a href="#sec-5">5</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline6">Is metadata protected?</a></td>
|
||||
<td class="left"><a href="#sec-6">6</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline7">How do I create email processing rules?</a></td>
|
||||
<td class="left"><a href="#sec-7">7</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline8">Why isn't dynamic DNS working?</a></td>
|
||||
<td class="left"><a href="#sec-8">8</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline9">How do I change my encryption settings?</a></td>
|
||||
<td class="left"><a href="#sec-9">9</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline10">How do I get a domain name?</a></td>
|
||||
<td class="left"><a href="#sec-10">10</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline11">How do I get a "real" SSL certificate?</a></td>
|
||||
<td class="left"><a href="#sec-11">11</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline12">How do I renew a StartSSL certificate?</a></td>
|
||||
<td class="left"><a href="#sec-12">12</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline13">Why use self-signed certificates?</a></td>
|
||||
<td class="left"><a href="#sec-13">13</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline14">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
||||
<td class="left"><a href="#sec-14">14</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgheadline15">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
||||
<td class="left"><a href="#sec-15">15</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="left"><a href="#sec-16">16</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgheadline1" class="outline-2">
|
||||
<h2 id="orgheadline1">Why not supply a disk image download?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline1">
|
||||
<div id="outline-container-sec-1" class="outline-2">
|
||||
<h2 id="sec-1"><span class="section-number-2">1</span> Why not supply a disk image download?</h2>
|
||||
<div class="outline-text-2" id="text-1">
|
||||
<p>
|
||||
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 <b>freedombone</b> 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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline2" class="outline-2">
|
||||
<h2 id="orgheadline2">I don't have a static IP address. Can I still install this system?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline2">
|
||||
<div id="outline-container-sec-2" class="outline-2">
|
||||
<h2 id="sec-2"><span class="section-number-2">2</span> I don't have a static IP address. Can I still install this system?</h2>
|
||||
<div class="outline-text-2" id="text-2">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -257,9 +248,9 @@ The lack of a static IP address can be worked around by using a dynamic DNS serv
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline3" class="outline-2">
|
||||
<h2 id="orgheadline3">What is the best hardware to run this system on?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline3">
|
||||
<div id="outline-container-sec-3" class="outline-2">
|
||||
<h2 id="sec-3"><span class="section-number-2">3</span> What is the best hardware to run this system on?</h2>
|
||||
<div class="outline-text-2" id="text-3">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -269,17 +260,45 @@ It was originally designed to run on the Beaglebone Black, but that should be re
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline4" class="outline-2">
|
||||
<h2 id="orgheadline4">Can I add more users to the system?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline4">
|
||||
<div id="outline-container-sec-4" class="outline-2">
|
||||
<h2 id="sec-4"><span class="section-number-2">4</span> Can I add more users to the system?</h2>
|
||||
<div class="outline-text-2" id="text-4">
|
||||
<p>
|
||||
Like any other GNU/Linux system you can add more users. It's easy to add users to Owncloud, XMPP or Hubzilla. 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.
|
||||
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 and the blog (depending on whether the variant which you installed includes those). To add a user login as root then run the command:
|
||||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">freedombone-adduser [username]
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
Something to consider when having more than a single user on the system is the security situation. The original administrator user will have access to all of the data for other users (including their encryption keys), so if you do add extra users they need to have <b>complete trust</b> in the administrator.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Another point is that Freedombone installations are not intended to support many users (maybe ten at most). Large numbers of users may make the system unstable, and the more users you have on one system the more it becomes a single point of failure and also perhaps a honeypot from the standpoint of adversaries. Think of what happened with Lavabit and the moral dilemma which an administrator can be faced with (comply with threats and betray the trust of your users or don't comply and suffer other consequences). Ideally, you never want to put yourself into a situation where you can be forced to betray others.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline5" class="outline-2">
|
||||
<h2 id="orgheadline5">How do I reset the tripwire?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline5">
|
||||
<div id="outline-container-sec-5" class="outline-2">
|
||||
<h2 id="sec-5"><span class="section-number-2">5</span> How do I remove a user from the system?</h2>
|
||||
<div class="outline-text-2" id="text-5">
|
||||
<p>
|
||||
To remove a user login as root then run the command:
|
||||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">freedombone-rmuser [username]
|
||||
</pre>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-sec-6" class="outline-2">
|
||||
<h2 id="sec-6"><span class="section-number-2">6</span> How do I reset the tripwire?</h2>
|
||||
<div class="outline-text-2" id="text-6">
|
||||
<p>
|
||||
You will get a daily email which indicates which files on the system have changed recently. Once per week the system will install any updates and those may also show up on the list, along with any changes due to installed packages or changed settings. Watch out for any files which change unexpectedly, which could indicate an intruder. To reset the tripwire:
|
||||
</p>
|
||||
|
|
@ -297,17 +316,17 @@ You will need to press enter a couple of times. Doing this typically once per we
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline6" class="outline-2">
|
||||
<h2 id="orgheadline6">Is metadata protected?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline6">
|
||||
<div id="outline-container-sec-7" class="outline-2">
|
||||
<h2 id="sec-7"><span class="section-number-2">7</span> Is metadata protected?</h2>
|
||||
<div class="outline-text-2" id="text-7">
|
||||
<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-orgheadline7" class="outline-2">
|
||||
<h2 id="orgheadline7">How do I create email processing rules?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline7">
|
||||
<div id="outline-container-sec-8" class="outline-2">
|
||||
<h2 id="sec-8"><span class="section-number-2">8</span> How do I create email processing rules?</h2>
|
||||
<div class="outline-text-2" id="text-8">
|
||||
<p>
|
||||
You can administer email in the traditional manner by editing folders or procmail rules, but for convenience some commands are available to make that process simpler. See the relevant manpages for more details.
|
||||
</p>
|
||||
|
|
@ -316,39 +335,39 @@ You can administer email in the traditional manner by editing folders or procmai
|
|||
|
||||
|
||||
<colgroup>
|
||||
<col class="org-left" />
|
||||
<col class="left" />
|
||||
|
||||
<col class="org-left" />
|
||||
<col class="left" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td class="org-left">freedombone-addlist</td>
|
||||
<td class="org-left">Adds a mailing list</td>
|
||||
<td class="left">freedombone-addlist</td>
|
||||
<td class="left">Adds a mailing list</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left">freedombone-rmlist</td>
|
||||
<td class="org-left">Removes a mailing list</td>
|
||||
<td class="left">freedombone-rmlist</td>
|
||||
<td class="left">Removes a mailing list</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left">freedombone-addemail</td>
|
||||
<td class="org-left">Transfers emails from an address to a given folder</td>
|
||||
<td class="left">freedombone-addemail</td>
|
||||
<td class="left">Transfers emails from an address to a given folder</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left">freedombone-rmemail</td>
|
||||
<td class="org-left">Removes an email transferal rule</td>
|
||||
<td class="left">freedombone-rmemail</td>
|
||||
<td class="left">Removes an email transferal rule</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left">freedombone-ignore</td>
|
||||
<td class="org-left">Ignores email from an address or with a subject line containing text</td>
|
||||
<td class="left">freedombone-ignore</td>
|
||||
<td class="left">Ignores email from an address or with a subject line containing text</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left">freedombone-unignore</td>
|
||||
<td class="org-left">Removes an ignore rule</td>
|
||||
<td class="left">freedombone-unignore</td>
|
||||
<td class="left">Removes an ignore rule</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -358,9 +377,9 @@ Spamassassin is also available and within Mutt you can use the S (shift+s) key t
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline8" class="outline-2">
|
||||
<h2 id="orgheadline8">Why isn't dynamic DNS working?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline8">
|
||||
<div id="outline-container-sec-9" class="outline-2">
|
||||
<h2 id="sec-9"><span class="section-number-2">9</span> Why isn't dynamic DNS working?</h2>
|
||||
<div class="outline-text-2" id="text-9">
|
||||
<p>
|
||||
If you run the command:
|
||||
</p>
|
||||
|
|
@ -428,9 +447,9 @@ http://httpbin.org/ip
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgheadline9" class="outline-2">
|
||||
<h2 id="orgheadline9">How do I change my encryption settings?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline9">
|
||||
<div id="outline-container-sec-10" class="outline-2">
|
||||
<h2 id="sec-10"><span class="section-number-2">10</span> How do I change my encryption settings?</h2>
|
||||
<div class="outline-text-2" id="text-10">
|
||||
<p>
|
||||
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:
|
||||
</p>
|
||||
|
|
@ -448,9 +467,9 @@ You will then be able to edit the crypto settings for all of the installed appli
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline10" class="outline-2">
|
||||
<h2 id="orgheadline10">How do I get a domain name?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline10">
|
||||
<div id="outline-container-sec-11" class="outline-2">
|
||||
<h2 id="sec-11"><span class="section-number-2">11</span> How do I get a domain name?</h2>
|
||||
<div class="outline-text-2" id="text-11">
|
||||
<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>
|
||||
|
|
@ -518,11 +537,11 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgheadline11" class="outline-2">
|
||||
<h2 id="orgheadline11">How do I get a "real" SSL certificate?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline11">
|
||||
<div id="outline-container-sec-12" class="outline-2">
|
||||
<h2 id="sec-12"><span class="section-number-2">12</span> How do I get a "real" SSL certificate?</h2>
|
||||
<div class="outline-text-2" id="text-12">
|
||||
<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 <a href="#orgheadline10">Using your own domain</a> 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).
|
||||
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 <a href="#sec-11">Using your own domain</a> 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>
|
||||
|
||||
<p>
|
||||
|
|
@ -539,10 +558,10 @@ Now we can generate the certificate request as follows.
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash"><span class="org-builtin">export</span> <span class="org-variable-name">HOSTNAME</span>=mydomainname.com
|
||||
openssl genrsa -out /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.key 2048
|
||||
chown root:ssl-cert /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.key
|
||||
chmod 440 /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.key
|
||||
<pre class="src src-bash">export HOSTNAME=mydomainname.com
|
||||
openssl genrsa -out /etc/ssl/private/$HOSTNAME.key 2048
|
||||
chown root:ssl-cert /etc/ssl/private/$HOSTNAME.key
|
||||
chmod 440 /etc/ssl/private/$HOSTNAME.key
|
||||
mkdir /etc/ssl/requests
|
||||
</pre>
|
||||
</div>
|
||||
|
|
@ -553,7 +572,7 @@ Now make a certificate request as follows. You should copy and paste the whole
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">openssl req -new -sha256 -key /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.key -out /etc/ssl/requests/$<span class="org-variable-name">HOSTNAME</span>.csr
|
||||
<pre class="src src-bash">openssl req -new -sha256 -key /etc/ssl/private/$HOSTNAME.key -out /etc/ssl/requests/$HOSTNAME.csr
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -571,7 +590,7 @@ View the request with:
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">cat /etc/ssl/requests/$<span class="org-variable-name">HOSTNAME</span>.csr
|
||||
<pre class="src src-bash">cat /etc/ssl/requests/$HOSTNAME.csr
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -585,7 +604,7 @@ Log into your StartSSL account and select <b>Retrieve Certificate</b> from the <
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">editor /etc/ssl/certs/$<span class="org-variable-name">HOSTNAME</span>.crt
|
||||
<pre class="src src-bash">editor /etc/ssl/certs/$HOSTNAME.crt
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -597,15 +616,15 @@ Paste the public key, then save and exit. Then on the Freedombone.
|
|||
|
||||
<pre class="src src-bash">mkdir /etc/ssl/roots
|
||||
mkdir /etc/ssl/chains
|
||||
wget <span class="org-string">"http://www.startssl.com/certs/ca.pem"</span> --output-document=<span class="org-string">"/etc/ssl/roots/startssl-root.ca"</span>
|
||||
wget <span class="org-string">"http://www.startssl.com/certs/sub.class1.server.ca.pem"</span> --output-document=<span class="org-string">"/etc/ssl/chains/startssl-sub.class1.server.ca.pem"</span>
|
||||
wget <span class="org-string">"http://www.startssl.com/certs/sub.class2.server.ca.pem"</span> --output-document=<span class="org-string">"/etc/ssl/chains/startssl-sub.class2.server.ca.pem"</span>
|
||||
wget <span class="org-string">"http://www.startssl.com/certs/sub.class3.server.ca.pem"</span> --output-document=<span class="org-string">"/etc/ssl/chains/startssl-sub.class3.server.ca.pem"</span>
|
||||
ln -s <span class="org-string">"/etc/ssl/roots/startssl-root.ca"</span> <span class="org-string">"/etc/ssl/roots/$HOSTNAME-root.ca"</span>
|
||||
ln -s <span class="org-string">"/etc/ssl/chains/startssl-sub.class1.server.ca.pem"</span> <span class="org-string">"/etc/ssl/chains/$HOSTNAME.ca"</span>
|
||||
cp <span class="org-string">"/etc/ssl/certs/$HOSTNAME.crt"</span> <span class="org-string">"/etc/ssl/certs/$HOSTNAME.crt+chain+root"</span>
|
||||
<span class="org-builtin">test</span> -e <span class="org-string">"/etc/ssl/chains/$HOSTNAME.ca"</span> && cat <span class="org-string">"/etc/ssl/chains/$HOSTNAME.ca"</span> >> <span class="org-string">"/etc/ssl/certs/$HOSTNAME.crt+chain+root"</span>
|
||||
<span class="org-builtin">test</span> -e <span class="org-string">"/etc/ssl/roots/$HOSTNAME-root.ca"</span> && cat <span class="org-string">"/etc/ssl/roots/$HOSTNAME-root.ca"</span> >> <span class="org-string">"/etc/ssl/certs/$HOSTNAME.crt+chain+root"</span>
|
||||
wget "http://www.startssl.com/certs/ca.pem" --output-document="/etc/ssl/roots/startssl-root.ca"
|
||||
wget "http://www.startssl.com/certs/sub.class1.server.ca.pem" --output-document="/etc/ssl/chains/startssl-sub.class1.server.ca.pem"
|
||||
wget "http://www.startssl.com/certs/sub.class2.server.ca.pem" --output-document="/etc/ssl/chains/startssl-sub.class2.server.ca.pem"
|
||||
wget "http://www.startssl.com/certs/sub.class3.server.ca.pem" --output-document="/etc/ssl/chains/startssl-sub.class3.server.ca.pem"
|
||||
ln -s "/etc/ssl/roots/startssl-root.ca" "/etc/ssl/roots/$HOSTNAME-root.ca"
|
||||
ln -s "/etc/ssl/chains/startssl-sub.class1.server.ca.pem" "/etc/ssl/chains/$HOSTNAME.ca"
|
||||
cp "/etc/ssl/certs/$HOSTNAME.crt" "/etc/ssl/certs/$HOSTNAME.crt+chain+root"
|
||||
test -e "/etc/ssl/chains/$HOSTNAME.ca" && cat "/etc/ssl/chains/$HOSTNAME.ca" >> "/etc/ssl/certs/$HOSTNAME.crt+chain+root"
|
||||
test -e "/etc/ssl/roots/$HOSTNAME-root.ca" && cat "/etc/ssl/roots/$HOSTNAME-root.ca" >> "/etc/ssl/certs/$HOSTNAME.crt+chain+root"
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -618,8 +637,8 @@ To avoid any possibility of the certificates being accidentally overwritten by s
|
|||
<pre class="src src-bash">mkdir /etc/ssl/backups
|
||||
mkdir /etc/ssl/backups/certs
|
||||
mkdir /etc/ssl/backups/private
|
||||
cp /etc/ssl/certs/$<span class="org-variable-name">HOSTNAME</span>* /etc/ssl/backups/certs/
|
||||
cp /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>* /etc/ssl/backups/private/
|
||||
cp /etc/ssl/certs/$HOSTNAME* /etc/ssl/backups/certs/
|
||||
cp /etc/ssl/private/$HOSTNAME* /etc/ssl/backups/private/
|
||||
chmod -R 400 /etc/ssl/backups/certs/*
|
||||
chmod -R 400 /etc/ssl/backups/private/*
|
||||
</pre>
|
||||
|
|
@ -631,9 +650,9 @@ Remove the certificate password, so if the server is rebooted then it won't wait
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">openssl rsa -in /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.key -out /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.new.key
|
||||
cp /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.new.key /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.key
|
||||
shred -zu /etc/ssl/private/$<span class="org-variable-name">HOSTNAME</span>.new.key
|
||||
<pre class="src src-bash">openssl rsa -in /etc/ssl/private/$HOSTNAME.key -out /etc/ssl/private/$HOSTNAME.new.key
|
||||
cp /etc/ssl/private/$HOSTNAME.new.key /etc/ssl/private/$HOSTNAME.key
|
||||
shred -zu /etc/ssl/private/$HOSTNAME.new.key
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -643,7 +662,7 @@ Create a bundled certificate which joins the certificate and chain file together
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">cat /etc/ssl/certs/$<span class="org-variable-name">HOSTNAME</span>.crt /etc/ssl/chains/startssl-sub.class1.server.ca.pem > /etc/ssl/certs/$<span class="org-variable-name">HOSTNAME</span>.bundle.crt
|
||||
<pre class="src src-bash">cat /etc/ssl/certs/$HOSTNAME.crt /etc/ssl/chains/startssl-sub.class1.server.ca.pem > /etc/ssl/certs/$HOSTNAME.bundle.crt
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -654,7 +673,7 @@ And also add it to the overall bundle of certificates for the Freedombone. This
|
|||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">mkdir /etc/ssl/mycerts
|
||||
cp /etc/ssl/certs/$<span class="org-variable-name">HOSTNAME</span>.bundle.crt /etc/ssl/mycerts
|
||||
cp /etc/ssl/certs/$HOSTNAME.bundle.crt /etc/ssl/mycerts
|
||||
cat /etc/ssl/mycerts/*.crt > /etc/ssl/freedombone-bundle.crt
|
||||
tar -czvf /etc/ssl/freedombone-certs.tar.gz /etc/ssl/mycerts/*.crt
|
||||
</pre>
|
||||
|
|
@ -666,7 +685,7 @@ Edit your configuration file.
|
|||
|
||||
<div class="org-src-container">
|
||||
|
||||
<pre class="src src-bash">editor /etc/nginx/sites-available/$<span class="org-variable-name">HOSTNAME</span>
|
||||
<pre class="src src-bash">editor /etc/nginx/sites-available/$HOSTNAME
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -691,14 +710,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://github.com/redmatrix/hubzilla">Hubzilla</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://github.com/redmatrix/hubzilla">Hubzilla</a>.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgheadline12" class="outline-2">
|
||||
<h2 id="orgheadline12">How do I renew a StartSSL certificate?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline12">
|
||||
<div id="outline-container-sec-13" class="outline-2">
|
||||
<h2 id="sec-13"><span class="section-number-2">13</span> How do I renew a StartSSL certificate?</h2>
|
||||
<div class="outline-text-2" id="text-13">
|
||||
<p>
|
||||
The StartSSL certificates last for a year. You can check the expiry date of your current certificate/s by going to your site and if you're using Firefox then click on the <b>lock icon</b>, select "<b>more information</b>" then "<b>view certificate</b>".
|
||||
</p>
|
||||
|
|
@ -712,7 +731,7 @@ Make sure that you have the StartSSL certificate which was created when you init
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Now go to <a href="https://startssl.com/">startssl.com</a> and click on the keys icon on the right hand side to log in. Select the <b>Control panel</b> then <b>Validations Wizard</b> and choose <b>Email address validation</b>. Enter your email address, then wait for the validation email to show up in your inbox. It will contain a code when you can then enter.
|
||||
Now go to <a href="https://startssl.com">startssl.com</a> and click on the keys icon on the right hand side to log in. Select the <b>Control panel</b> then <b>Validations Wizard</b> and choose <b>Email address validation</b>. Enter your email address, then wait for the validation email to show up in your inbox. It will contain a code when you can then enter.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -768,9 +787,9 @@ The new certificate will then be installed.
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline13" class="outline-2">
|
||||
<h2 id="orgheadline13">Why use self-signed certificates?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline13">
|
||||
<div id="outline-container-sec-14" class="outline-2">
|
||||
<h2 id="sec-14"><span class="section-number-2">14</span> Why use self-signed certificates?</h2>
|
||||
<div class="outline-text-2" id="text-14">
|
||||
<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>
|
||||
|
|
@ -784,17 +803,17 @@ For now a self-signed certificate will probably in most cases protect your commu
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgheadline14" class="outline-2">
|
||||
<h2 id="orgheadline14">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline14">
|
||||
<div id="outline-container-sec-15" class="outline-2">
|
||||
<h2 id="sec-15"><span class="section-number-2">15</span> Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
||||
<div class="outline-text-2" id="text-15">
|
||||
<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.
|
||||
<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-orgheadline15" class="outline-2">
|
||||
<h2 id="orgheadline15">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
||||
<div class="outline-text-2" id="text-orgheadline15">
|
||||
<div id="outline-container-sec-16" class="outline-2">
|
||||
<h2 id="sec-16"><span class="section-number-2">16</span> Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
||||
<div class="outline-text-2" id="text-16">
|
||||
<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>
|
||||
|
|
@ -806,40 +825,10 @@ So the situation with email presently is pretty bad, and there's a clear selecti
|
|||
</div>
|
||||
</div>
|
||||
<div id="postamble" class="status">
|
||||
|
||||
<style type="text/css">
|
||||
.back-to-top {
|
||||
position: fixed;
|
||||
bottom: 2em;
|
||||
right: 0px;
|
||||
text-decoration: none;
|
||||
color: #000000;
|
||||
background-color: rgba(235, 235, 235, 0.80);
|
||||
font-size: 12px;
|
||||
padding: 1em;
|
||||
display: none;
|
||||
}
|
||||
|
||||
.back-to-top:hover {
|
||||
background-color: rgba(135, 135, 135, 0.50);
|
||||
}
|
||||
</style>
|
||||
|
||||
<div class="back-to-top">
|
||||
<a href="#top">Back to top</a> | <a href="mailto:bob@robotics.uk.to">E-mail me</a>
|
||||
</div>
|
||||
|
||||
<script type="text/javascript">
|
||||
var offset = 220;
|
||||
var duration = 500;
|
||||
jQuery(window).scroll(function() {
|
||||
if (jQuery(this).scrollTop() > offset) {
|
||||
jQuery('.back-to-top').fadeIn(duration);
|
||||
} else {
|
||||
jQuery('.back-to-top').fadeOut(duration);
|
||||
}
|
||||
});
|
||||
</script>
|
||||
<p class="author">Author: Bob Mottram</p>
|
||||
<p class="date">Created: 2015-10-27 Tue 11:37</p>
|
||||
<p class="creator"><a href="http://www.gnu.org/software/emacs/">Emacs</a> 24.4.1 (<a href="http://orgmode.org">Org</a> mode 8.2.10)</p>
|
||||
<p class="validation"><a href="http://validator.w3.org/check?uri=referer">Validate</a></p>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
|
|
|||
Loading…
Reference in New Issue