db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2883) template security policy file for network server uses undefined property derby.security.host
Date Mon, 06 Jul 2009 18:33:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-2883:
---------------------------------

    Urgency: Normal

Triaged for 10.5.2: assigned normal urgency.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message