[ https://issues.apache.org/jira/browse/LOG4NET-586 ]
Davyd McColl deleted comment on LOG4NET-586:
--
was (Author: davydm):
I'm looking into this as part of another investigation. There are some options
here, but none of them produce exactly the
[
https://issues.apache.org/jira/browse/LOG4NET-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480880#comment-17480880
]
Davyd McColl commented on LOG4NET-586:
--
I'm looking into this as part of another in
[
https://issues.apache.org/jira/browse/LOG4NET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480868#comment-17480868
]
Andrea commented on LOG4NET-683:
Hi [~santjo]
yes, looking at the code it looks like t
[
https://issues.apache.org/jira/browse/LOG4NET-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480857#comment-17480857
]
Davyd McColl commented on LOG4NET-672:
--
I've started to look into this - I first wa
[
https://issues.apache.org/jira/browse/LOG4J2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Duft closed LOG4J2-3358.
---
Took the time to do it as fast as you responded xD Closing since JsonLayout it
back to working perfectl
[
https://issues.apache.org/jira/browse/LOG4J2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480847#comment-17480847
]
Markus Duft commented on LOG4J2-3358:
-
Thanks for the very quick response, very much
swebb2066 merged pull request #105:
URL: https://github.com/apache/logging-log4cxx/pull/105
--
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: notifi
srdo commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-1019592372
> Setting a depth limit of something like 10 would still be vulnerable to
billion-laughs style attacks
Good point. I guess in order to prevent such an attack, you would
jvz commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-1019582347
I'm leaning toward closing this for a couple reasons:
* Setting a depth limit of something like 10 would still be vulnerable to
billion-laughs style attacks.
* The is
[
https://issues.apache.org/jira/browse/LOG4J2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480702#comment-17480702
]
Ralph Goers commented on LOG4J2-3359:
-
This builder is doing the wrong thing when pr
[
https://issues.apache.org/jira/browse/LOG4NET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480699#comment-17480699
]
Stojan Andjelkovic commented on LOG4NET-683:
hi [~agalbiati],
you are maybe
BUILD SUCCESS
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/805/
Project:
release-2.x
Date of build:
Sun, 23 Jan 2022 13:04:11 +
Build duration:
1 hr 7 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s), Pa
[
https://issues.apache.org/jira/browse/LOG4NET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480633#comment-17480633
]
Andrea commented on LOG4NET-683:
Hi,
to me this is related to LOG4NET-586
Cheers
A
13 matches
Mail list logo
