I think enough of the key is in the record that brute-forcing the remainder wouldn't be much of a challenge. I'm not sure what the parameters represent, but only erk and pub are truncated. I'm assuming that "pub" is the public key in this context.
Ironically they truncated the public part of the DSA keys. The private key is "k".
For bruteforcing the remainder of the AES256 loader key (erk), as proposed by another commenter: There are still 13 hex-digits left (e.g. 52 bits), that might take a while ;-).
AES256 is indeed more complex than DES, but it's important to remember that both were designed partially with fast hardware implementations in mind. The difference is not as dramatic as you might initially think. 52 bits of an AES256 key are weeeell within "doable" in 2010.
Comments
The erk and priv values in the printed website shown there are truncated, so it is not the whole key.
I think enough of the key is in the record that brute-forcing the remainder wouldn't be much of a challenge. I'm not sure what the parameters represent, but only erk and pub are truncated. I'm assuming that "pub" is the public key in this context.
Ironically they truncated the public part of the DSA keys. The private key is "k".
For bruteforcing the remainder of the AES256 loader key (erk), as proposed by another commenter: There are still 13 hex-digits left (e.g. 52 bits), that might take a while ;-).
The EFF's Deep Crack could do 56-bit keys in a matter of days, and this was a long while ago:
http://en.wikipedia.org/wiki/Deep_Crack
AES256 is more complex than DES, but it's still in the ballpark of "possible".
AES256 is indeed more complex than DES, but it's important to remember that both were designed partially with fast hardware implementations in mind. The difference is not as dramatic as you might initially think. 52 bits of an AES256 key are weeeell within "doable" in 2010.