You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2015/01/26 12:16:34 UTC
[jira] [Commented] (SANTUARIO-413) Decrypted content should not be
logged
[ https://issues.apache.org/jira/browse/SANTUARIO-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291705#comment-14291705 ]
Colm O hEigeartaigh commented on SANTUARIO-413:
-----------------------------------------------
I tend to disagree - I've used the ability to see decrypted data in the logs numerous times when debugging issues with XML Security.
Colm.
> Decrypted content should not be logged
> --------------------------------------
>
> Key: SANTUARIO-413
> URL: https://issues.apache.org/jira/browse/SANTUARIO-413
> Project: Santuario
> Issue Type: Bug
> Affects Versions: Java 2.0.3
> Reporter: Chris Moos
> Assignee: Colm O hEigeartaigh
> Priority: Minor
> Attachments: remove-decrypted-content-logging.patch
>
>
> In XMLCipher the decrypted contents are logged if debug logging is enabled. This means that if someone can modify the logging levels the logs will contain decrypted data. I don't think there is any reason to include the decrypted content in the logs.
> Patch is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)