You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Jason Tedor (JIRA)" <ji...@apache.org> on 2016/10/07 15:39:20 UTC
[jira] [Commented] (LOG4J2-1563) Log4j 2.6.2 can lose exceptions
when a security manager is present
[ https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555412#comment-15555412 ]
Jason Tedor commented on LOG4J2-1563:
-------------------------------------
I recognize that I'm an external contributor and my opinion caries very little weight here, but I really think open source projects like this one should be applying patches from external contributors directly keeping their name as the commit author and keeping their original commit message.
> Log4j 2.6.2 can lose exceptions when a security manager is present
> ------------------------------------------------------------------
>
> Key: LOG4J2-1563
> URL: https://issues.apache.org/jira/browse/LOG4J2-1563
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Reporter: Jason Tedor
> Assignee: Gary Gregory
> Fix For: 2.7
>
> Attachments: 0001-Unify-handling-of-throwables-when-loading-class.patch, 0002-Remove-policy-in-throwable-proxy-security-test.patch, throwable-proxy-security-exception-2.6.2.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 is the backport for LOG4J2-1560.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org