sylus edited a comment on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991401716
I'm not sure whether this effects zookeeper but I think you first would need
access to the solr pod so first mitigation suffices?
--
This is an automated message from the
sylus commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991401716
Does this not affect zookeeper i too see literally nothing about it anywhere.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
gerlowskija commented on a change in pull request #450:
URL: https://github.com/apache/solr/pull/450#discussion_r767068017
##
File path:
solr/solrj/src/java/org/apache/solr/client/solrj/request/beans/CreateCorePayload.java
##
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Sof
gerlowskija commented on a change in pull request #450:
URL: https://github.com/apache/solr/pull/450#discussion_r767067405
##
File path:
solr/core/src/test/org/apache/solr/handler/admin/V2CoresAPIMappingTest.java
##
@@ -0,0 +1,146 @@
+/*
+ * Licensed to the Apache Software Fou
sylus commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991399854
@plumdog were u able to find anything about zookeeper?
Also when this is set in solropts, is there a way for me to confirm it is
passed? I thought I would see it in the Solr
thelabdude commented on a change in pull request #52:
URL: https://github.com/apache/solr-site/pull/52#discussion_r767063125
##
File path: content/solr/security/2021-12-10-cve-2021-44228.md
##
@@ -11,7 +11,7 @@ Critical
**Description:**
Apache Solr releases prior to 8.11.1 we
thelabdude merged pull request #53:
URL: https://github.com/apache/solr-site/pull/53
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubs
uschindler commented on a change in pull request #52:
URL: https://github.com/apache/solr-site/pull/52#discussion_r767031901
##
File path: content/solr/security/2021-12-10-cve-2021-44228.md
##
@@ -11,7 +11,7 @@ Critical
**Description:**
Apache Solr releases prior to 8.11.1 we
uschindler commented on a change in pull request #52:
URL: https://github.com/apache/solr-site/pull/52#discussion_r767030548
##
File path: content/solr/security/2021-12-10-cve-2021-44228.md
##
@@ -11,7 +11,7 @@ Critical
**Description:**
Apache Solr releases prior to 8.11.1 we
madrob merged pull request #52:
URL: https://github.com/apache/solr-site/pull/52
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr..
janhoy commented on pull request #383:
URL: https://github.com/apache/solr/pull/383#issuecomment-991344883
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsub
janhoy merged pull request #383:
URL: https://github.com/apache/solr/pull/383
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@s
madrob merged pull request #51:
URL: https://github.com/apache/solr-site/pull/51
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr..
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457390#comment-17457390
]
ASF subversion and git services commented on SOLR-15843:
Commit e
thelabdude edited a comment on pull request #436:
URL: https://github.com/apache/solr/pull/436#issuecomment-991330781
Confirmed ... the query form getting submitted 2x each time you push the
`Execute Query` button exists on main! So that's bad and looks to be the cause
of why having `stats
uschindler commented on pull request #49:
URL: https://github.com/apache/solr-site/pull/49#issuecomment-991334713
That was the first time. Not sure what happened. It's all fine because the
info is at top of page, so it is still fine on Twitter.
No worries,
Uwe
--
This is an aut
anshumg merged pull request #442:
URL: https://github.com/apache/solr/pull/442
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@
thelabdude commented on pull request #436:
URL: https://github.com/apache/solr/pull/436#issuecomment-991330781
Confirmed ... the query form getting submitted 2x each time you push the
`Execute Query` button exists on main! So that's bad and looks to be the cause
of why having `stats.field=
thelabdude commented on pull request #436:
URL: https://github.com/apache/solr/pull/436#issuecomment-991321741
I suspect this is probably an existing bug (not introduced by the changes in
this PR) (see screenshot), but if you supply the same parameter more than once,
such as `stats.field`
anshumg commented on pull request #49:
URL: https://github.com/apache/solr-site/pull/49#issuecomment-991313065
I think this commit broke the link -
https://github.com/apache/solr-site/pull/48/files
The permalink is created from the `title` which was updated in that request,
breaking
uschindler commented on pull request #49:
URL: https://github.com/apache/solr-site/pull/49#issuecomment-991309717
The one I copypasted broke. Not sure why.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
anshumg commented on pull request #49:
URL: https://github.com/apache/solr-site/pull/49#issuecomment-991308418
@uschindler - This shouldn't have broken the permalink, just realized that
the link only has the CVE# and not the date
`https://solr.apache.org/security.html#apache-solr-
[
https://issues.apache.org/jira/browse/SOLR-15846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457345#comment-17457345
]
Michael Schumann commented on SOLR-15846:
-
I see that on [https://solr.apache.org
anshumg merged pull request #50:
URL: https://github.com/apache/solr-site/pull/50
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr.
plumdog edited a comment on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991251103
@HoustonPutman another thing I have just thought of: should we also be
concerned about the Zookeeper that is created for a SolrCloud?
Edit: or rather, that _may_ be
uschindler commented on pull request #49:
URL: https://github.com/apache/solr-site/pull/49#issuecomment-991265867
You broke permalink second time. 💩🤬
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
plumdog edited a comment on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991251103
@HoustonPutman another thing I have just thought of: should we also be
concerned about the Zookeeper that is created for a SolrCloud?
Edit: or rather, that _may_ be
anshumg merged pull request #49:
URL: https://github.com/apache/solr-site/pull/49
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr.
dsmiley commented on pull request #221:
URL: https://github.com/apache/solr/pull/221#issuecomment-991257166
This wasn't done; it's follow-up tiny stuff. @NazerkeBS there are a couple
things remaining I asked of you -- the empty catch, and loadConfigSetProperties
--
This is an automated
plumdog edited a comment on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991251103
@HoustonPutman another thing I have just thought of: should we also be
concerned about the Zookeeper that is created for a SolrCloud?
Edit: or rather, that _may_ be
plumdog commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991251103
@HoustonPutman another thing I have just thought of: should we also be
concerned about the Zookeeper that is created for a SolrCloud?
--
This is an automated message from the A
[
https://issues.apache.org/jira/browse/SOLR-15846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457340#comment-17457340
]
Michael Schumann commented on SOLR-15846:
-
https://logging.apache.org/log4j/2.x/s
Michael Schumann created SOLR-15846:
---
Summary: High security vulnerability in Log4J - CVE-2021-44228
bundled with Solr
Key: SOLR-15846
URL: https://issues.apache.org/jira/browse/SOLR-15846
Project:
andyetitmoves commented on pull request #383:
URL: https://github.com/apache/solr/pull/383#issuecomment-991238699
> I skimmed the code and believe you are right. Do you agree @andyetitmoves ?
Yep, that's correct.
--
This is an automated message from the Apache Git Service.
To respo
anshumg commented on pull request #49:
URL: https://github.com/apache/solr-site/pull/49#issuecomment-991221939
Something to remember is that this would break the permalink (in case folks
have already shared that)
--
This is an automated message from the Apache Git Service.
To respond to
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457317#comment-17457317
]
ASF subversion and git services commented on SOLR-15843:
Commit f
madrob merged pull request #454:
URL: https://github.com/apache/solr/pull/454
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@s
thelabdude commented on a change in pull request #453:
URL: https://github.com/apache/solr/pull/453#discussion_r766896056
##
File path: solr/core/src/java/org/apache/solr/handler/SQLHandler.java
##
@@ -145,17 +150,56 @@ public String getSource() {
private boolean firstTupl
sonatype-lift[bot] commented on a change in pull request #453:
URL: https://github.com/apache/solr/pull/453#discussion_r766896087
##
File path: solr/core/src/java/org/apache/solr/handler/SQLHandler.java
##
@@ -145,17 +150,56 @@ public String getSource() {
private boolean f
uschindler edited a comment on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991169501
> > > You should not expect additional 8.9.z releases
> >
> >
> > @madrob So if I want something both stable and patched, I'll need
8.11.next?
>
> I would
madrob merged pull request #48:
URL: https://github.com/apache/solr-site/pull/48
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr..
madrob merged pull request #47:
URL: https://github.com/apache/solr-site/pull/47
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr..
ctargett commented on a change in pull request #47:
URL: https://github.com/apache/solr-site/pull/47#discussion_r766874626
##
File path: content/solr/security/2021-12-12-cve-2021-44228.md
##
@@ -14,8 +14,10 @@ Apache Solr releases prior to 8.11.1 were using a bundled
version o
ctargett commented on a change in pull request #47:
URL: https://github.com/apache/solr-site/pull/47#discussion_r766874295
##
File path: content/solr/security/2021-12-12-cve-2021-44228.md
##
@@ -25,5 +27,13 @@ Any of the following are enough to prevent this
vulnerability:
`
uschindler commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991169501
> > > You should not expect additional 8.9.z releases
> >
> >
> > @madrob So if I want something both stable and patched, I'll need
8.11.next?
>
> I would NOT wai
thelabdude commented on a change in pull request #47:
URL: https://github.com/apache/solr-site/pull/47#discussion_r766867553
##
File path: content/solr/security/2021-12-12-cve-2021-44228.md
##
@@ -25,5 +27,13 @@ Any of the following are enough to prevent this
vulnerability:
uschindler commented on a change in pull request #454:
URL: https://github.com/apache/solr/pull/454#discussion_r766867101
##
File path: solr/bin/solr.in.cmd
##
@@ -213,8 +213,8 @@ REM set SOLR_ADMIN_UI_DISABLED=false
REM Solr is by default allowed to read and write data from/t
uschindler commented on a change in pull request #45:
URL: https://github.com/apache/solr-site/pull/45#discussion_r766846751
##
File path: content/solr/security/2021-12-12-cve-2021-44228.md
##
@@ -0,0 +1,27 @@
+Title: Apache Solr affected by Apache Log4J CVE-2021-44228: JNDI fe
thelabdude commented on pull request #436:
URL: https://github.com/apache/solr/pull/436#issuecomment-991139800
I'll kick the tires on this now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to th
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457269#comment-17457269
]
Cassandra Targett commented on SOLR-15843:
--
> I couldn't find a great place in t
[
https://issues.apache.org/jira/browse/SOLR-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houston Putman resolved SOLR-8319.
--
Fix Version/s: main (9.0)
8.11.1
Resolution: Fixed
> NPE when creating
[
https://issues.apache.org/jira/browse/SOLR-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457261#comment-17457261
]
ASF subversion and git services commented on SOLR-8319:
---
Commit 82f9
[
https://issues.apache.org/jira/browse/SOLR-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457260#comment-17457260
]
ASF subversion and git services commented on SOLR-8319:
---
Commit 2079
[
https://issues.apache.org/jira/browse/SOLR-15840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457248#comment-17457248
]
Mark Robert Miller commented on SOLR-15840:
---
https://github.com/eclipse/jetty.p
[ https://issues.apache.org/jira/browse/SOLR-15843 ]
Mike Drob deleted comment on SOLR-15843:
--
was (Author: mdrob):
Security page has been updated -
https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228-jndi-fea
HoustonPutman commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991105023
Pinning this, so that others can see the mitigation step if they come
looking for information.
--
This is an automated message from the Apache Git Service.
To respond to
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457239#comment-17457239
]
Mike Drob commented on SOLR-15843:
--
Security page has been updated -
https://solr.apach
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457240#comment-17457240
]
Houston Putman commented on SOLR-15843:
---
The CVE is now listed on the security page
HoustonPutman commented on issue #384:
URL: https://github.com/apache/solr-operator/issues/384#issuecomment-991101468
That is the correct way to mitigate the CVE.
And you are correct, it's a good option to have by default.
--
This is an automated message from the Apache Git Service
HoustonPutman merged pull request #46:
URL: https://github.com/apache/solr-site/pull/46
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-uns
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457238#comment-17457238
]
Mike Drob commented on SOLR-15843:
--
> We should also give a hint in the release notes
I
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457236#comment-17457236
]
Jan Høydahl commented on SOLR-15844:
Why do you believe it is the same? The 2019 cve
madrob merged pull request #45:
URL: https://github.com/apache/solr-site/pull/45
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr..
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457232#comment-17457232
]
Mike Drob commented on SOLR-15843:
--
bq. I am not sure about this. Who reads the example
HoustonPutman commented on a change in pull request #45:
URL: https://github.com/apache/solr-site/pull/45#discussion_r766790950
##
File path: content/solr/security/2021-12-12-cve-2021-44228.md
##
@@ -0,0 +1,27 @@
+Title: Apache Solr affected by Apache Log4J CVE-2021-44228: JNDI
HoustonPutman commented on issue #382:
URL: https://github.com/apache/solr-operator/issues/382#issuecomment-991086348
ahhh so that pod options is for the Solr cluster.
For the zookeeper cluster, use the following in your SolrCloud resource:
```yaml
spec:
zookeeperRef:
plumdog opened a new issue #384:
URL: https://github.com/apache/solr-operator/issues/384
I believe from
https://github.com/apache/solr/pull/454#issuecomment-991066278 and
https://apache.github.io/solr-operator/docs/solr-cloud/solr-cloud-crd.html#custom-solrxml
that to mitigate, I need to
uschindler edited a comment on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991066278
> > You should not expect additional 8.9.z releases
>
> @madrob So if I want something both stable and patched, I'll need
8.11.next?
I would NOT wait for a rel
uschindler commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991066278
> > You should not expect additional 8.9.z releases
>
> @madrob So if I want something both stable and patched, I'll need
8.11.next?
I would NOT wait for a release or
plumdog commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991044672
> You should not expect additional 8.9.z releases
@madrob So if I want something both stable and patched, I'll need 8.11.next?
--
This is an automated message from the Apache
acdha commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991043291
I was wondering whether someone could confirm that the top-level version
lock will also affect the contrib prometheus-exporter. My scan of our container
images turned up a second copy
uschindler commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991041323
> Also, regarding Solr 5 and 6 and log4j: apache/logging-log4j2#608 (comment)
This is only a problem if you use special appenders, which solr does not do.
--
This is an au
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457189#comment-17457189
]
Uwe Schindler commented on SOLR-15843:
--
I am not sure about this. Who reads the exam
madrob commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991035511
> Should we expect patched releases for older 8.x versions? In my case, 8.9?
Or will I have to take 8.11?
You should not expect additional 8.9.z releases
--
This is an automa
plumdog commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991031845
Also, regarding Solr 5 and 6 and log4j:
https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126
Based on that, I think they would be affected.
--
This is an
plumdog commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991010332
Should we expect patched releases for older 8.x versions? In my case, 8.9?
Or will I have to take 8.11?
--
This is an automated message from the Apache Git Service.
To respond to t
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457167#comment-17457167
]
Mike Drob commented on SOLR-15843:
--
We could add that to our example configurations as w
uschindler commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-991006777
> Release notes or the security page on the site (or both?)
>
> Solr 7 is affected but AFAICT Solr 5 and 6 are not because they use log4j
1.2.17
I would maybe do both
madrob commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-990999055
Release notes or the security page on the site (or both?)
Solr 7 is affected but AFAICT Solr 5 and 6 are not because they use log4j
1.2.17
--
This is an automated message fro
[
https://issues.apache.org/jira/browse/SOLR-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457158#comment-17457158
]
Uwe Schindler commented on SOLR-15843:
--
We should also give a hint in the release no
uschindler commented on pull request #454:
URL: https://github.com/apache/solr/pull/454#issuecomment-990987372
> Hey team, can this also be backported to 7.7 as a new 7.7.4 release? Many
people still running Solr 7 will also require this fix.
This won't happen anymore as 7.x is out o
[
https://issues.apache.org/jira/browse/SOLR-14607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457140#comment-17457140
]
Jan Høydahl commented on SOLR-14607:
Reviving stale discussion. I have not spent much
janhoy commented on a change in pull request #72:
URL: https://github.com/apache/solr/pull/72#discussion_r70057
##
File path: solr/licenses/README.committers.md
##
@@ -0,0 +1,54 @@
+# Licensing Information for Committers
+
+When a new dependency is added to Solr (or an exis
janhoy commented on pull request #221:
URL: https://github.com/apache/solr/pull/221#issuecomment-990950077
The JIRA for this PR is closed. Should this PR also be closed or is there
still work that needs to be merged?
--
This is an automated message from the Apache Git Service.
To respond
janhoy commented on pull request #386:
URL: https://github.com/apache/solr/pull/386#issuecomment-990948776
This issue https://issues.apache.org/jira/browse/SOLR-15337 has three
main-branch PRs #104 , #160 and this. The JIRA and both the other PRs are
merged. Is this last PR supposed to be
janhoy commented on pull request #383:
URL: https://github.com/apache/solr/pull/383#issuecomment-990947149
And I wouldn't bother with a JIRA for just a one-line refguide correction.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
janhoy commented on pull request #383:
URL: https://github.com/apache/solr/pull/383#issuecomment-990946538
I skimmed the code and believe you are right. Do you agree @andyetitmoves ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457121#comment-17457121
]
Gus Heck edited comment on SOLR-15844 at 12/10/21, 12:39 PM:
-
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457121#comment-17457121
]
Gus Heck commented on SOLR-15844:
-
The velocity one is
https://solr.apache.org/security.
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl reassigned SOLR-15844:
--
Assignee: Jan Høydahl
> High security vulnerability in Apache Velocity (+2) - CVE-2020-13936 (
Jan Høydahl created SOLR-15845:
--
Summary: Solr needs its own Version class
Key: SOLR-15845
URL: https://issues.apache.org/jira/browse/SOLR-15845
Project: Solr
Issue Type: Improvement
Secur
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-15844:
---
Fix Version/s: 8.11.1
> High security vulnerability in Apache Velocity (+2) - CVE-2020-13936 (+1)
>
gthvidsten edited a comment on issue #382:
URL: https://github.com/apache/solr-operator/issues/382#issuecomment-990775921
Thanks. Adding the `podOptions` mostly worked!
Almost all the pods are now up and running, except one of the zookeeper
replicas, which gave the following error:
gthvidsten edited a comment on issue #382:
URL: https://github.com/apache/solr-operator/issues/382#issuecomment-990775921
Thanks. Adding the `podOptions` mostly worked!
Almost all the pods are now up and running, except one of the zookeeper
replicas (`example-solrcloud-zookeeper-1`),
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-15844:
---
Priority: Blocker (was: Major)
> High security vulnerability in Apache Velocity (+2) - CVE-2020-1393
[
https://issues.apache.org/jira/browse/SOLR-15844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457003#comment-17457003
]
Jan Høydahl commented on SOLR-15844:
I'll attempt a patch for 8.11.1
> High security
betulince commented on pull request #436:
URL: https://github.com/apache/solr/pull/436#issuecomment-990731056
Hello,
I sent another commit which I changed the improvement based on feedbacks, I
am waiting for you to check so I can move forward with another improvements.
Timot
97 matches
Mail list logo
