Comment 6 for bug 1501206

I just received notification that bug #1498665 has been fixed. While I haven't yet confirmed that the fix is good myself, assuming that it is means that this bug now also applies generally to most IPv6 subnet with DHCP service (since IPv6 is generally be deployed using public addresses).

For the record I have no strong opinion about keeping the bug embargoed or not. I do agree with Mark that making it public is not likely to significantly increase the risk to OpenStack operators though, as folks looking for open resolvers will likely just scan the entire IPv4 address space rather than bothering to specifically target networks that are known to run OpenStack (or other vulnerable-by-default products).