Re: [log4j] Security page refactoring

[Matt Sicker]

Actually, I was able to review this just now during the lunch break.

> On Nov 7, 2023, at 1:24 PM, Matt Sicker  wrote:
> 
> Also note that I’m at KubeCon right now, so I won’t have a chance to review 
> this PR until, well, sometime during the conference. Possibly today, but 
> likely within the next day or two.
> 
>> On Nov 6, 2023, at 2:17 PM, Volkan Yazıcı  wrote:
>> 
>> I have created #1948 
>> refactoring the Log4j security page. See the PR description for details.
>> Reviews are welcome.
> 

Re: [log4j] Security page refactoring

[Matt Sicker]

Also note that I’m at KubeCon right now, so I won’t have a chance to review 
this PR until, well, sometime during the conference. Possibly today, but likely 
within the next day or two.

> On Nov 6, 2023, at 2:17 PM, Volkan Yazıcı  wrote:
> 
> I have created #1948 
> refactoring the Log4j security page. See the PR description for details.
> Reviews are welcome.

Re: [log4j] Security page refactoring

[Matt Sicker]

Not that it’s relevant to adopt right away, but do note that there is a CVSS 
4.0 now (that was finished quite recently) which is supposed to produce more 
useful severity scores.

> On Nov 6, 2023, at 2:17 PM, Volkan Yazıcı  wrote:
> 
> I have created #1948 
> refactoring the Log4j security page. See the PR description for details.
> Reviews are welcome.

[log4j] Security page refactoring

[Volkan Yazıcı]

I have created #1948 
refactoring the Log4j security page. See the PR description for details.
Reviews are welcome.