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

Posted to commits@santuario.apache.org by "Chris Moos (JIRA)" <ji...@apache.org> on 2015/01/23 21:40:35 UTC

[jira] [Updated] (SANTUARIO-413) Decrypted content should not be logged

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

Chris Moos updated SANTUARIO-413:
---------------------------------
    Attachment: remove-decrypted-content-logging.patch

> 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)