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:
parent
e3f5de6fc9
commit
a67a10796e
|
@ -33,13 +33,16 @@
|
||||||
<p>
|
<p>
|
||||||
Traditionally, these pieces of information have always been distributed
|
Traditionally, these pieces of information have always been distributed
|
||||||
together. On <span class="brand">keys.openpgp.org</span>, they are
|
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>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
The technical data of keys can be freely up- and downloaded on
|
Any valid technical data will be stored and freely redistributed.
|
||||||
<span class="brand">keys.openpgp.org</span>. It consists of technical
|
Anyone can download these parts at any time as they contain only
|
||||||
information only, which can't be used to identify its owner.
|
technical information which can't be used to directly identify a person.
|
||||||
Good OpenPGP software can use <span class="brand">keys.openpgp.org</span>
|
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.
|
to keep this information up to date for any key that it knows about.
|
||||||
This helps OpenPGP users maintain secure and reliable communication.
|
This helps OpenPGP users maintain secure and reliable communication.
|
||||||
|
|
Loading…
Reference in New Issue