[ https://issues.apache.org/jira/browse/DERBY-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910730#comment-13910730 ]
Daniel Stocker commented on DERBY-6438: --------------------------------------- Legend! Cheers Rick, much appreciated, all sorted, easy as that :) > Explicitly grant SocketPermission "listen" in default server policy > ------------------------------------------------------------------- > > Key: DERBY-6438 > URL: https://issues.apache.org/jira/browse/DERBY-6438 > Project: Derby > Issue Type: Improvement > Components: Network Server > Affects Versions: 10.11.0.0 > Reporter: Knut Anders Hatlen > Assignee: Knut Anders Hatlen > Fix For: 10.5.3.2, 10.6.2.4, 10.7.1.4, 10.8.3.3, 10.9.2.2, > 10.10.1.4, 10.11.0.0 > > Attachments: 1010_server.policy, 1010_server.policy, > 1010_server.policy, 1010_server.policy, d6438-1a.diff, releaseNote.html, > releaseNote.html > > > 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. -- This message was sent by Atlassian JIRA (v6.1.5#6160)