[
https://issues.apache.org/jira/browse/LOG4J2-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491432#comment-15491432
]
Jason Tedor commented on LOG4J2-1563:
-------------------------------------
Heya [~garydgregory], I'm confused about the contribution process here? I
supplied a patch with an elaborate commit message but I see the commit in the
logs does not have my commit message nor authorship? What am I missing here?
{code}
commit b7b30013e84e8be2b6bbc8326e9bc2ff27e239f1
Author: Gary Gregory <ggreg...@apache.org>
AuthorDate: Tue Sep 6 22:21:37 2016 -0400
Commit: Gary Gregory <ggreg...@apache.org>
CommitDate: Tue Sep 6 22:21:37 2016 -0400
[LOG4J2-1563] Log4j 2.6.2 can lose exceptions when a security manager is
present.
{code}
> 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-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
