I corrected an error in a fix posted to bugtraq yesterday, guy used && when he meant to use ||… The advisory can be found here (with no mention of my contribution, I might add):