Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 21 Aug 2014 22:04:11 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12730790.1406726187868.6580.1408658651399@arcas>
In-Reply-To: <JIRA.12730790.1406726187868@arcas>
References: <JIRA.12730790.1406726187868@arcas>
Subject: [jira] [Updated] (DERBY-6680) Other jar files may need to be
 granted permission to read derby.ui.* properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-6680:
---------------------------------

    Attachment: derby-6680-2.diff

Uploading [erby-6680-2.diff].

This patch moves the reading of the two system properties up into NetworkServerControlImpl. Other usage of LocalizedResource is unaffected and might still try to read those system properties, i.e. as called from ij.

Removes the note about LocalizedResource in the policy template file.


> Other jar files may need to be granted permission to read derby.ui.* properties
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-6680
>                 URL: https://issues.apache.org/jira/browse/DERBY-6680
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.11.1.1
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>             Fix For: 10.11.1.2, 10.12.0.0
>
>         Attachments: derby-6680-2.diff, derby-6680.diff, derby-6680b.diff
>
>
> The following properties may be read by LocalizedResource, a class which is included in derby.jar, derbynet.jar, derbyclient.jar, and derbytools.jar:
> {noformat}
> derby.ui.codeset
> derby.ui.locale
> {noformat}
> A user has tripped across this problem in production. With the user's language settings, the network server fails to come up because the server policy file does not grant the server permission to read these properties. See http://apache-database.10148.n7.nabble.com/Hellow-I-have-some-problem-in-customize-security-policy-with-derby-modified-3-td141002.html
> We should adjust server.policy and template.policy accordingly.


--
This message was sent by Atlassian JIRA
(v6.2#6252)