Hi All,
Is ignite impacted by this critical vulnerability?
https://securityboulevard.com/2022/03/cyrc-vulnerability-analysis-two-distinct-spring-vulnerabilities-discovered-spring4shell-and-cve-2022-22963/
Regards,
Vishwas
Is ignite impacted by CVE-2021-42392 ?
https://jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/
Regards,
Vishwas
Any inputs on this?
On Thu, 23 Dec, 2021, 17:31 Vishwas Bm, wrote:
> Hi,
>
> In the javadocs I see that the value of getCurrentCpuLoad is in the range
> [0,1]
>
> https://www.javadoc.io/static/org.apache.ignite/ignite-core/2.11.1/org/apac
Hi,
In the javadocs I see that the value of getCurrentCpuLoad is in the range
[0,1]
https://www.javadoc.io/static/org.apache.ignite/ignite-core/2.11.1/org/apache/ignite/internal/ClusterLocalNodeMetricsMXBeanImpl.html#getCurrentCpuLoad--
But in the code I see the value getting multiplied by 100.
Correct url to rest-http module
https://github.com/apache/ignite/blob/21f7ca41c4348909e2fd26ccf59b5b2ce1f4474e/modules/rest-http/pom.xml#L131
On Mon, 20 Dec, 2021, 16:06 Vishwas Bm, wrote:
> Hi,
>
> Why is ignite rest module still using old log4j version dependency?
>
>
>
Hi,
Why is ignite rest module still using old log4j version dependency?
https://github.com/apache/ignite/blob/21f7ca41c4348909e2fd26ccf59b5b2ce1f4474e/modules/log4j/pom.xml#L46
Can this be removed ? There is a critical CVE against this package.
Regards,
Vishwas
On Wed, 15 Dec, 2021, 12:57
Hi Raymond,
This is an issue related to repository configuration in settings.xml.
You can find more information in below thread
http://apache-ignite-developers.2346864.n4.nabble.com/Building-Ignite-with-Adopt-OpenJDK-11-td52389.html#a52391
Regards,
Vishwas
On Wed, 12 May, 2021, 05:17 Raymond
Hi Marius,
This is more of a mvn repository issue. The jacorb jar is found at below
link
https://repository.ow2.org/nexus/content/repositories/ow2-legacy/org/jacorb/jacorb/2.2.3-jonas-patch-20071018/
You need to add this repo in your settings.xml file.
Regards,
Vishwas
On Sun, 18 Apr, 2021,
Hi,
Is this related to issue seen with
IGNITE-13912 ?
I had hit IGNITE-13912 when I was using ignite 2.9 release.
I am yet to try my use case with the fix provided as part of IGNITE-13912
Regards,
Vishwas
On Tue, 26 Jan, 2021, 21:18 ткаленко кирилл, wrote:
> Hello, everyone!
>
> Currently,
Hi Denis,
Thanks for the feedback.
I had also put a comment in one of your PR regarding iep-41.
https://github.com/apache/ignite/pull/8038#issuecomment-742230009
It will be great if you can provide input on this.
Regards,
Vishwas
On Fri, 18 Dec, 2020, 21:39 Denis Garus, wrote:
> Hi!
> I
Hi Denis,
Thanks for the reply.
I will try to use the version of kafka-ext available in mvn repository with
ignite master branch code.
Regards,
Vishwas
On Sat, 19 Dec, 2020, 01:48 Denis Magda, wrote:
> Hi Vishwas,
>
> Kafka and all other extensions I being moved to that separate repository
>
ributes can't be used to spread a thin client's security context.
> For this purpose, you can use a cache of Ignite, a third-party database,
> or other tools appropriate to your case.
>
> сб, 28 нояб. 2020 г. в 06:16, Vishwas Bm :
>
> > Hi Denis,
> >
> >
> > T
e node is up to the
> plugin's developers.
>
> Also, you have to implement the GridSecurityProcessor.securityContext(UUID
> subjId) method,
>
> the way this method is used in Ignite can see in the task description [1].
>
>
>
>
>1. https://issues.apache.org/jira/bro
Hi,
I was facing an issue with a custom security plugin and thin remote client.
I am using Ignite 2.9.0 version and I am hitting below issue
https://cwiki.apache.org/confluence/display/IGNITE/IEP-41%3A+Security+Context+of+thin+client+on+remote+nodes
I had asked the question in the user listing
14 matches
Mail list logo