ams-tschoening merged pull request #92:
URL: https://github.com/apache/logging-log4cxx/pull/92
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466706#comment-17466706
]
Mike Li commented on LOG4J2-3295:
-
Ralph, thanks for the detailed explanation. The reason that I am
vy commented on pull request #671:
URL: https://github.com/apache/logging-log4j2/pull/671#issuecomment-1002900021
@ramananravi, we think there are a few more places in the code where a
similar improvement might be handy. Mind creating a JIRA ticket for this
change, please?
--
This is
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-3295.
-
Resolution: Won't Fix
> Reconfiguration failure with an error
>
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466684#comment-17466684
]
Ralph Goers commented on LOG4J2-3295:
-
Mike, what you are asking for is simply not possible. Log4j
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466646#comment-17466646
]
Mike Li commented on LOG4J2-3295:
-
Hi Ralph,
Thank you for your comments. It's true that the current
carterkozak closed pull request #672:
URL: https://github.com/apache/logging-log4j2/pull/672
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
carterkozak commented on pull request #672:
URL: https://github.com/apache/logging-log4j2/pull/672#issuecomment-1002808751
This was meant to match the `README.md` file. No strong preference either
way from my end, I opted for exclusion initially since it's easier to read
through the file
sullis commented on pull request #673:
URL: https://github.com/apache/logging-log4j2/pull/673#issuecomment-1002759421
Mistaken PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
sullis closed pull request #673:
URL: https://github.com/apache/logging-log4j2/pull/673
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
sullis opened a new pull request #673:
URL: https://github.com/apache/logging-log4j2/pull/673
latest version of Mockito
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
Vladimir Sitnikov created LOG4J2-3301:
-
Summary: Please merge PR#18 to logging-log4j1
Key: LOG4J2-3301
URL: https://issues.apache.org/jira/browse/LOG4J2-3301
Project: Log4j 2
Issue Type:
sullis closed pull request #445:
URL: https://github.com/apache/logging-log4j2/pull/445
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
sullis commented on pull request #445:
URL: https://github.com/apache/logging-log4j2/pull/445#issuecomment-1002749381
obsolete.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
sullis commented on pull request #446:
URL: https://github.com/apache/logging-log4j2/pull/446#issuecomment-1002749324
obsolete.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
sullis closed pull request #446:
URL: https://github.com/apache/logging-log4j2/pull/446
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466577#comment-17466577
]
Marco Tenti edited comment on LOG4J2-3254 at 12/29/21, 7:27 PM:
The use
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466577#comment-17466577
]
Marco Tenti edited comment on LOG4J2-3254 at 12/29/21, 7:27 PM:
The use
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466577#comment-17466577
]
Marco Tenti edited comment on LOG4J2-3254 at 12/29/21, 7:27 PM:
The use
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466577#comment-17466577
]
Marco Tenti commented on LOG4J2-3254:
-
The use case is actually very simple, i downloaded a Redhat
Matt Sicker created LOG4J2-3300:
---
Summary: Add annotations for specifying conditional plugins
Key: LOG4J2-3300
URL: https://issues.apache.org/jira/browse/LOG4J2-3300
Project: Log4j 2
Issue
Matt Sicker created LOG4J2-3299:
---
Summary: Add structured format for configuring PropertiesUtil
settings
Key: LOG4J2-3299
URL: https://issues.apache.org/jira/browse/LOG4J2-3299
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466554#comment-17466554
]
Matt Sicker commented on LOG4J2-3259:
-
As somewhat noticed in LOG4J2-3296, this could also have
[
https://issues.apache.org/jira/browse/LOG4J2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466549#comment-17466549
]
Matt Sicker commented on LOG4J2-3293:
-
There's a bit of an eventual consistency problem here: we
[
https://issues.apache.org/jira/browse/LOG4J2-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466535#comment-17466535
]
Ralph Goers commented on LOG4J2-3297:
-
Yes, I fully understand your point of view. It is precisely
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/577/
Project:
release-2.x
Date of build:
Wed, 29 Dec 2021 15:31:03 +
Build duration:
1 hr 31 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s),
[
https://issues.apache.org/jira/browse/LOG4J2-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466531#comment-17466531
]
Peter Malone commented on LOG4J2-3297:
--
[~rgoers] if I can explain it another way, loading
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466515#comment-17466515
]
Ralph Goers commented on LOG4J2-3295:
-
Ok. But when a reconfiguration has errors Log4j is supposed
[
https://issues.apache.org/jira/browse/LOG4J2-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-3297:
---
Assignee: Ralph Goers
> Disable remote loading of log4j configuration to prevent MiTM
[
https://issues.apache.org/jira/browse/LOG4J2-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466514#comment-17466514
]
Ralph Goers commented on LOG4J2-3297:
-
This would not qualify for a CVE. Simply doing bad or
[
https://issues.apache.org/jira/browse/LOG4J2-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466513#comment-17466513
]
Ralph Goers commented on LOG4J2-2240:
-
I apologize. I still haven't gotten to it.
> Is there a
[
https://issues.apache.org/jira/browse/LOG4J2-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-3296.
-
Resolution: Duplicate
> Log4j 2.17.1 ‘Properties’ Uncontrolled CPU Resource Consumption
>
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466508#comment-17466508
]
Ralph Goers edited comment on LOG4J2-3254 at 12/29/21, 4:22 PM:
Can you
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466508#comment-17466508
]
Ralph Goers commented on LOG4J2-3254:
-
Can you provide a sample application. Our OSGi tests pass and
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Li updated LOG4J2-3295:
Summary: Reconfiguration failure with an error (was: Reconfiguration error)
> Reconfiguration failure
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
[
https://issues.apache.org/jira/browse/LOG4J2-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Pavlovich updated LOG4J2-3298:
---
Description:
Currently, if a JSON string is pushed to ThreadContext, it will be escaped. It
Matt Pavlovich created LOG4J2-3298:
--
Summary: Update JSONTemplateFormat to support not escaping certain
payloads
Key: LOG4J2-3298
URL: https://issues.apache.org/jira/browse/LOG4J2-3298
Project:
garydgregory commented on pull request #668:
URL: https://github.com/apache/logging-log4j2/pull/668#issuecomment-1002652178
Hi @Kenducky
Thank you for your PR.
You'll want to look at the branch 'release-2.x', that where the 2.x releases
originate while the branch 'master' is for
rm5248 commented on pull request #90:
URL: https://github.com/apache/logging-log4cxx/pull/90#issuecomment-1002651075
My current thought is that we'll do a 0.13.0 release in a few weeks; there
are a number of fixes for that already in master. next_stable probably won't
be for several
[
https://issues.apache.org/jira/browse/LOG4J2-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466477#comment-17466477
]
Gary D. Gregory commented on LOG4J2-2951:
-
[~thackel]
Thank you for the confirmation.
Do
Peter Malone created LOG4J2-3297:
Summary: Disable remote loading of log4j configuration to prevent
MiTM Attacks
Key: LOG4J2-3297
URL: https://issues.apache.org/jira/browse/LOG4J2-3297
Project: Log4j
[
https://issues.apache.org/jira/browse/LOG4J2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466471#comment-17466471
]
Gary D. Gregory commented on LOG4J2-3293:
-
Hello [~yhorndt]
The 2.12.4 and 2.3.2 releases are
[
https://issues.apache.org/jira/browse/LOG4J2-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466460#comment-17466460
]
Lado Kumsiashvili commented on LOG4J2-2240:
---
What ist the status of this ticket?
> Is there a
[
https://issues.apache.org/jira/browse/LOG4J2-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466453#comment-17466453
]
Yannik Horndt commented on LOG4J2-3293:
---
[~mattsicker] When you say backported to 2.12.4, do you
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Li reopened LOG4J2-3295:
-
I am reopening the issue as the reason explained in my last comment.
> Reconfiguration error
>
[
https://issues.apache.org/jira/browse/LOG4J2-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466447#comment-17466447
]
Mike Li commented on LOG4J2-3295:
-
It is understandable of the error message. But the major issue is
Maksymilian created LOG4J2-3296:
---
Summary: Log4j 2.17.1 ‘Properties’ Uncontrolled CPU Resource
Consumption
Key: LOG4J2-3296
URL: https://issues.apache.org/jira/browse/LOG4J2-3296
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Hackel closed LOG4J2-2951.
-
I can confirm that starting with 2.15.0 the test-case succeeds.
Thanks!
(Also thanks for the fast
ams-tschoening commented on a change in pull request #92:
URL: https://github.com/apache/logging-log4cxx/pull/92#discussion_r776230335
##
File path: src/test/cpp/throughput/throughput-main.cpp
##
@@ -71,14 +74,14 @@ static void benchmark_conversion_pattern( std::string name,
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17466366#comment-17466366
]
Marco Tenti commented on LOG4J2-3254:
-
The error persist on version 2.17.0 and 2.17.1.
{code:java}
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tenti updated LOG4J2-3254:
Affects Version/s: 2.17.0
2.17.1
> Need a log4j-core version 2.16 osgi
58 matches
Mail list logo
