Originally posted here by TechieChick
[B]Testing a system that is not only not yours, but where you have not been asked to do such testing is only asking for problems. People are hyper sensitive to this right now and don't like any flaws in their systems being pointed out to them.

It's a very fine line between doing that and accidentally tripping across something
**********
Just my 2cents here, you have to do what you have to do...
Unless you are on a personal (or at least codial) basis with the SysOp is to print T.C.'s opening comment, post it somewhere easy to see, and consider the finer points of "problem ownership". If your online or desktop stuff is at risk, change servers, there's a jillion of them around and except for a very few most have holes somewhere. It would be very small satisfaction that a judge/jury found you innocent of all charges, after you paid some attorney a small fortune to defend you. "Problem Ownership", is a rather difficult concept for most of us to grasp who just like to help other people. T.C. is very correct, with the present atmosphere and the present laws, it would not be difficult for some SysOp with a hangover and a boss all over his a$$ on a monday morning to blame a "gooder" for all the problems that he had over the weekend. Just my 2cents worth, One of the AO'ers here has it for a signature and it's about as accurate as it is comical... "Paranoia isn't paranoia when you know they're actually after you!"