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

Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/07/19 20:48:49 UTC

[jira] [Commented] (CLOUDSTACK-3274) API Refactoring: secretkey and accesskey of the backing store is found in plaintext in the logs

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713932#comment-13713932 ] 

Animesh Chaturvedi commented on CLOUDSTACK-3274:
------------------------------------------------

Not related to object_store updating the summary
                
> API Refactoring: secretkey and accesskey of the backing store is found in plaintext in the logs
> -----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3274
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3274
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Storage Controller
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Assignee: Min Chen
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Should we be printing the s3 store credentials in the logs in plaintext? Can it be sanitized?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira