This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected Fedora versions. For comments that are specific to the vulnerability please use bugs filed against "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please include the bug IDs of the respective parent bugs filed against the "Security Response" product. Please mention CVE ids in the RPM changelog when available. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=742644 Please note: this issue affects multiple supported versions of Fedora EPEL. Only one tracking bug has been filed; please only close it when all affected versions are fixed. [bug automatically created by: add-tracking-bugs]
Adding parent bug CVE-2011-3869 New bodhi update url: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=742644,742645
Adding parent bug CVE-2011-3871 New bodhi update url: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=742644,742645,742649
Adding parent bug CVE-2011-3848 New bodhi update url: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=742644,742645,742649,742174
Since updates were already submitted to bodhi (and in the case of EPEL, pushed to testing), what's the preferred method forward here (for both Fedora and EPEL)?
I should have included the bodhi links: https://admin.fedoraproject.org/updates/puppet-2.6.6-3.el5 https://admin.fedoraproject.org/updates/puppet-2.6.6-3.el6 https://admin.fedoraproject.org/updates/puppet-2.6.6-3.fc14 https://admin.fedoraproject.org/updates/puppet-2.6.6-3.fc15 https://admin.fedoraproject.org/updates/puppet-2.6.6-3.fc16
If the bugs are linked, then bodhi should close the tracking bugs once they're pushed to stable. I don't see any bugs linked, so that may not be the case. When the bugs get pushed to stable, if these trackers aren't closed automatically, feel free to close them. Thanks.
Will do. There aren't any links because the updates were pushed before these tracker bugs were created¹. :) ¹ Other than for EL-4, which I neglected to take care of until yesterday. Poor old EL-4.
This has been fixed in EPEL 5 and 6 with build 2.6.12-1