You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexandr Kuramshin (JIRA)" <ji...@apache.org> on 2016/12/27 05:58:58 UTC

[jira] [Resolved] (IGNITE-4167) Add an option to avoid printing out sensitive data into logs

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

Alexandr Kuramshin resolved IGNITE-4167.
----------------------------------------
    Resolution: Fixed

Option added, toString() methods updated.
Basic key/value logging fixed (upon cache operations).

Some sensitive logging may still occur (rare), until all logging will be checked.

> Add an option to avoid printing out sensitive data into logs
> ------------------------------------------------------------
>
>                 Key: IGNITE-4167
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4167
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Denis Kholodov
>            Assignee: Alexandr Kuramshin
>
>    
> We are seeing sensitive cache data being output in ignite debug logging. I've tracked it down to at least two places:
> 1. GridToStringBuilder uses reflection to print all fields in cache objects that are not annotated with @GridToStringExclude
> 2. GridCacheMapEntry does a direct toString() call on the value objects in a debug log
> As a fabric platform, we won't always have control over the object classes being added to/retrieved from the cache.
> We must always assume that all keys and values are sensitive and should not be outputted in logs except in local debugging situations. To this end, we need a configuration option (turned OFF by default) that allows keys/values to be written to log messages.
>  



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