[
https://issues.apache.org/jira/browse/DERBY-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157935#comment-14157935
]
ASF subversion and git services commented on DERBY-6635:
--------------------------------------------------------
Commit 1629192 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1629192 ]
DERBY-6635: Prevent the optimizerTracing optional tool from writing its output
over an existing file; commit derby-6635-01-ab-noOverwrite.diff.
> 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)
