[
https://issues.apache.org/jira/browse/LOG4J2-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463105#comment-15463105
]
Gary Gregory commented on LOG4J2-1560:
--------------------------------------
Go for it :-) I am travelling coast-to-coast today so I will not be able to
review until Monday or Tuesday but I welcome any release. I like RERO!
I have most of what I need for work in Git master. My focus this coming week
will be to hammer on everything related the Socket and Syslog appenders because
that what I selfishly need for my current gig. Even if 2.7 is out and I have
some changes in this area, that's OK with me.
[~jasonetedor]: if you want to grease the wheels for a possible 2.6.3, I'd
suggest you prepare a patch against the 2.6.2 tag and attach it to a new
ticket. If someone wants to volunteer for a 2.6.3, the initial leg-work will be
done, not by me ATM, but that would be a good exercise anyway.
Gary
> Log4j can lose exceptions when a security manager is present
> ------------------------------------------------------------
>
> Key: LOG4J2-1560
> URL: https://issues.apache.org/jira/browse/LOG4J2-1560
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Reporter: Jason Tedor
> Attachments: log4j-exception-logging-issue.tar.gz,
> throwable-proxy-security.exception.patch
>
>
> When Log4j is rendering an exception, it can attempt to load classes that it
> does not have permissions to load when a security manager is present.
> I have a patch and a failing test case for this; I will submit it shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
