db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6635) OptimizerTracer.unloadTool() could be used to write garbage over Derby data files.
Date Fri, 03 Oct 2014 12:31:33 GMT

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

Rick Hillegas updated DERBY-6635:
---------------------------------
    Attachment: derby-6635-01-ab-noOverwrite.diff

Attaching derby-6635-01-ab-noOverwrite.diff. Tests passed cleanly on the previous rev of the
patch except for an error caused by the canonized old text of the message which has changed
(DATA_FILE_EXISTS). This new rev of the patch adjusts the stale canon.

Touches the following additional file:

M       java/testing/org/apache/derbyTesting/functionTests/master/importExportIJ.out


> OptimizerTracer.unloadTool() could be used to write garbage over Derby data files.
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-6635
>                 URL: https://issues.apache.org/jira/browse/DERBY-6635
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.11.1.1
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6635-01-aa-noOverwrite.diff, derby-6635-01-ab-noOverwrite.diff
>
>
> I don't see any checks in place to prevent this method from writing its output file into
the log or sego directories or even over service.properties. Fortunately, only the DBO can
run this procedure by default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message