🚀 go-pugleaf

In article <1e97f0INNmsr@transfer.stratus.com>, cme@ellisun.sw.stratus.com (Carl Ellison) writes:
|> In article <1992Nov14.153536.9930@infodev.cam.ac.uk> rja14@cl.cam.ac.uk (Ross Anderson) writes:
|> >
|> >Call a public key cryptosystem coercion-resistant if an opponent who 
|> >monitors the channel between two parties, and some time thereafter 
|> >obtains the cooperation of one of these parties, cannot recover the 
|> >session key.
|> >
|> 
|> If I wanted to do this with an RSA system, I'd put my session key in
|> a record with an expiration datime.  My tamper-resistent Digital Signing
|> Unit would check the expiration datime and refuse to give me a session
|> key which has expired.  Under no circumstances would anyone be allowed
|> to get the secret part of the RSA key out of the DSU.  There would be
|> no passive backup of the DSU.

How do you ensure that the DSU is tamper-resistant?  What's to stop me
from hacking your RSA system to bypass the expiration date check?

-- 
Peter K. Boucher
--
RIPEM public key available upon request.