free
/
freedombone
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Move the image

This commit is contained in:
Bob Mottram 2017-07-30 18:19:21 +01:00
parent 241ccb9803
commit de37fbc633
2 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/EN/app_keyserver.org
View File

@ -16,14 +16,14 @@
</center>
#+END_EXPORT
#+BEGIN_CENTER
[[file:images/keyserver.jpg]]
#+END_CENTER
The /web of trust/ is a nice idea, but how trustable is it? If you take a look at how many OpenPGP key servers are out there then there are a two or three main ones and not much else. Can you trust those servers? Who is maintaining them and how often? Is any censorship going on? How hard would it be for adversaries to get implants onto them? In terms of technology this infrastructure is quite old and it could have been neglected for a long time. Once vigilant maintainers might have turned lazy and gotten lax with server security, or been recruited over to the dark side.
For these kinds of reasons you might prefer to run your own web of trust infrastructure. In simple terms it's a database of GPG public keys which provides a way for users to /find out how to communicate with others securely via email/. You can meet in person and exchange public keys via sneakernet on USB drives, but most users of GPG don't do that. Instead they just download the public key for a given email address from one of the key servers.
#+BEGIN_CENTER
[[file:images/keyserver.jpg]]
#+END_CENTER
* Installation
ssh into the system with:

42
website/EN/app_keyserver.html
View File

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2017-07-30 Sun 18:12 -->
<!-- 2017-07-30 Sun 18:18 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title>
@ -248,14 +248,6 @@ for the JavaScript code in this tag.
<h1>OpenPGP Key Server</h1>
</center>
<div class="org-center">
<div class="figure">
<p><img src="images/keyserver.jpg" alt="keyserver.jpg" />
</p>
</div>
</div>
<p>
The <i>web of trust</i> is a nice idea, but how trustable is it? If you take a look at how many OpenPGP key servers are out there then there are a two or three main ones and not much else. Can you trust those servers? Who is maintaining them and how often? Is any censorship going on? How hard would it be for adversaries to get implants onto them? In terms of technology this infrastructure is quite old and it could have been neglected for a long time. Once vigilant maintainers might have turned lazy and gotten lax with server security, or been recruited over to the dark side.
</p>
@ -264,9 +256,17 @@ The <i>web of trust</i> is a nice idea, but how trustable is it? If you take a l
For these kinds of reasons you might prefer to run your own web of trust infrastructure. In simple terms it's a database of GPG public keys which provides a way for users to <i>find out how to communicate with others securely via email</i>. You can meet in person and exchange public keys via sneakernet on USB drives, but most users of GPG don't do that. Instead they just download the public key for a given email address from one of the key servers.
</p>
<div id="outline-container-org9a238e8" class="outline-2">
<h2 id="org9a238e8">Installation</h2>
<div class="outline-text-2" id="text-org9a238e8">
<div class="org-center">
<div class="figure">
<p><img src="images/keyserver.jpg" alt="keyserver.jpg" />
</p>
</div>
</div>
<div id="outline-container-orgfcf6c32" class="outline-2">
<h2 id="orgfcf6c32">Installation</h2>
<div class="outline-text-2" id="text-orgfcf6c32">
<p>
ssh into the system with:
</p>
@ -286,9 +286,9 @@ After the install has completed go to <b>Security settings</b> and select <b>Cre
</div>
</div>
<div id="outline-container-org671d1b4" class="outline-2">
<h2 id="org671d1b4">How to use it</h2>
<div class="outline-text-2" id="text-org671d1b4">
<div id="outline-container-org8e2baf7" class="outline-2">
<h2 id="org8e2baf7">How to use it</h2>
<div class="outline-text-2" id="text-org8e2baf7">
<p>
Interaction with the web user interface is pretty minimal and obvious, but most likely you will also want to be able to use your keyserver from the commandline. To do that use the <b>&#x2013;keyserver</b> option. For example to search for a key on your server:
</p>
@ -318,9 +318,9 @@ Or to get a key:
</div>
</div>
</div>
<div id="outline-container-org8a015fc" class="outline-2">
<h2 id="org8a015fc">Sync with other keyservers</h2>
<div class="outline-text-2" id="text-org8a015fc">
<div id="outline-container-orgf7e93ae" class="outline-2">
<h2 id="orgf7e93ae">Sync with other keyservers</h2>
<div class="outline-text-2" id="text-orgf7e93ae">
<p>
Key servers avoid censorship or errors by gossiping between each other and cross referencing the data. You can define which other servers your key server will gossip with by going to the <b>Administrator control panel</b>, selecting <b>App Settings</b> then <b>keyserver</b> then <b>Sync with other keyserver</b>.
</p>
@ -330,9 +330,9 @@ It's a good idea not to try to sync with the popular OpenPGP key servers, becaus
</p>
</div>
</div>
<div id="outline-container-orge9e564a" class="outline-2">
<h2 id="orge9e564a">Possible problems</h2>
<div class="outline-text-2" id="text-orge9e564a">
<div id="outline-container-org7be3c82" class="outline-2">
<h2 id="org7be3c82">Possible problems</h2>
<div class="outline-text-2" id="text-org7be3c82">
<p>
OpenPGP key servers are not very well defended from flooding attacks. This means that an adversary could just upload a billion keys to destabilize the server and fill it with nonsense to make it unusable. Since key servers are <i>fully open to the public</i> there isn't anything to prevent that from happening.
</p>