Let`s look at what actually takes the key and the data, and turns it into something that other people can`t read without knowing the key. Algorithms are either secret key algorithms or public key algorithms. The larger the key can be, the better.

Secret Key Algorithms

RC2, RC4, RC5

All these algorithms can handle up to 56-bit (character) keys

DES, Triple DES, DESX

DES can handle up to 56-bit keys

DESX can handle up to 120-bit keys

Triple DES can handle up to 168-bit keys (3 56-bit keys together)

Blowfish

Blowfish can handle keys up to 448-bit keys.

Blowfish is a free, open source algorithm

Rijndael

Rijndael can handle up to 256-bit keys

Rijndael recently replaced Triple DES as the Advanced

Encryption Standard (AES)

Public Key Algorithms

Diffie-Hellman

First public key algorithm, widely used in VPNs

Diffie-Hellman can support up to 1536-bit keys

RSA

RSA can support up to 2034-bits

ElGamal

Developed in 1986, it is widely use in digital certificates

ElGamal can support up to 2048-bits

=========================================================

Hackability

Hacking any of these systems can be tough, but it has been done. Some of the above mentioned algorithms have also shown weaknesses as well. The elitist underground of cryptographic hackers, so aptly named as ``cypherpunks,`` are there to try, and they have an arsenal of attacks and exploits at their disposal.

The main attack they will try to use is called a brute-force crack. The size of the key determines the amount of time it will take. They capture the message and then begin guessing as to what the key could be. The guessing is done by a program and the guesses are every possible key that the key could be. They figure out the algorithm used, what the key length is, and then go at it.

It is important to remember: All encrypted messages can be cracked through brute force cracking! This can take quite some time, depending on the key length (upward of 900 years with some). Other attacks use known weaknesses in an algorithm that can be very complicated and confusing to comprehend. The point to remember is that they exist.

The main weakness they`ll exploit is small and/or bad keys. Keys are like passwords—don`t use the same one twice, and use mixture of letters, numbers, and characters. tR3~$8)vQq% is a good example of what you would want a key to look like, just make sure it`s a lot longer. I can`t stress enough the practice of making your keys and passwords as strong as possible. Weak keys are the number one cause of these systems getting compromised.``

=========================================================

TDL:

``DES, 3DES, and AES. The TDL uses a physically secure FIPS 140-1, level 2-compliant hardware device to perform authentication and encryption key storage.``

========================================================

======================================================

The TDL will Handel any of the standard mentioned Cryptography types mentioned above...as long as a compliant decryptor is present...

The keys generated by the originator of the content are then carried forth and placed within the ``physically secure FIPS 140-1, level 2-compliant hardware device``(decryptor)

An authentication process is then established between the encrypted files and the compliant hardware device.

This is all a post production single layer process encrypting files....if content providers feel confident in encrypting files only...Fine.

The DigE first layer can be configured....to manage any method of post production file Cryptography with matching decryptor mechanism.

This for what ever DivX provides or any of the above with keys attached....and safe harbor it within yet another Hardware Encryption scheme.

The DigE is a dual layer scheme....e.Digital supplies the top layer of the scheme...the content file key management is not handled the same as the TDL.....The TDL is the end of the line for encrypted content...it is decrypted at that point if files need to be decrypted....files sit on the TDL at one layer of encryption...

If e.Digital`s layer is not needed so be it.

doni