Issue #1871 has been updated by luke. Status changed from Re-opened to Ready for Checkin Assigned to set to jamtur01 Target version set to 0.24.8
Fixed, again. This time I used 'is_to_s' and 'should_to_s', so anyone who uses the API correctly should now never have the actual content. ---------------------------------------- Bug #1871: Sensitive information leaked in log reports http://projects.reductivelabs.com:80/issues/1871 Author: IanTurner Status: Ready for Checkin Priority: Normal Assigned to: jamtur01 Category: file Target version: 0.24.8 Complexity: Unknown Affected version: 0.24.7 Keywords: security content source logs It seems that at the moment, any files mastered through the "content" tag will sometimes have their contents reported through the various logging domains, either with a diff or with the complete file contents. This does not appear to happen with files mastered through the "source" tag. Since installed files may contain highly sensitive information, such as passwords, it should be possible to disable this behavior, either by a change for all users or through a configuration directive. ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
