db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6680) Other jar files may need to be granted permission to read derby.ui.* properties
Date Tue, 19 Aug 2014 20:07:18 GMT

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

Dag H. Wanvik resolved DERBY-6680.
----------------------------------

          Resolution: Fixed
       Fix Version/s: 10.12.0.0
    Issue & fix info: Known fix  (was: Known fix,Patch Available)

Resolving. Will backport to 10.11 though.

> 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.12.0.0
>
>         Attachments: 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)

Mime
View raw message