http://bugzilla.suse.com/show_bug.cgi?id=1109957
http://bugzilla.suse.com/show_bug.cgi?id=1109957#c1
Lars Vogdt changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lars.vogdt@suse.com,
| |maintenance@opensuse.org
Flags| |needinfo?(maintenance@opens
| |use.org)
--- Comment #1 from Lars Vogdt ---
Looks to me like the issue if fixed in latest ansible 2.7.8 (if you want, try
the package from the development repository in systemsmanagement).
@Maintenance: as there are a lot of other fixes included in the latest version,
I like to release the 2.7.8 one as maintenance update for
* openSUSE:Backports:SLE-12/ansible
* openSUSE:Backports:SLE-15:Update/ansible
* openSUSE:Leap:15.0:Update/ansible
* openSUSE:Leap:15.1:Update/ansible
* openSUSE:Leap:42.3:Update/ansible
if you agree.
There are some configuration settings, that are meanwhile marked as
"deprecated" and this will result in a warning message once the user executes
his ansible playbooks, but I assume that at least the following CVE (and other)
fixes are worth this small inconvenience:
* CVE-2018-16876
* CVE-2018-16859
* CVE-2018-10875
* CVE-2018-10855
--
You are receiving this mail because:
You are on the CC list for the bug.
