[DERBY-2883] template security policy file for network server uses undefined property derby.security.host

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.3.1.4, 10.4.1.3
• Component/s: Network Server
• Labels: derby_triage10_5_2 derby_triage10_9
• Urgency: Normal
• Issue & fix info: Newcomer
• Bug behavior facts: Security
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 29/Jun/07 15:38
• Updated: 21/Feb/12 00:28

Description

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.