db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6598) Document permissions recommendations for JAR procedures
Date Thu, 05 Jun 2014 11:25:01 GMT

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

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

Thanks for the patch, Kim. I'd probably not mention it in the REMOVE_JAR topic. At least it
shouldn't say that the procedure can be used to install code, since it does the exact opposite.
Apart from that, all the changes look good to me.

> Document permissions recommendations for JAR procedures
> -------------------------------------------------------
>
>                 Key: DERBY-6598
>                 URL: https://issues.apache.org/jira/browse/DERBY-6598
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: DERBY-6598.diff, DERBY-6598.stat, DERBY-6598.zip
>
>
> It's been recommended that we should make the documentation of the SQLJ.INSTALL_JAR procedure
(and SQLJ.REPLACE_JAR) state more explicitly that the privilege should only be granted to
trusted users. For example:
> "Since this procedure can be used to install arbitrary code that runs in the same Java
Virtual Machine as the Derby database engine, the execution privilege should only be granted
to trusted users."
> This needs to go into the Reference Manual topics on these procedures as well as other
locations where they are discussed.



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

Mime
View raw message