DES -- Implementation Issues (TripleDES, Key Replacement, Padding)

A Quick survey of major DES implementation issues: original DES is obsolete, Triple-DES, and other remedies. Threat analysis and Key Replacement Policy, and padding schemes. If you encrypt a 4 digits payment PIN, (What Target did...) and pad it with zeros, you weaken DES considerably. You avoid implementation mistakes by learning the machinery of the cipher you use. That is what we do in the Crypto Academy (WeSecure.net/learn).

[@ImaginaryNumb3r]

excellent video, thank your for sharing your knowledge.

[@Vrajesh064]

Excellent information.
Thank you.

[@Hurmatullah_Mahbob]

Good Thanks it was relible video

[@pierrejeanes]

thank you very good information, your voice is like Morgan Freeman. : ) ,
one question, I am encrypting (tripple-des) a conection string obfuscated with blank spaces and the key is a hardware serial number so when my app loads get the devides list and when try to log to the server try the devide id as a key for decryp. so it is safe? how ccai i encrypt 3des + other in .NET any example?