accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2938) Investigate logging on KeyExtent to ensure no data leakage
Date Mon, 23 Jun 2014 20:06:25 GMT


Sean Busbey commented on ACCUMULO-2938:

alternatively, provide a configurable toggle that makes sure the operator is aware of the
sensitivity. e.g. we could set a max log level that is allowed to have unmasked sensitive
things (default to NONE). Then an operator could up this to TRACE or DEBUG and configure their
logging mechanism to write those logs to a more protected space (like a disk volume with encryption
and rights restricting access).

> Investigate logging on KeyExtent to ensure no data leakage
> ----------------------------------------------------------
>                 Key: ACCUMULO-2938
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>            Reporter: Josh Elser
> The KeyExtent class identifies a Tablet in Accumulo. Of interest to this issue, KeyExtent
may contain the endRow of the Tablet and/or the endRow of the previous Tablet (or neither).
> If we log the extent, we have the potential to be leaking some data that might need to
be protected (visibilities, encryption) to a medium only protected by filesystem restrictions.
> This may be difficult since the extent is included in things like MinC and MajC log messages
and can be helpful when diagnosing problems on the system. Can we abstract away what might
be potentially sensitive data in some way that we still provide useful data for debugging

This message was sent by Atlassian JIRA

View raw message