[all][requirements][stable] requests version bump on stable brances {pike|queens} for CVE-2018-18074

Jesse Pretorius jesse at odyssey4.me
Thu May 9 12:38:29 UTC 2019

> On 9 May 2019, at 13:10, Thierry Carrez <thierry at openstack.org> wrote:
> I agree it is a bit of a slippery slope... We historically did not do that (stable branches are a convenience, not a product), because it is a lot of work to track and test vulnerable dependencies across multiple stable branches in a comprehensive manner.
> Why update requests 2.18.4 for CVE-2018-18074, and not Jinja2 2.10.0 for CVE-2019-8341 ?
> I'm not sure doing it on a case-by-case basis is a good idea either, as it might set unreasonable expectations.

A lot of operators make use of u-c for source-based builds to ensure consistency in the builds and to ensure that they’re using the same packages as those which were tested upstream. It makes sense to collaborate on something this important as far upstream as possible.

If we think of this as a community effort similar to the extended maintenance policy - the development community doesn’t *have* to implement the infrastructure to actively monitor for the vulnerabilities and respond to them. It can be maintained on a best effort basis by those interested in doing so.

To limit the effort involved we could agree to limit the scope to only allow changes to the current ‘maintained’ releases. For all other branches we can encourage an upgrade to a ‘maintained’ release by adding a release note.

To manage the 'unreasonable expectations’, we should document a policy to this effect.

More information about the openstack-discuss mailing list