
Thug@phantom.com says:
There's actually a much easier way for a backdoor to be inserted that will allow monitoring even without the spooks knocking on your door to get your disk... PGP uses RSA only to encode and transmit a "random" DES/IDEA-type session key, and the rest of the message is encoded only with the session key. The recipient PGP uses RSA to recover the session key, and then decodes the rest of the message with the recovered session key. Say that the "backdoored" PGP is redesigned to only choose session keys from a large-but-reasonably-brute-forceable set.... [example: only from consecutive 8-byte sequences in the executable image; I'm sure some other more obscure method can be easily devised]. The result is that there might only be a few hundred thousand possible session keys- few enough that a brute-force attack with a small array of workstations might succeed in recovering the session key in a few minutes to hours. ----- The only way ViaCrypt can prove that this isn't the case is to distribute the source code of _their_ product. [Note: they do NOT have to include the RSA module source- if it's possible to examine the non-RSA code, and instrument it (to prove that the session key is honestly generated _AND_ transmitted/recovered correctly) then Thug's tests will be adequate to verify a lack of backdoors (as far as I can see- but I'm perhaps not as devious as a professional). -Bill

One could apply the same sabotage to the generation of RSA public keys making any keys generated with ViaCrypt easily crackable. Of course you could use PGP to generate keys. And now what is ViaCrypt useful for? It's original purpose: Establishing plausable deniability. "Yes your honor, all these encrypted messages presented by the FBI as Exibit A were generated by ViaCrypt which incidentally we have a site licence for... No sir, We've never used PGP." brad
participants (2)
-
Brad Huntting
-
Read me doctor memory! 26-Aug-1993 1434