Re: [log4j] 2.x changelog

2023-03-10 Thread Gary Gregory
Thank you Volkan :-) Gary On Fri, Mar 10, 2023, 08:53 Volkan Yazıcı wrote: > In `/CHANGELOG.adoc`. There is nothing special about it. Create a > `/src/changelog/.2.x.x/-.xml` file, you can use the > existing ones for inspiration, that is it. > > On Fri, Mar 10, 2023 at 1:51 PM Gary D. Gregory

Re: [log4j] Checkout from git is broken

2023-03-10 Thread Piotr P. Karwasz
Hi Gary, On Fri, 10 Mar 2023 at 12:47, Gary Gregory wrote: > So the branch renaming broke cloning and checking out code with the most > basic git command? At least that's what the side effect seems to me. What's > the fix? Or will no one ever be able to say 'git clone' as below and have > it just

Re: [log4j] 2.x changelog

2023-03-10 Thread Volkan Yazıcı
In `/CHANGELOG.adoc`. There is nothing special about it. Create a `/src/changelog/.2.x.x/-.xml` file, you can use the existing ones for inspiration, that is it. On Fri, Mar 10, 2023 at 1:51 PM Gary D. Gregory wrote: > Hi All: > > Where are the steps I can follow to add an entry to the changelog

CVE-2023-26464: Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender

2023-03-10 Thread Arnout Engelen
Severity: low Description: ** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested) hashmap or hashtable (depending on which log

Re: [log4j] Checkout from git is broken

2023-03-10 Thread Gary D. Gregory
On 2023/03/10 12:42:00 Volkan Yazıcı wrote: > If you browse to https://github.com/apache/logging-log4j2 and clone the > repository as described there: > > git clone g...@github.com:apache/logging-log4j2.git > > This not only works, but also lands you on the right branch: `2.x`. Pardon me for

[log4j] 2.x changelog

2023-03-10 Thread Gary D. Gregory
Hi All: Where are the steps I can follow to add an entry to the changelog (in this case for 2.20.1)? TY! Gary

Re: [log4j] Checkout from git is broken

2023-03-10 Thread Volkan Yazıcı
If you browse to https://github.com/apache/logging-log4j2 and clone the repository as described there: git clone g...@github.com:apache/logging-log4j2.git This not only works, but also lands you on the right branch: `2.x`. On Fri, Mar 10, 2023 at 12:47 PM Gary Gregory wrote: > So the branc

Re: Compiling with JDK 11 or JDK 17

2023-03-10 Thread Gary D. Gregory
I'm OK with our tooling requiring whatever makes our lives simplest as long we can guarantee that the target byte codes and *API calls* will work on Java 8 for 2.x. Gary On 2023/03/08 19:29:29 Volkan Yazıcı wrote: > I completely support both initiatives: > > 1. Moving the JDK to 17 (why stay

Re: [log4j] Checkout from git is broken

2023-03-10 Thread Gary Gregory
So the branch renaming broke cloning and checking out code with the most basic git command? At least that's what the side effect seems to me. What's the fix? Or will no one ever be able to say 'git clone' as below and have it just work? Gary On Fri, Mar 10, 2023, 05:18 Volkan Yazıcı wrote: > We

Re: [log4j] Checkout from git is broken

2023-03-10 Thread Volkan Yazıcı
We mention the `gitbox` keyword neither in the sources, nor in the docs. There is a GitHub link at the top right corner of every page in the website. `pom.xml`s SCM block points to GitHub. `CONTRIBUTING.md` only hints to GitHub resources – though I agree there is no direct link to the repository