logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1560) Log4j can lose exceptions when a security manager is present
Date Fri, 07 Oct 2016 15:07:21 GMT

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

Remko Popma commented on LOG4J2-1560:

Mikael, Simon, looks like only the patches for LOG4J2-1563 were included in the 2.7 release.
(The title for that issues is the same as this one, I did not follow this closely enough to
notice that this ticket had a separate patch attached.)

2.7 was just released. The attached patch will be included in a subsequent 2.7.1 release.

> 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-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 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