logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Tedor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1820) Log4j 2.8 can lose exceptions when a security manager is present
Date Thu, 02 Mar 2017 15:34:45 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892426#comment-15892426

Jason Tedor commented on LOG4J2-1820:

Thank you for providing all of this information [~jvz]. I hope this helps address this problem
in the future. I have just one comment: it is fine to use {{git am}} on a patch file like
I supplied here, the output of {{git format-patch}} is fully compatible with {{git am}}.

> Log4j 2.8 can lose exceptions when a security manager is present
> ----------------------------------------------------------------
>                 Key: LOG4J2-1820
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1820
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.8
>            Reporter: Jason Tedor
>            Assignee: Gary Gregory
>             Fix For: 2.8.2
>         Attachments: 0001-Handle-security-exception-on-getting-class-loader.patch, 0002-Handle-security-exception-on-getting-class-loader.patch
> When Log4j is rendering an exception, it can attempt to access a class loader that it
does not have permissions to access when a security manager is present.
> I have a patch and a failing test case for this; I will submit it shortly.
> This is similar to LOG4J2-1560.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message