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 fc951d8  Automatic Site Publish by Buildbot
fc951d8 is described below

commit fc951d8f615218e4fe91e7e620ff7c758cf8ce5b
Author: buildbot <[email protected]>
AuthorDate: Fri Dec 10 17:37:37 2021 +0000

    Automatic Site Publish by Buildbot
---
 output/feeds/all.atom.xml           | 6 ++++--
 output/feeds/solr/security.atom.xml | 6 ++++--
 output/news.html                    | 6 ++++--
 output/security.html                | 6 ++++--
 4 files changed, 16 insertions(+), 8 deletions(-)

diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 7f3511a..759c585 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -18,8 +18,10 @@ Any of the following are enough to prevent this 
vulnerability:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;Upgrade to &lt;code&gt;Solr 8.11.1&lt;/code&gt; or greater (when 
available), which will include an updated version of the log4j2 
dependancy.&lt;/li&gt;
 &lt;li&gt;Manually update the version of log4j2 on your runtime classpath and 
restart your Solr application.&lt;/li&gt;
-&lt;li&gt;(Linux/MacOS) Edit your &lt;code&gt;solr.in.sh&lt;/code&gt; file to 
include &lt;code&gt;SOLR_OPTS="$SOLR_OPTS 
-Dlog4j2.formatMsgNoLookups=true"&lt;/code&gt;&lt;/li&gt;
-&lt;li&gt;(Windows) Edit your &lt;code&gt;solr.in.cmd&lt;/code&gt; file to 
include &lt;code&gt;set SOLR_OPTS=%SOLR_OPTS% 
-Dlog4j2.formatMsgNoLookups=true&lt;/code&gt;&lt;/li&gt;
+&lt;li&gt;(Linux/MacOS) Edit your &lt;code&gt;solr.in.sh&lt;/code&gt; file to 
include:
+  &lt;code&gt;SOLR_OPTS="$SOLR_OPTS 
-Dlog4j2.formatMsgNoLookups=true"&lt;/code&gt;&lt;/li&gt;
+&lt;li&gt;(Windows) Edit your &lt;code&gt;solr.in.cmd&lt;/code&gt; file to 
include:
+  &lt;code&gt;set SOLR_OPTS=%SOLR_OPTS% 
-Dlog4j2.formatMsgNoLookups=true&lt;/code&gt;&lt;/li&gt;
 &lt;li&gt;Follow any of the other mitgations listed at 
https://logging.apache.org/log4j/2.x/security.html&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;&lt;strong&gt;References:&lt;/strong&gt;
diff --git a/output/feeds/solr/security.atom.xml 
b/output/feeds/solr/security.atom.xml
index 69736ec..b8cee3a 100644
--- a/output/feeds/solr/security.atom.xml
+++ b/output/feeds/solr/security.atom.xml
@@ -18,8 +18,10 @@ Any of the following are enough to prevent this 
vulnerability:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;Upgrade to &lt;code&gt;Solr 8.11.1&lt;/code&gt; or greater (when 
available), which will include an updated version of the log4j2 
dependancy.&lt;/li&gt;
 &lt;li&gt;Manually update the version of log4j2 on your runtime classpath and 
restart your Solr application.&lt;/li&gt;
-&lt;li&gt;(Linux/MacOS) Edit your &lt;code&gt;solr.in.sh&lt;/code&gt; file to 
include &lt;code&gt;SOLR_OPTS="$SOLR_OPTS 
-Dlog4j2.formatMsgNoLookups=true"&lt;/code&gt;&lt;/li&gt;
-&lt;li&gt;(Windows) Edit your &lt;code&gt;solr.in.cmd&lt;/code&gt; file to 
include &lt;code&gt;set SOLR_OPTS=%SOLR_OPTS% 
-Dlog4j2.formatMsgNoLookups=true&lt;/code&gt;&lt;/li&gt;
+&lt;li&gt;(Linux/MacOS) Edit your &lt;code&gt;solr.in.sh&lt;/code&gt; file to 
include:
+  &lt;code&gt;SOLR_OPTS="$SOLR_OPTS 
-Dlog4j2.formatMsgNoLookups=true"&lt;/code&gt;&lt;/li&gt;
+&lt;li&gt;(Windows) Edit your &lt;code&gt;solr.in.cmd&lt;/code&gt; file to 
include:
+  &lt;code&gt;set SOLR_OPTS=%SOLR_OPTS% 
-Dlog4j2.formatMsgNoLookups=true&lt;/code&gt;&lt;/li&gt;
 &lt;li&gt;Follow any of the other mitgations listed at 
https://logging.apache.org/log4j/2.x/security.html&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;&lt;strong&gt;References:&lt;/strong&gt;
diff --git a/output/news.html b/output/news.html
index 7399c54..2df99ce 100644
--- a/output/news.html
+++ b/output/news.html
@@ -148,8 +148,10 @@ Any of the following are enough to prevent this 
vulnerability:</p>
 <ul>
 <li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which 
will include an updated version of the log4j2 dependancy.</li>
 <li>Manually update the version of log4j2 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>
-<li>(Windows) Edit your <code>solr.in.cmd</code> file to include <code>set 
SOLR_OPTS=%SOLR_OPTS% -Dlog4j2.formatMsgNoLookups=true</code></li>
+<li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to include:
+  <code>SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li>
+<li>(Windows) Edit your <code>solr.in.cmd</code> file to include:
+  <code>set SOLR_OPTS=%SOLR_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>
 </ul>
 <p><strong>References:</strong>
diff --git a/output/security.html b/output/security.html
index ef18ab8..529c400 100644
--- a/output/security.html
+++ b/output/security.html
@@ -232,8 +232,10 @@ Any of the following are enough to prevent this 
vulnerability:</p>
 <ul>
 <li>Upgrade to <code>Solr 8.11.1</code> or greater (when available), which 
will include an updated version of the log4j2 dependancy.</li>
 <li>Manually update the version of log4j2 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>
-<li>(Windows) Edit your <code>solr.in.cmd</code> file to include <code>set 
SOLR_OPTS=%SOLR_OPTS% -Dlog4j2.formatMsgNoLookups=true</code></li>
+<li>(Linux/MacOS) Edit your <code>solr.in.sh</code> file to include:
+  <code>SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true"</code></li>
+<li>(Windows) Edit your <code>solr.in.cmd</code> file to include:
+  <code>set SOLR_OPTS=%SOLR_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>
 </ul>
 <p><strong>References:</strong>

Reply via email to