Strong Revocation
Strong Revocation
This is a novel protocol designed by Codel to address the issue of undetected abuse of or access to protected systems. In short, the idea is that every time the protected system is used to communicate with another party, a 3rd party intervenes to seek confirmation that the user accepts responsibility for, and confirms the validity of, the immediately preceding transaction.
For example, if we are using the protocol to protect credit cards, Codel would send back an anonymous token which it has retained from the previous transaction. The user's Codel software would use the token to retrieve details of that transaction and present that information to the user for validation. If the token is not recognised, or if the user does not recognise the details they are being presented with, then the unauthorised abuse or access has been identified and the user can take the appropriate steps.
What this means is that no transaction earlier in the audit trail can subsequently be revoked unless the user is prepared to (and can, presumably, justify) revoke an entire series of transactions. This builds incremental trust into the audit trail.
Please see the Flowchart or Powerpoint for schematic illustration.
Previous page: One Time Pads and One Time Keys
Next page: Strong Authentication