Bug 649915
| Summary: | protect cumin password wherever it lives | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Pete MacKinnon <pmackinn> |
| Component: | cumin | Assignee: | Justin Ross <jross> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Sarenik <jsarenik> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | beta | CC: | jneedle, jsarenik, matt, tross |
| Target Milestone: | 1.3.0.1 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The cumin user (i.e. the cumin-data client and the cumin-web QMF client) needs to be authenticated to the broker. Previously, if the password for the authentication was stored in plain text in a file (e.g. cumin.conf), that file did not have appropriate permissions so that the password could be readable by the cumin user only. With this update, the ownership of files in /etc/cumin changed to cumin.cumin with 0600 permissions, thus, ensuring the safety of the stored password.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-11-30 17:50:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pete MacKinnon
2010-11-04 19:43:56 UTC
Resolved in cumin 0.1.4410-2.
Ownership of files in /etc/cumin changed to cumin.cumin with permissions 0600.
%attr(600,cumin,cumin) %config(noreplace) %{cumin_etc}/cumin.conf
%attr(600,cumin,cumin) %config(noreplace) %{cumin_etc}/cumin.crt
%attr(600,cumin,cumin) %config(noreplace) %{cumin_etc}/cumin.key
Sooo...the password field will be stored in cumin.conf? Do we need a separate BZ for that change? It works even after an update from MRG 1.3's cumin. ~# cd /etc/cumin/ cumin# ls -lZ -rw------- cumin cumin system_u:object_r:etc_t cumin.conf -rw------- cumin cumin system_u:object_r:etc_t cumin.crt -rw------- cumin cumin system_u:object_r:etc_t cumin.key cumin# rpm -q cumin cumin-0.1.4410-2.el5 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0921.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
The cumin user (i.e. the cumin-data client and the cumin-web QMF client) needs to be authenticated to the broker. Previously, if the password for the authentication was stored in plain text in a file (e.g. cumin.conf), that file did not have appropriate permissions so that the password could be readable by the cumin user only. With this update, the ownership of files in /etc/cumin changed to cumin.cumin with 0600 permissions, thus, ensuring the safety of the stored password.
|