[
https://issues.apache.org/jira/browse/LOG4J2-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-350.
---------------------------------
Resolution: Won't Fix
As per the reply to the similar request for HttpClient [1]
'Trusted-Library' attribute is Applet runtime specific attribute. We do not
distribute signed version of the HttpClient jars and therefore are not in a
position to declare the library trusted. This is a responsibility of those who
package and sign HttpClient jars as a part of an Applet distribution.
Same goes for RIA environments and the 'Permissions' attribute. Without
specifying a 'Codebase' we are not in a position to set permission level to
'all-permissions'
[1] https://issues.apache.org/jira/browse/HTTPCLIENT-1386
> New attributes to be added in Log4j manifest
> --------------------------------------------
>
> Key: LOG4J2-350
> URL: https://issues.apache.org/jira/browse/LOG4J2-350
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Himanshu Gusain
>
> We are using log4j jar by apache.
> But, due to new java 7 releases by oracle our applet starts throwing the new
> prompts they introduced for mixed code in their java 7 update 21 release.
> Now to remove these prompts I have to add the Trusted-Library: true attribute
> into the Manifest.mf of all the jars we are using.
> We also want to add the attribute Permissions: all-permissions to the
> manifest of the log4j jar as per java 7 update 25.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
