accumulo-notifications mailing list archives

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

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

Sean Busbey updated ACCUMULO-2938:
----------------------------------

    Priority: Critical  (was: Major)

increasing priority to Critical, because of potential for data leak

> Investigate logging on KeyExtent to ensure no data leakage
> ----------------------------------------------------------
>
>                 Key: ACCUMULO-2938
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2938
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>            Reporter: Josh Elser
>            Priority: Critical
>
> 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
purposes?



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

Mime
View raw message