[
https://issues.apache.org/jira/browse/DERBY-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-2883:
----------------------------------
Issue & fix info: Newcomer
Labels: derby_triage10_5_2 derby_triage10_9 (was:
derby_triage10_5_2)
Triage for 10.9. Mark as Newcomer. Good newcomer issue to learn a bit about
java 2 security.
> template security policy file for network server uses undefined property
> derby.security.host
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-2883
> URL: https://issues.apache.org/jira/browse/DERBY-2883
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.3.1.4, 10.4.1.3
> Reporter: Daniel John Debrunner
> Labels: derby_triage10_5_2, derby_triage10_9
>
> DERBY-2811 changed the use of
> permission java.net.SocketPermission "${derby.drda.host}:*", "accept";
> to
> permission java.net.SocketPermission "${derby.security.host}:*", "accept";
> I think this is correct for the default policy file used by the network
> server, but incorrect for the user template file.
> I think rather than exposing this "internal property" derby.security.host,
> the template should continue to use ${derby.drda.host}
> and include comments about needing to change it if the server is listening on
> a wildcard address. Currently there's no explanation of where
> derby.security.host comes from.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
