Am 15.12.21 um 19:23 schrieb Milamber:
> Hello,
>
> The first release candidate for JMeter 5.4.2 (f393453287) has been
> prepared, and your votes are solicited.
>
> This release is only a vulnerabily fix release about the
> CVE-2021-44228: Apache Log4j2 JNDI features do not protect against
> attac
Thank you Milamber
+1
The release looks good to me.
Vladimir
Hello,
Thanks for release Milamber
+1 I support this release
Regards
On Wednesday, December 15, 2021, Milamber wrote:
> Hello,
>
> The first release candidate for JMeter 5.4.2 (f393453287) has been
> prepared, and your votes are solicited.
>
> This release is only a vulnerabily fix release abo
Hello,
The first release candidate for JMeter 5.4.2 (f393453287) has been
prepared, and your votes are solicited.
This release is only a vulnerabily fix release about the CVE-2021-44228:
Apache Log4j2 JNDI features do not protect against attacker controlled
LDAP and other JNDI related endpoi
kevin-imbus commented on pull request #680:
URL: https://github.com/apache/jmeter/pull/680#issuecomment-994978210
Quick reminder that there are unreleased nightly builds for JMeter available
that you can use at your own risk :)
https://ci.apache.org/projects/jmeter/nightlies/
--
T
sebiboga commented on pull request #680:
URL: https://github.com/apache/jmeter/pull/680#issuecomment-994970222
in case you're running JMeter in Windows, I wrote a batch file that automate
what you need to do;
documentation and instructions can be found here - of course steps are
impleme
I suggest naming the branch as release/5.4.x (or branch/5.4.x or
branch/5.4), so we can cut 5.4.x releases from it (e.g. in case more CVEs
are to be fixed)
Of course, it is not a show-stopper now, and we can create the branch later.
Having an explicit branch is helpful for creating PRs that target
A 5.4.2 would be great.
A 5.5 could be harder, as there are usually some smaller things, that pop up.
Felix
Am 15. Dezember 2021 09:06:39 MEZ schrieb Milamber :
>Hi,
>
>5.5 is ready to release or need some commits?
>
>I will prepare 5.4.2 (just fix Log4J)
>
>Milamber
>
>On 15/12/2021 09:04, Phi
kevin-imbus edited a comment on pull request #680:
URL: https://github.com/apache/jmeter/pull/680#issuecomment-993684734
I can confirm that @FSchumacher's suggestion works with JMeter 5.4.1 and
log4j 2.16.0. Thank you!
@vlsi Many thanks for your fix! :)
Edit: Also works flawle
Hello,
The Version log4j 2.15 is incomplete 😫😫
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046
Anas
On Wed, Dec 15, 2021 at 9:15 AM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:
> I think 5.5 is ready.
>
> Vladimir
>
--
Cordialement,
-
Anas OUFDOU
I think 5.5 is ready.
Vladimir
Hi,
5.5 is ready to release or need some commits?
I will prepare 5.4.2 (just fix Log4J)
Milamber
On 15/12/2021 09:04, Philippe Mouawad wrote:
Hello Milamber,
If you're available, it would be good to release:
- 5.4.2 with just the fix for Log4J
- 5.5 (fix+improvements)
If not, just 5
Hello Milamber,
If you're available, it would be good to release:
- 5.4.2 with just the fix for Log4J
- 5.5 (fix+improvements)
If not, just 5.5
Thanks
On Wed, Dec 15, 2021 at 9:02 AM Milamber wrote:
> Hi,
>
> Probably need to release ASAP a fix version? 5.4.1? (from tag with just
> the
Hi,
Probably need to release ASAP a fix version? 5.4.1? (from tag with just
the fix for Log4J) or new version 5.5 (fix+improvements)?
Milamber
On 14/12/2021 21:42, Philippe Mouawad wrote:
Hello,
For information:
- https://blogs.apache.org/security/entry/cve-2021-44228
Regards
On Tuesday, D
14 matches
Mail list logo
