[httpd-site] branch asf-site updated: Automatic Site Publish by Buildbot

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/httpd-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 13ed476  Automatic Site Publish by Buildbot
13ed476 is described below

commit 13ed476477719c598aaabb0e3eeea315289c05cb
Author: buildbot <us...@infra.apache.org>
AuthorDate: Fri Dec 17 15:29:35 2021 +0000

    Automatic Site Publish by Buildbot
---
 output/dev/verification.html | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/output/dev/verification.html b/output/dev/verification.html
index c3ed1e8..e0f5aaf 100644
--- a/output/dev/verification.html
+++ b/output/dev/verification.html
@@ -126,10 +126,9 @@ gpg:               imported: 2  (RSA: 2)
 as 'Jim Jagielski &lt;<a href="mailto:jim@apache.org">jim@apache.org</a>&gt;' However, you have no way of
 verifying whether these keys were created by the person known as Jim
 Jagielski whose email address is claimed.  In fact, one of them is
-an imposter: see <a href="https://evil32.org/">https://evil32.org/</a> for the story
-(and this could change again at any time).  This doesn't mean that PGP
-is broken, just that you need to look at the full 40-character key
-fingerprint rather than the vulnerable 8-character ID.</p>
+an imposter.  This doesn't mean that PGP is broken, just that you need to
+look at the full 40-character key fingerprint rather than the vulnerable
+8-character ID.</p>
 <p>Anyway, let's try to verify the release signature again:</p>
 <pre><code>% gpg --verify httpd-2.4.18.tar.gz.asc httpd-2.4.18.tar.gz
 gpg: Signature made Tue Dec  8 21:32:07 2015 CET using RSA key ID 791485A8