Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6438

Explicitly grant SocketPermission "listen" in default server policy

    Details

    • Urgency:
      Normal
    • Issue & fix info:
      Release Note Needed

      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.

        Attachments

        1. 1010_server.policy
          10 kB
          Rick Hillegas
        2. 1010_server.policy
          10 kB
          Rick Hillegas
        3. 1010_server.policy
          10 kB
          Rick Hillegas
        4. 1010_server.policy
          10 kB
          Myrna van Lunteren
        5. d6438-1a.diff
          23 kB
          Knut Anders Hatlen
        6. releaseNote.html
          8 kB
          Knut Anders Hatlen
        7. releaseNote.html
          8 kB
          Myrna van Lunteren

          Activity

            People

            • Assignee:
              knutanders Knut Anders Hatlen
              Reporter:
              knutanders Knut Anders Hatlen
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: