[
https://issues.apache.org/jira/browse/DERBY-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466095
]
Rick Hillegas commented on DERBY-2250:
--------------------------------------
Thanks again for the quick feedback, Dan.
You are right, I modelled SYSFILEPERMS on SYSROUTINEPERMS. That is how I ended
up with the odd primary key. I'm happy with the changes you recommend.
I think that JAR and USAGE can be non-reserved keywords and I agree that that
will make upgrade simpler.
Thanks also for catching my cut-and-paste errors.
I will make the verbiage around the USAGE requirement consistent.
> Implement USAGE privilege for Jar files
> ---------------------------------------
>
> Key: DERBY-2250
> URL: https://issues.apache.org/jira/browse/DERBY-2250
> Project: Derby
> Issue Type: New Feature
> Components: Security, SQL
> Reporter: Rick Hillegas
> Fix For: 10.3.0.0
>
> Attachments: jarUsage.html
>
>
> Implement the USAGE privilege for jar files and require this privilege on
> jars wired into the derby.database.classpath. These are the first two tasks
> in the closing "Improving Java Routine Security in 10.3 onwards" section of
> the wiki page on Java routine security:
> http://wiki.apache.org/db-derby/JavaRoutineSecurity
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
