After looking at it more carefully, I'm not positive that it's a failure to check privileges, although the symptoms at the time made it look like that (literall

After looking at it more carefully, I'm not positive that it's a failure to check privileges, although the symptoms at the time made it look like that (literally logging an unprivileged process killing a privileged one). Rather, I think it's some sort of race. Anyway, I'm glad they fixed it now, but the response to our original bug submission didn't inspire a ton of confidence.