Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 3 Nov 2016 10:44:58 +0000 (UTC)
From: "Semen Boikov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13017585.1478169894000.171189.1478169898366@Atlassian.JIRA>
In-Reply-To: <JIRA.13017585.1478169894000@Atlassian.JIRA>
References: <JIRA.13017585.1478169894000@Atlassian.JIRA> <JIRA.13017585.1478169894184@arcas>
Subject: [jira] [Created] (IGNITE-4167) Add an option to avoid printing out
 sensitive data into logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 03 Nov 2016 10:45:00 -0000

Semen Boikov created IGNITE-4167:
------------------------------------

             Summary: Add an option to avoid printing out sensitive data in=
to logs
                 Key: IGNITE-4167
                 URL: https://issues.apache.org/jira/browse/IGNITE-4167
             Project: Ignite
          Issue Type: Improvement
            Reporter: Denis Kholodov


  =20
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.=C2=A0To this en=
d, we need a configuration option (turned OFF by default) that allows keys/=
values to be written to log messages.


=20


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