• TravisDBA (3/4/2013)


    Geoff A (3/4/2013)


    TravisDBA (3/4/2013)


    Geoff,

    Please be Be very careful about suggesting or even implying that people should do this on productiohn SQL Servers. i work for the government and the auditors are looking for this kind of stuff on your PC and if they find it, you are probably gone!!! I repeat: DO NOT KEEP THESE FILES ON YOUR WORK LAPTOP IF YOU WORK FOR THE GOVERNMENT, OR YOU ARE A GOVERNMENT CONTRACTOR!!!! You can not only be fired you can also be prosecuted.:-D

    Travis,

    i am not sure how i am resposible for goverment employees and their activities on their laptops.

    but if you saying i should be on the look out for black suits knocking on my door, I'll keep one eye open 😉

    Ok, no problem, just be careful suggesting that kind of thing to the public at large. Not everyone means well in this world. That is all I'm saying. I could see someone sitting in court and explaining "Well your honor, Geoff Albin showed me how to hack a SQL Login production password on SQLServerCentral.com!!!":-D

    On a personal system, there's no one to tell you, "No."

    For most corporations and government agencies, a password cracker is considered a hacking tool and the discovery of such on your system tends to lead to a career altering event. This is why, whenever I cover a tool like this, I make a point to issue that standard disclaimer. Keep in mind that even though you may have the purest of motives for having such a tool. However, unless you went and got prior permission from someone authorized to give it (usually this is a manager on the security or network/systems side, not the DBA or development manager), you're reason for having it is suspect.

    K. Brian Kelley
    @kbriankelley