So what next, what I should do exactly now ?
-Original Message-
From: Ralph Goers
Sent: Saturday, April 22, 2023 4:32 AM
To: dev@logging.apache.org
Cc: Gurumoorthi Vijayalingam
Subject: Re: [External] Re: Log4j Issue
CAUTION: This message was sent from outside of the company. Please
Hi all,
On Sat, 22 Apr 2023 at 01:02, Ralph Goers wrote:
>
> Note that he may also have a shaded jar that has Log4j embedded in it. That
> would be impossible for us to know without personally inspecting the
> deployment.
That's something that can be discovered with a shell script like this:
25 2022 i18n-slf4j-1.4.4.jar
>> -rwxr-xr-x. 1 fruser fruser 301872 Mar 2 17:28 log4j-api-2.17.1.jar
>> -rwxr-xr-x. 1 fruser fruser 1790452 Mar 2 17:28 log4j-core-2.17.1.jar
>>
>> Regards,
>> Guru.
>>
>> -Original Message-----
>> Fro
17:28 log4j-api-2.17.1.jar
> -rwxr-xr-x. 1 fruser fruser 1790452 Mar 2 17:28 log4j-core-2.17.1.jar
>
> Regards,
> Guru.
>
> -Original Message-
> From: Christian Grobmeier
> Sent: Friday, April 21, 2023 4:55 PM
> To: Gurumoorthi Vijayalingam ;
> dev@log
Grobmeier
Sent: Friday, April 21, 2023 4:55 PM
To: Gurumoorthi Vijayalingam ; dev@logging.apache.org
Subject: Re: [External] Re: Log4j Issue
CAUTION: This message was sent from outside of the company. Please do not click
links or open attachments unless you recognize the source of this email
der. The problem
> occurred when we upgraded the jar files from 2.2 t o2.17
>
>
> Regards,
> Guru.
>
> -Original Message-
> From: Christian Grobmeier
> Sent: Friday, April 21, 2023 4:36 PM
> To: Gurumoorthi Vijayalingam ;
> dev@logging.apache.org
>
Subject: Re: [External] Re: Log4j Issue
CAUTION: This message was sent from outside of the company. Please do not click
links or open attachments unless you recognize the source of this email and
know the content is safe.
Hello Gurumoorthi,
please subscribe to dev@logging.apache.org by sending
Any help on this request ? we stuck.
-Original Message-
From: Gurumoorthi Vijayalingam
Sent: Thursday, April 13, 2023 7:36 AM
To: Christian Grobmeier ; dev@logging.apache.org
Subject: RE: [External] Re: Log4j Issue
Hi Team,
We tried the steps as Christian mentioned in below email
am wrote:
> Any help on this request ? we stuck.
>
> -Original Message-
> From: Gurumoorthi Vijayalingam
> Sent: Thursday, April 13, 2023 7:36 AM
> To: Christian Grobmeier ; dev@logging.apache.org
> Subject: RE: [External] Re: Log4j Issue
>
> Hi Team,
>
&g
t; dev@logging.apache.org
> Cc: Paolo Gil Ostrea ; Roark Hamilton
> ; Bhavana Pujari ; Sireesha Kutala
>
> Subject: Re: [External] Re: Log4j Issue
>
> CAUTION: This message was sent from outside of the company. Please do not
> click links or open attachments unless y
: Paolo Gil Ostrea ; Roark Hamilton
; Bhavana Pujari ; Sireesha Kutala
Subject: Re: [External] Re: Log4j Issue
CAUTION: This message was sent from outside of the company. Please do not click
links or open attachments unless you recognize the source of this email and
know the content is safe
Hello Gurumoorthi,
Piotr already responded to your email:
> MapLookup#newMap changed from private (as in 2.2) to package (as in
> 2.17.1) in the course of history. Your Tomcat is picking up the
> private one, which means that log4j-core-2.2.jar is still on the
> classpath.
> Double check that
Hi Team,
Can you please help us to fix this issue.
Regards,
Guru.
From: Dominik Psenner
Sent: 04 March 2023 02:16
To: secur...@logging.apache.org
Cc: Paolo Gil Ostrea ; Roark Hamilton
; Gurumoorthi Vijayalingam
Subject: [External] Re: Log4j Issue
CAUTION: This message was sent from outside
13 matches
Mail list logo
