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 a19f569 Automatic Site Publish by Buildbot
a19f569 is described below
commit a19f5692acc8282223cd2230e905611a6c872dff
Author: buildbot <[email protected]>
AuthorDate: Fri Dec 10 18:37:58 2021 +0000
Automatic Site Publish by Buildbot
---
output/feeds/all.atom.xml | 4 ++--
output/feeds/solr/security.atom.xml | 4 ++--
output/news.html | 4 ++--
output/security.html | 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 759a4a1..0287398 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -29,9 +29,9 @@ Any of the following are enough to prevent this vulnerability
for Solr servers:&
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when
available), which will include an updated version of the log4j2
dependency.</li>
<li>Manually update the version of log4j2 on your runtime classpath and
restart your Solr application.</li>
-<li>Edit your <code>solr-exporter</code> script to include
+<li>Edit your <code>solr-exporter</code> script to include:
<code>JAVA_OPTS="$JAVA_OPTS
-Dlog4j2.formatMsgNoLookups=true"</code></li>
-<li>Follow any of the other mitgations listed at
https://logging.apache.org/log4j/2.x/security.html</li>
+<li>Follow any of the other mitgations listed at <a
href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></li>
</ul>
<p><strong>References:</strong>
<a
href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p></content><category
term="solr/security"></category></entry><entry><title>Apache Solr Operator™
v0.5.0 available</title><link
href="/apache-solr-operatortm-v050-available.html"
rel="alternate"></link><published>2021-11-16T00:00:00+00:00</published><updated>2021-11-16T00:00:00+00:00</updated><author><name>Solr
Developers</name></author><id>tag:None,2021- [...]
diff --git a/output/feeds/solr/security.atom.xml
b/output/feeds/solr/security.atom.xml
index 5460f85..f09f28a 100644
--- a/output/feeds/solr/security.atom.xml
+++ b/output/feeds/solr/security.atom.xml
@@ -29,9 +29,9 @@ Any of the following are enough to prevent this vulnerability
for Solr servers:&
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when
available), which will include an updated version of the log4j2
dependency.</li>
<li>Manually update the version of log4j2 on your runtime classpath and
restart your Solr application.</li>
-<li>Edit your <code>solr-exporter</code> script to include
+<li>Edit your <code>solr-exporter</code> script to include:
<code>JAVA_OPTS="$JAVA_OPTS
-Dlog4j2.formatMsgNoLookups=true"</code></li>
-<li>Follow any of the other mitgations listed at
https://logging.apache.org/log4j/2.x/security.html</li>
+<li>Follow any of the other mitgations listed at <a
href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></li>
</ul>
<p><strong>References:</strong>
<a
href="https://logging.apache.org/log4j/2.x/security.html">https://logging.apache.org/log4j/2.x/security.html</a></p></content><category
term="solr/security"></category></entry><entry><title>CVE-2021-27905: SSRF
vulnerability with the Replication handler</title><link
href="/cve-2021-27905-ssrf-vulnerability-with-the-replication-handler.html"
rel="alternate"></link><published>2021-04-12T00:00:00+00:00</published><updated>2021-04-12T00:00:00+00:00</updated><author><name
[...]
diff --git a/output/news.html b/output/news.html
index 46ec753..f8f1be6 100644
--- a/output/news.html
+++ b/output/news.html
@@ -159,9 +159,9 @@ Any of the following are enough to prevent this
vulnerability for Solr servers:<
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which
will include an updated version of the log4j2 dependency.</li>
<li>Manually update the version of log4j2 on your runtime classpath and
restart your Solr application.</li>
-<li>Edit your <code>solr-exporter</code> script to include
+<li>Edit your <code>solr-exporter</code> script to include:
<code>JAVA_OPTS="$JAVA_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li>
-<li>Follow any of the other mitgations listed at
https://logging.apache.org/log4j/2.x/security.html</li>
+<li>Follow any of the other mitgations listed at <a
href="https://logging.apache.org/log4j/2.x/security.html";>https://logging.apache.org/log4j/2.x/security.html</a></li>
</ul>
<p><strong>References:</strong>
<a
href="https://logging.apache.org/log4j/2.x/security.html";>https://logging.apache.org/log4j/2.x/security.html</a></p>
diff --git a/output/security.html b/output/security.html
index b60027b..8a9c0d6 100644
--- a/output/security.html
+++ b/output/security.html
@@ -243,9 +243,9 @@ Any of the following are enough to prevent this
vulnerability for Solr servers:<
<ul>
<li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which
will include an updated version of the log4j2 dependency.</li>
<li>Manually update the version of log4j2 on your runtime classpath and
restart your Solr application.</li>
-<li>Edit your <code>solr-exporter</code> script to include
+<li>Edit your <code>solr-exporter</code> script to include:
<code>JAVA_OPTS="$JAVA_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li>
-<li>Follow any of the other mitgations listed at
https://logging.apache.org/log4j/2.x/security.html</li>
+<li>Follow any of the other mitgations listed at <a
href="https://logging.apache.org/log4j/2.x/security.html";>https://logging.apache.org/log4j/2.x/security.html</a></li>
</ul>
<p><strong>References:</strong>
<a
href="https://logging.apache.org/log4j/2.x/security.html";>https://logging.apache.org/log4j/2.x/security.html</a></p>
