Bug 695427

Summary: Add warning for cert. files with the same basename
Product: Red Hat Enterprise Linux 6 Reporter: James Antill <james.antill>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED ERRATA QA Contact: Karel Srot <ksrot>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: kdudka, ksrot, pknirsch, syeghiay, tcapek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, users were not notified that different certificate files with the same basename are treated as identical, which could lead to all sorts of problems. With this update, yum checks certificate files for such duplicates and displays an error message appropriately.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:34:22 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 James Antill 2011-04-11 17:29:31 UTC
Description of problem:

 This is due to the problems in curl/pycurl mentioned in 694294. We're just going to add a warning to yum, and something to the man page explaining it.
 This is needed for 6.1 due to rhsm.

Comment 1 James Antill 2011-04-11 18:41:26 UTC
Change is done, waiting for ACKs so I can build.

Comment 8 Tomas Capek 2011-05-17 11:57:31 UTC
    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:
Previously, users were not notified that different certificate files with the same basename are treated as identical, which could lead to all sorts of problems. With this update, yum checks certificate files for such duplicates and displays an error message appropriately.

Comment 9 errata-xmlrpc 2011-05-19 13:34:22 UTC
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/RHBA-2011-0602.html