Author: buildbot
Date: Thu Aug 29 07:28:24 2013
New Revision: 876565
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/downloads.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 29 07:28:24 2013
@@ -1 +1 @@
-1513298
+1518519
Modified: websites/staging/openoffice/trunk/content/downloads.html
==============================================================================
--- websites/staging/openoffice/trunk/content/downloads.html (original)
+++ websites/staging/openoffice/trunk/content/downloads.html Thu Aug 29
07:28:24 2013
@@ -161,11 +161,11 @@ via the central <a href="http://www.open
</li>
</ul>
<p><strong>Note</strong>:
-All downloads can be verified using the Apache OpenOffice code signing <a
href="http://www.apache.org/dist/openoffice/KEYS";>KEYS</a>.
+All downloads can be verified using the Apache OpenOffice code signing <a
href="https://people.apache.org/keys/group/openoffice.asc";>KEYS</a>.
When downloading from a mirror please check the <a
href="http://www.apache.org/dev/release-signing#md5";>md5sum</a> and verify the
<a href="http://www.apache.org/dev/release-signing#openpgp";>OpenPGP</a>
compatible signature from the main
<a href="http://www.apache.org";>Apache site</a>. Links are provided above
(next to the release download link).
-This <a href="http://www.apache.org/dist/openoffice/KEYS";>KEYS</a> file
contains the public keys used for signing
+This <a href="https://people.apache.org/keys/group/openoffice.asc";>KEYS</a>
file contains the public keys used for signing
release. It is recommended that (when possible) a <a
href="http://www.apache.org/dev/release-signing#web-of-trust";>web of trust</a>
is
used to confirm the identity of these keys. For more information, please see
the
<a href="http://www.apache.org/dev/release.html";>Apache Release FAQ</a>.</p>
