Efficient certified email protocol

• US 8,341,410 B2
• Filed: 10/08/2007
• Issued: 12/25/2012
• Est. Priority Date: 10/08/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Shao, Jun, Zhu, Bin, Feng, Min
• Primary Examiner(s): Orgad, Edan
• Assistant Examiner(s): OLION, BRIAN L
• Application Number:
  US11/868,872
• Publication Number:
  US 20090094452A1
• Time in Patent Office: 1,905 Days
• Field of Search: 713/171
• US Class Current: 713/171
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 9/0844 with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3218 using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs

Abstract

An exemplary optimistic protocol for a two-party transaction includes a setup sub-protocol that includes an authorized Diffie-Hellman key agreement, an exchange sub-protocol that includes sending a certificate from a sending party to a receiving party and sending a receipt from the receiving party to the sending party and a dispute sub-protocol that includes a dispute resolution mechanism for resolving disputes between the sending party and the receiving party due to sending of an invalid certificate, due to sending an invalid receipt, or due to abortion of the exchange sub-protocol. Other exemplary methods, systems, etc., are also disclosed.

Claims

1. One or more computer-readable memory storing computer-executable instructions that, when executed, cause one or more processors to implement protocols for a two-party transaction, the protocols comprising:

a setup sub-protocol that comprises using an authorized Diffie-Hellman key agreement to share an encryption key between a sending party and a trusted third party that resolves transaction disputes between the sending party and a receiving party;

an exchange sub-protocol that comprises sending a message description, a hash of the encryption key, a certificate, and a message encrypted by the encryption key from the sending party to the receiving party, sending a receipt from the receiving party to the sending party during the two-party transaction, and sending the encryption key from the sending party to the receiving party in response to receiving the receipt at the sending party; and

a dispute sub-protocol that comprises a dispute resolution mechanism to resolving disputes between the sending party and the receiving party by the trusted third party at least due to a discrepancy between the hash and an additional hash of the encryption key.

2. The one or more computer-readable memory of claim 1, wherein the two-party transaction comprises an email transaction.

3. The one or more computer-readable memory of claim 1, wherein the message is an encrypted message that is encrypted using the encryption key.

4. The one or more computer-readable memory of claim 1, wherein the message description is a hash of the message.

5. The one or more computer-readable memory of claim 2, wherein the exchange sub-protocol further comprises sending decryption information that provides the encryption key from the sending party to the receiving party for decrypting the message in exchange for the receipt.

6. The one or more computer-readable memory of claim 5, wherein the encryption key is a symmetric encryption key.

7. The one or more computer-readable memory of claim 1, wherein the trusted third party is to further resolve disputes between the sending party and the receiving party further due to one of sending of an invalid certificate, sending of an invalid receipt, a discrepancy between the message and the message description, or an abortion of the exchange sub-protocol.

8. The one or more computer-readable memory of claim 1, wherein the message is an email message.

9. The one or more computer-readable memory of claim 1, wherein the trusted third party is different from a certification authority that issued the certificate.

10. The one or more computer-readable memory of claim 1, wherein the setup sub-protocol includes registering a public key with a certification authority in exchange for the certificate.

11. The one or more computer-readable memory of claim 2, wherein the trusted third party resolves disputes between the sending party and the receiving party by at least one of providing decryption information for an email that is sent by the sending party to the receiving party during the email transaction or forcing the receiving party to send a valid receipt to the sending party in exchange for the email.

12. The one or more computer-readable memory of claim 1, wherein the sending party and the receiving party transact via a distributed application operating in a distributed computing environment.

13. The one or more computer-readable memory of claim 1, wherein the setup sub-protocol further comprises binding a public key of the sending party to a certificate for the sending party.

14. The one or more computer-readable memory of claim 13, wherein the trusted party is an off-line party to the two-party transaction between the sending party and the receiving party.

15. The one or more computer-readable memory of claim 1, wherein the setup sub-protocol comprises a modified Schnorr signature scheme for generating a signature for the receiving party that is included in the receipt.

16. A computer-implemented method, comprising:

sharing an encryption key that is known to the sending party with a trusted third party using an authorized Diffie-Hellman key agreement, the encryption key for resolving transaction disputes between the sending party and a receiving party;

sending a message description, a hash of the encryption key, a certificate, and an encrypted message that is encrypted by the encryption key to the receiving party;

receiving a receipt from the receiving party and in response to the receiving, sending decryption information to the receiving party, wherein the decryption information provides the encryption key for decrypting the encrypted message; and

receiving an indication that the receiving party sent a dispute resolution request to the trusted third party, the dispute resolution request being sent in response to detecting a discrepancy between the hash and an additional hash of the encryption key performed by the receiving party.

17. The method of claim 16, wherein the trusted party is an off-line party to a two-party transaction between the sending party and the receiving party.

18. A method, implemented at least in part by a computing device, the method comprising:

under control of a computing device comprising one or more processors,

receiving a message description, a hash of an encryption key, an encrypted message, and a certificate from a sending party at a receiving party, the encrypted message being encrypted based at least on the encryption key, the encryption key being shared between the sending party and a trusted third party using an authorized Diffie-Hellman key agreement prior to a transaction dispute between the sending party and the receiving party;

sending a receipt from the receiving party to the sending party during a two-party transaction, and receiving the encryption key from the sending party in exchange for the receipt; and

sending a dispute resolution request from the receiving party to the trusted third party in response to detecting a discrepancy between the hash and an additional hash of the encryption key.

19. The method of claim 18, further comprising receiving a decryption key from the trusted third party at the receiving party when the receiving party provides the receipt to the trusted third party during a dispute resolution.

20. The method of claim 19, further comprising decrypting the message at the receiving party using the decryption key from the trusted third party.