[
https://issues.apache.org/jira/browse/DERBY-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648361#comment-13648361
]
Rick Hillegas commented on DERBY-6160:
--------------------------------------
Hi Dag,
I am leaning toward categorizing the file-visibility-control permissions as (i)
too. I would further clarify the definition of "mandatory" as "needed if there
is some environment in which Derby wouldn't run correctly without the
permission." Sort of analogous to the following permissions which are already
listed as "mandatory":
permission java.util.PropertyPermission "derby.*", "read"
permission java.util.PropertyPermission "derby.storage.jvmInstanceId",
"write"
Thanks.
> Fixes needed to documentation topics on security policy permissions
> -------------------------------------------------------------------
>
> Key: DERBY-6160
> URL: https://issues.apache.org/jira/browse/DERBY-6160
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.9.1.0, 10.10.1.1
> Reporter: Kathey Marsden
> Assignee: Kim Haase
> Attachments: DERBY-6160-2.diff, DERBY-6160-2.stat, DERBY-6160-2.zip,
> DERBY-6160.diff, DERBY-6160.stat, DERBY-6160.zip
>
>
> DERBY-5363 added a new required permission RuntimePermission
> "accessUserInformation".
> This should be added to the developer guide information under granting
> permissions to Derby.
> https://builds.apache.org/job/Derby-docs/lastSuccessfulBuild/artifact/trunk/out/devguide/cdevbabejgjd.html
> I am not sure of the context under which it is required if it is just needed.
--
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
