You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/03/01 15:31:00 UTC

[jira] [Commented] (LOG4J2-2274) Allow EnvironmentPropertySource to run with a SecurityManager that rejects environment variable access

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

ASF subversion and git services commented on LOG4J2-2274:
---------------------------------------------------------

Commit e21d127c6a684ba05da7fa2500c733867285a59d in logging-log4j2's branch refs/heads/release-2.x from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e21d127 ]

[LOG4J2-2274] Allow EnvironmentPropertySource to run with a
SecurityManager that rejects environment variable access.

> Allow EnvironmentPropertySource to run with a SecurityManager that rejects environment variable access
> ------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-2274
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2274
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.10.0
>            Reporter: Sebastien Lannez
>            Assignee: Gary Gregory
>            Priority: Major
>             Fix For: 2.11.0
>
>         Attachments: EnvironmentPropertySource.java, TestSecManager.java
>
>
> Please find attached to this email a code change proposal for the EnvironmentPropertySource so it does not  fail when used in conjonction with highly restrictive security restriction managers.
> I propose to surround with a try..catch the retrieval of environment variables so the library does not fail to initialize when it runs in the context of a security manager that always issues Exception when security rules are violated.
> see attachment for proposal.
> Avoids:
> {noformat}
> java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.util.PropertiesUtil
>     at org.apache.logging.log4j.status.StatusLogger.<clinit>(StatusLogger.java:78)
>     at org.apache.logging.log4j.core.AbstractLifeCycle.<clinit>(AbstractLifeCycle.java:38)
>     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>     at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>     at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:172)
>     at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:161)
>     at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:1)
>     at org.apache.logging.log4j.util.EnvironmentPropertySourceSecurityManagerTest.test(EnvironmentPropertySourceSecurityManagerTest.java:55)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)