Comment 8 for bug 1430645

The discussion in https://review.openstack.org/134347 is sort of skirting this vulnerability, just need to remain careful to keep it under wraps until we settle on a disclosure date. I recommend subscribing Thiago to this bug report so that we're all on the same page.

Assuming this is something that the Swift developers want fixed for currently supported stable branches, we'll need some sort of backports conforming to our stable branch maintenance requirements. If this ends up only being fixed in the master branch instead then we would forgo any advisory and just switch the bug to public once the determination is made.