[
https://issues.apache.org/jira/browse/IGNITE-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024576#comment-16024576
]
ASF GitHub Bot commented on IGNITE-4496:
----------------------------------------
GitHub user akuramshingg opened a pull request:
https://github.com/apache/ignite/pull/2005
ignite-4496-1
IGNITE-4496 Review all logging for sensitive data leak
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4496-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2005.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2005
----
commit db02d5a0abb3b27d26f19b37daac0ad7d4cd7744
Author: Alexandr Kuramshin <[email protected]>
Date: 2017-05-25T11:05:40Z
IGNITE-4496 Review all logging for sensitive data leak
commit 281d5e8227fc360198d574211f6224db5d48a59d
Author: Alexandr Kuramshin <[email protected]>
Date: 2017-05-25T11:22:27Z
log.debug() fix
remove empty files
----
> Review all logging for sensitive data leak
> ------------------------------------------
>
> Key: IGNITE-4496
> URL: https://issues.apache.org/jira/browse/IGNITE-4496
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexandr Kuramshin
> Assignee: Alexandr Kuramshin
>
> While sensitive logging option added and toString() methods fixed, not all
> logging was checked for sensitive data leak
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
