Check out the new USENIX Web site. next up previous
Next: Discussion Up: The Resilient On-line Transaction Previous: The transaction procedure

The secret-revocation procedure

When a customer wants to change her secret, she has to send previously used information with a new secret. We suggest a way of revocation and update of secrets: the customer sends a nonce tex2html_wrap_inline594 with C to the bank, then the bank sends back tex2html_wrap_inline598 . The customer checks tex2html_wrap_inline600 , if it is valid, she requests to update her shared information by sending tex2html_wrap_inline602 , where tex2html_wrap_inline604 is the new secret. It the customer wants to change p as well, she can do it in the same procedure, but does not have to. When tex2html_wrap_inline608 is correct, the bank changes the customer's information. Similarly, the customer can change her information in a merchant by using tex2html_wrap_inline610 and tex2html_wrap_inline612 , where tex2html_wrap_inline614 is a nonce and tex2html_wrap_inline616 is the new secret. If the customer cannot remember her previous information, the information cannot be revoked on-line, and the revocation should be done in off-line communication with both the bank and the merchant.

PROTOCOL



next up previous
Next: Discussion Up: The Resilient On-line Transaction Previous: The transaction procedure

Jong-Hyeon Lee, Computer Laboratory, University of Cambridge, 1998.