Hi Joe,
Adding to what Davyd wrote. I just searched the codebase and the JndiLookup
class (where the log4j vulnerability was found) does not exist in log4net. In
fact, there is no code related to jndi at all as far as I can see.
David
-Original Message-
From: Davyd McColl
Sent: Tues
Not sure I qualify to vote, but looks good to me
+1
David Schwartz
Get Outlook for Android<https://aka.ms/AAb9ysg>
From: Ralph Goers
Sent: Sunday, October 31, 2021 6:55:48 PM
To: dev@logging.apache.org
Subject: [EXTERNAL] Re: [Vote] Release log4net 2.0.
even
though I'm the only one maintaining it right now.
Thanks for the pr - I'll try check it out tomorrow.
-d
On October 24, 2021 11:29:52 David Schwartz wrote:
> Hi Log4Net,
>
> I have a PR to repair issue 611 for .netstandard 2.0 libraries.
>
> https://urldefense.c
://github.com/apache/logging-log4net/pull/76
I need this as part of the migration plan of our products to .net standard /
.net 5. Could someone please review/approve the PR and then release a new
version of log4net with this change?
Thank you
David Schwartz
NI
