cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3274) API Refactoring: secretkey and accesskey of the backing store is found in plaintext in the logs
Date Wed, 07 Aug 2013 18:47:21 GMT

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

Animesh Chaturvedi updated CLOUDSTACK-3274:
-------------------------------------------


These blockers and critical issues are resolved but not verified. Reporters of these issues
please verify the fixes and help close these issues
                
> 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

Mime
View raw message