| Summary: | imagefactory.log permissions are too open by default | ||
|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Brad P. Crochet <brad> |
| Component: | imagefactory | Assignee: | Steve Loranz <sloranz> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Kočí <mkoci> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.0.0 | CC: | akarol, brad, dajohnso, deltacloud-maint, dgao, hbrock, imcleod, nobody, sloranz, ssachdev, whayutin |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-15 20:22:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Brad P. Crochet
2012-02-22 20:34:15 UTC
Two questions: 1. What sensitive information does the image factory log contain? 2. What sets the perms on the log, factory or configure? We've made several changes to avoid having passwords in the log. Beyond that, I don't know what would be in it that is worth protecting. Commit pulled into release branch as: https://github.com/aeolusproject/imagefactory/commit/0115e304e28ac1a9cb0e8d1c59c250c13227e081 Brewed as 1.0.0rc7 [root@dell-per805-01 log]# ls -l imagefactory.log -rw-------. 1 root root 23865 Feb 27 04:41 imagefactory.log Verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-36.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-conductor-daemons-0.8.0-36.el6.noarch aeolus-configure-2.5.0-15.el6.noarch rubygem-aeolus-image-0.3.0-10.el6.noarch aeolus-all-0.8.0-36.el6.noarch aeolus-conductor-doc-0.8.0-36.el6.noarch Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0588.html |