Comment 11 for bug 1989008

Per the OpenStack VMT's report taxonomy, we should make this public unless there is the likelihood of identifying a fix which can be backported safely to all supported stable branches (before the 90-day embargo expires on 2022-12-06):

https://security.openstack.org/vmt-process.html#report-taxonomy

It does not sound like this is a probable outcome, so unless someone disagrees by the end of this week (2022-09-30), I'll go ahead and switch the report to the Public Security type (class B1 "can only be fixed in master"), after which time it will be allowable to refer to it in public discussions in order to better drive completion of the privsep migration among affected projects.