So is this now fixed by John's patch? If so, but followon work is needed to remove a dangerous API let's turn that into a separate bug.
Is this still critical and still needed for 2.0?
So is this now fixed by John's patch? If so, but followon work is needed to remove a dangerous API let's turn that into a separate bug.
Is this still critical and still needed for 2.0?