Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 9 Jan 2014 12:50:57 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12685558.1387450287978.68350.1389271857037@arcas>
In-Reply-To: <JIRA.12685558.1387450287978@arcas>
References: <JIRA.12685558.1387450287978@arcas>
Subject: [jira] [Commented] (DERBY-6438) Explicitly grant SocketPermission
 "listen" in default server policy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866612#comment-13866612 ] 

Knut Anders Hatlen commented on DERBY-6438:
-------------------------------------------

Thanks for backporting the fix, Myrna. I got a request for this fix on 10.6, so I did that backport myself (it merged cleanly from 10.7).

Are you planning to backport it any further? If not, I'll mark the issue as resolved.

> 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.11.0.0
>
>         Attachments: d6438-1a.diff
>
>
> 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)