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/solr-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 9bfb7a5 Automatic Site Publish by Buildbot
9bfb7a5 is described below
commit 9bfb7a59d01fdc572d34c806858210e22b76a8a6
Author: buildbot <[email protected]>
AuthorDate: Wed Dec 15 13:20:44 2021 +0000
Automatic Site Publish by Buildbot
---
output/feeds/all.atom.xml | 2 +-
output/feeds/solr/security.atom.xml | 2 +-
output/news.html | 2 +-
output/security.html | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 04e2ed3..458a7a0 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -16,7 +16,7 @@ Apache Solr releases prior to 8.11.1 were using a bundled
version of the Apache
Any of the following are enough to prevent this vulnerability for Solr
servers:</p>
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when
available), which will include an updated version of the Log4J
dependency.</li>
-<li>If you are using Solr's official docker image, no matter the
version, it has already been mitigated. You may need to re-pull the
image.</li>
+<li>If you are using Solr's official docker image, it has already been
mitigated in all versions listed as supported on Docker Hub: <a
href="https://hub.docker.com/_/solr">https://hub.docker.com/_/solr</a>.
You may need to re-pull the image.</li>
<li>Manually update the version of Log4J on your runtime classpath and
restart your Solr application.</li>
<li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to
include:
<code>SOLR_OPTS="$SOLR_OPTS
-Dlog4j2.formatMsgNoLookups=true"</code></li>
diff --git a/output/feeds/solr/security.atom.xml
b/output/feeds/solr/security.atom.xml
index 602e586..2fcccd5 100644
--- a/output/feeds/solr/security.atom.xml
+++ b/output/feeds/solr/security.atom.xml
@@ -16,7 +16,7 @@ Apache Solr releases prior to 8.11.1 were using a bundled
version of the Apache
Any of the following are enough to prevent this vulnerability for Solr
servers:</p>
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when
available), which will include an updated version of the Log4J
dependency.</li>
-<li>If you are using Solr's official docker image, no matter the
version, it has already been mitigated. You may need to re-pull the
image.</li>
+<li>If you are using Solr's official docker image, it has already been
mitigated in all versions listed as supported on Docker Hub: <a
href="https://hub.docker.com/_/solr">https://hub.docker.com/_/solr</a>.
You may need to re-pull the image.</li>
<li>Manually update the version of Log4J on your runtime classpath and
restart your Solr application.</li>
<li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to
include:
<code>SOLR_OPTS="$SOLR_OPTS
-Dlog4j2.formatMsgNoLookups=true"</code></li>
diff --git a/output/news.html b/output/news.html
index 40a8d84..b24b424 100644
--- a/output/news.html
+++ b/output/news.html
@@ -147,7 +147,7 @@ Apache Solr releases prior to 8.11.1 were using a bundled
version of the Apache
Any of the following are enough to prevent this vulnerability for Solr
servers:</p>
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which
will include an updated version of the Log4J dependency.</li>
-<li>If you are using Solr's official docker image, no matter the version, it
has already been mitigated. You may need to re-pull the image.</li>
+<li>If you are using Solr's official docker image, it has already been
mitigated in all versions listed as supported on Docker Hub: <a
href="https://hub.docker.com/_/solr";>https://hub.docker.com/_/solr</a>. You
may need to re-pull the image.</li>
<li>Manually update the version of Log4J on your runtime classpath and restart
your Solr application.</li>
<li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to include:
<code>SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li>
diff --git a/output/security.html b/output/security.html
index dfeecc8..2ec4f82 100644
--- a/output/security.html
+++ b/output/security.html
@@ -231,7 +231,7 @@ Apache Solr releases prior to 8.11.1 were using a bundled
version of the Apache
Any of the following are enough to prevent this vulnerability for Solr
servers:</p>
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which
will include an updated version of the Log4J dependency.</li>
-<li>If you are using Solr's official docker image, no matter the version, it
has already been mitigated. You may need to re-pull the image.</li>
+<li>If you are using Solr's official docker image, it has already been
mitigated in all versions listed as supported on Docker Hub: <a
href="https://hub.docker.com/_/solr";>https://hub.docker.com/_/solr</a>. You
may need to re-pull the image.</li>
<li>Manually update the version of Log4J on your runtime classpath and restart
your Solr application.</li>
<li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to include:
<code>SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li>
