[
https://issues.apache.org/jira/browse/ACCUMULO-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977008#comment-13977008
]
Christopher Tubbs commented on ACCUMULO-2713:
---------------------------------------------
Re: the patch, sensitive properties are labeled with an annotation. It'd be
best to remove any instance properties with that @Sensitive annotation, rather
than just a specific known one, to prevent regression. However, I'm having a
difficult time understanding why CryptoModuleParameters includes instance
properties in the first place. Perhaps they can just be removed entirely. I
can't find where they would be used. Can anybody help me out here?
> Instance secret written out with other configuration items to RFiles and
> WALogs when encryption is turned on
> ------------------------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-2713
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2713
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.5.1
> Reporter: Michael Allen
> Assignee: John Vines
> Priority: Blocker
> Labels: WAL, encryption, rfile
> Fix For: 1.6.0
>
> Attachments: Dont-write-instance-secret-to-RFiles.patch
>
>
> The encryption at rest feature records configuration information in order to
> encrypted RFiles and WALogs so that if the configuration changes, the files
> can be read back. The code that does this recording hovers up all the
> "instance.*" entries, and does not pick out the instance.secret as a special
> one not to write. Thus the instance secret goes into each file in the clear,
> which is non-ideal to say the least.
> Patch forthcoming.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
