[DERBY-6438] Explicitly grant SocketPermission "listen" in default server policy

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.3.3.1, 10.4.2.1, 10.5.3.2, 10.6.2.4, 10.7.1.4, 10.8.3.3, 10.9.2.2, 10.10.2.0, 10.11.1.1
• Component/s: Network Server
• Urgency: Normal
• Issue & fix info: Release Note Needed
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 19/Dec/13 10:51
• Updated: 21/Jan/15 00:23
• Resolved: 19/May/14 16:53

Description

The network server needs SocketPermission "listen" on the port that it listens to, but this permission is not granted by the basic server policy that's installed by default. This doesn't cause any problems in most cases, since the JVM's default policy grants all code bases SocketPermission "listen" on a range of ports, and Derby's network server port is within that range.

Still, the network server should not rely on this fact. It is possible to run the network server on any port, not only those ports that happen be in the range that's given carte blanche by the platform's default policy. The network server will however not be able to run on those ports with the basic policy currently, only with a custom policy or with the security manager disabled.

The default policy should make this permission explicit.

Sub-Tasks

• Document new SocketPermission in Network Server policy file: Closed