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] [Updated] (DERBY-6680) Other jar files may need to be granted permission to read derby.ui.* properties
Date Fri, 22 Aug 2014 15:56:11 GMT

     [ 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-2b.diff

Thanks, Knut. I added (*) the reading of codeset of the instance you mentioned so the behavior
will be indentical. It does seem odd, though.. would one ever want to change the codeset when
the locale is the default "en"? Rerunning regressions with the version.

(*) [^derby-6680-2b.diff]

> 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:
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>             Fix For:,
>         Attachments: derby-6680-2.diff, derby-6680-2b.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

View raw message