No, what's unfortunate is that you didn't bother reading my strikeback white-paper before writing your SF piece... Just like you didn't bother reading any of the book before posting this response. My strikeback concept and code for the associated neutralizing agents were *never* self propagating or worm-like, yet you go out of your way to make it seem like they were... Not only is guidance offered, but a framework proposed that specifically addresses the questions of when, where, and how to strikeback, yet you say I offer "no boundaries of acceptable behavior" in your response piece. What is really frustrating is that these questions were answered before you even asked them, and that the white paper, its references, and my articles were all available at the time of your column, yet you didn't even bother reading them, or you would have known that. I also take it that you were not on hand for the BH conference you reference, as I went over it there as well... The white-paper and original articles are also in the book.
About the only thing I agree with in your SF guest feature is that a security professional must have integrity. To me, integrity includes due diligence in researching subject matter before one purports to be an authority on it, particularly when you endeavor to be a critic.
Timothy Mullen
Slashdot Mirror
No, what's unfortunate is that you didn't bother reading my strikeback white-paper before writing your SF piece... Just like you didn't bother reading any of the book before posting this response. My strikeback concept and code for the associated neutralizing agents were *never* self propagating or worm-like, yet you go out of your way to make it seem like they were... Not only is guidance offered, but a framework proposed that specifically addresses the questions of when, where, and how to strikeback, yet you say I offer "no boundaries of acceptable behavior" in your response piece. What is really frustrating is that these questions were answered before you even asked them, and that the white paper, its references, and my articles were all available at the time of your column, yet you didn't even bother reading them, or you would have known that. I also take it that you were not on hand for the BH conference you reference, as I went over it there as well... The white-paper and original articles are also in the book. About the only thing I agree with in your SF guest feature is that a security professional must have integrity. To me, integrity includes due diligence in researching subject matter before one purports to be an authority on it, particularly when you endeavor to be a critic. Timothy Mullen