On 18/11/2013 12:45, Konstantin Kolinko wrote:
> 2013/11/18  <[email protected]>:
>> Author: markt
>> Date: Mon Nov 18 09:02:13 2013
>> New Revision: 1542952
>>
>> URL: http://svn.apache.org/r1542952
>> Log:
>> Update comments. No JNDI permission is granted now JNDI is not used to 
>> access files.
>>
> 
> Are we ready to remove the JndiPermission class itself? I think that we are.

I think so to. I'm currently looking at WebappLoader.setPermissions()
which is going to need some work so no objections from me to removing
JndiPermission if you want to scratch that itch.

Mark

> 
> Note that it is referenced in several places, such as build.xml and
> documentation.
> 
> 
>> Modified:
>>     tomcat/trunk/conf/catalina.policy
>>
>> Modified: tomcat/trunk/conf/catalina.policy
>> URL: 
>> http://svn.apache.org/viewvc/tomcat/trunk/conf/catalina.policy?rev=1542952&r1=1542951&r2=1542952&view=diff
>> ==============================================================================
>> --- tomcat/trunk/conf/catalina.policy (original)
>> +++ tomcat/trunk/conf/catalina.policy Mon Nov 18 09:02:13 2013
>> @@ -127,7 +127,7 @@ grant codeBase "file:${catalina.home}/li
>>
>>  // These permissions are granted by default to all web applications
>>  // In addition, a web application will be given a read FilePermission
>> -// and JndiPermission for all files and directories in its document root.
>> +// for all files and directories in its document root.
>>  grant {
>>      // Required for JNDI lookup of named JDBC DataSource's and
>>      // javamail named MimePart DataSource used to send mail
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to