Go directly to jail.
While searching for some information on the Microsoft Office Solution Accelerator for Sarbanes/Oxley I came across this little nugget on the GotDotNet workspace for SARBOX:
“I'm trying to bypass the Sarbanes/Oxley requirement of having a screensaver come up every 15 minutes (for my Operators).”
I really don't know what to say. I'm going to simply state the obvious by saying that the words “bypass”, “requirement”, and “Sarbanes/Oxley” should never appear in the same sentence. It's been a while since I have been this astounded by someone's blatant stupidity. Of course, I haven't been getting out much lately.
Given the level of ignorance this type of thing requires, I was ill-prepared for this helpful gem in the same thread:
“hey tektrader I don't know if you can create a screen saver and run it that way you can probably manipulate the settings of the one you don't have access to, anyway I am just trying to help, but check this code there are some parts where you can tweak the registry and probably that helps,, “
Again, I am stunned speechless. If the guy cannot disable the screensaver due to a policy restriction,
HE PROBABLY CAN'T EDIT THE F*CKING REGISTRY EITHER!! AND BESIDES THAT, YOU SHOULDN'T BE HELPING THIS MORON DO THIS.
<sigh>
Dave
Just because I can...(at least until some clown f*cks it all up for the rest of us)