Bug#851619: new upstream release fixes a bag of CVEs

Hi, On Mon, Jan 16, 2017 at 10:43:05PM +0100, Toni Mueller wrote: > there is a new Ansible release, 2.2.1, which was published on 2017-01-11 > on releases.ansible.com, which fixes a bag of security holes, for which > CVEs should already exist. Please take a look at sorry, MY BAD. The final

Bug#851619: new upstream release fixes a bag of CVEs

Hi Harlan, On Mon, Jan 16, 2017 at 05:06:36PM -0500, Harlan Lieberman-Berg wrote: > Happy to report that these have already been fixed through cherry-picks > over the last five days or so. 2.2.1 has no security fixes not present > in 2.2.0.0-4. oh, great. I almost expected as much, but wanted

Bug#851619: new upstream release fixes a bag of CVEs

package ansible tag 851619 -security -upstream severity 851619 wishlist retitle 851619 New ansible upstream version thanks Toni Mueller writes: > there is a new Ansible release, 2.2.1, which was published on 2017-01-11 > on releases.ansible.com, which fixes a bag of security

Bug#851619: new upstream release fixes a bag of CVEs

Package: ansible Version: 2.2.0.0-1 Severity: grave Tags: security upstream Hi, there is a new Ansible release, 2.2.1, which was published on 2017-01-11 on releases.ansible.com, which fixes a bag of security holes, for which CVEs should already exist. Please take a look at