db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-6438) Explicitly grant SocketPermission "listen" in default server policy
Date Thu, 19 Dec 2013 10:52:08 GMT
Knut Anders Hatlen created DERBY-6438:

             Summary: 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:
            Reporter: Knut Anders Hatlen
            Assignee: Knut Anders Hatlen

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

The default policy should make this permission explicit.

This message was sent by Atlassian JIRA

View raw message