### Random thuds on cracking public key encryption

Lemme see now...

Let

Let ¤ represent

Let

Let

Let

Let

Alice cleverly enciphers

Alice pops

Bob deduces

Bob deciphers

Aaarrrgh!

Ok. This probably

Let

*T*be a plaintext which Alice must convey to Bob.Let ¤ represent

`exclusive-or`, or some similar operation which is reversible when twice applied (or at least symmetric, like TEA, where`encode`and`decode`work jes' fine.)Let

*P*be Alice's public key, and*p*be her private key.Let

*P*←*¤***M***p*, where*is mysterious***M**^{†}.Let

*Q*be Bob's public key, and*q*his private key.Let

*Q*←*¤***M***q*, where*is still mysterious.***M**Alice cleverly enciphers

*C*←*T*¤*Q*¤*p*.Alice pops

*C*into an envelope and sends it to Bob, awaiting anxiously.Bob deduces

__Alice's private key__,*p*← (*¤***M***p*)¤(*¤***M***q*)¤*q*←*P*¤*Q*¤*q*.Bob deciphers

*T*←*C*¤*Q*¤*p*.Aaarrrgh!

Ok. This probably

*ain't*how public key encryption works, but if it reduces to*this*case, kiddies, the jig is up!^{†}**is***M**not*my favorite pseudorandom number generator, Mersenne Twister.**is***M**mysterious!*Like this.Labels: Crypto

## 0 Comments:

## Post a Comment

Subscribe to Post Comments [Atom]

<< Home