This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora EPEL. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs]
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1440912,1441407 # Description of your update notes=Security fix for # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
If the Fedora bug was closed, shouldn't the EPEL bug be closed as well? I understand that the issue wasn't actually fixed in 2.3, but EPEL and Fedora have the same version of Ansible (or will after everything makes it to stable). Plus Ansible upstream doesn't view this as a bug as Ansible in any case.
Yes. It was just missed it looks like. Closing the same as the fedora version of this: "Discussed this last week with btarasso. Couple things I should mention: * The change in ansible-2.3.0.0 was not to address this (task-level no_log) but module parameters which are labelled no_log in the module's file. * We don't consider this a bug in Ansible but rather, in any callback which is recording the sensitive data. I've recorded our thinking in the CVE bug: https://bugzilla.redhat.com/show_bug.cgi?id=1440912#c22 Since we don't consider this a bug upstream, I think this bug could stay closed but I don't know how the security team wants to track it."