kotovalexarian-likes-gitlab
/
hagrid-keyserver--hagrid
mirror of https://gitlab.com/hagrid-keyserver/hagrid.git
1
0
Fork 0
Code Releases Activity

about: avoid clunky "up- and downloaded" construction 

This also happens to fix a bit of the text that is actually incorrect:
the policies about uploads and downloads are different, and can't be
described together.
This commit is contained in:
Daniel Kahn Gillmor 2019-06-06 10:06:30 -04:00 committed by Vincent Breitmoser
parent e3f5de6fc9
commit a67a10796e
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
dist/templates/about/about.html.hbs vendored
View File

@ -33,13 +33,16 @@
<p>
Traditionally, these pieces of information have always been distributed
together. On <span class="brand">keys.openpgp.org</span>, they are
treated differently:
treated differently. While anyone can upload all parts of any OpenPGP key
to <span class="brand">keys.openpgp.org</span>, our keyserver
will only retain and publish certain parts under certain
conditions:
</p>
<p>
The technical data of keys can be freely up- and downloaded on
<span class="brand">keys.openpgp.org</span>. It consists of technical
information only, which can't be used to identify its owner.
Any valid technical data will be stored and freely redistributed.
Anyone can download these parts at any time as they contain only
technical information which can't be used to directly identify a person.
Good OpenPGP software can use <span class="brand">keys.openpgp.org</span>
to keep this information up to date for any key that it knows about.
This helps OpenPGP users maintain secure and reliable communication.