SECURE DOCUMENT DELIVERY

• US 20110302410A1
• Filed: 06/07/2010
• Published: 12/08/2011
• Est. Priority Date: 06/07/2010
• Status: Abandoned Application

• Current Assignee: VE Networks
• Original Assignee: VE Networks
• Inventors: Clarke, Christopher, Mullen, Michael
• Application Number:
  US12/795,591
• Publication Number:
  US 20110302410A1
• Time in Patent Office: Days
• US Class Current: 713/155
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/068 using time-dependent keys, e.g. periodically changing keys cryptographic mechanisms or cryptographic arrangements for controlling usage of secret information H04L9/088
• CPC Class Codes: H04L 9/083 involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
• CPC Class Codes: H04L 9/0872 using geo-location information, e.g. location data, time, relative position or proximity to other entities
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying

Abstract

A method, machine-readable medium, and server to create a key, set an expiration event for the key to expire, send the key to a first client device to encrypt the document, authenticate a second client device that is in receipt of the encrypted document, delete the key if the expiration event has occurred, and send the key from to the authenticated second client device to decrypt the document if the expiration event has not yet occurred. For one embodiment, the key is used by client devices for encryption and decryption of the document only and is not otherwise accessible to the client devices. For one embodiment, the server facilitates sending the encrypted document to the second client device but does not retain a copy of the encrypted document.

Claims

1. A method for secure delivery of a document, the method comprising:

creating, by a server, a key;

setting an expiration event for the key to expire;

sending the key from the server to a first client device to encrypt the document;

authenticating, by the server, a second client device;

determining if the expiration event has occurred;

deleting, by the server, the key if the expiration event has occurred; and

sending the key from the server to the authenticated second client device to decrypt the document if the expiration event has not yet occurred.

2. The method of claim 1, wherein the key is used by the first client device only to encrypt the document and is not otherwise accessible to first client device.

3. The method of claim 1, wherein the key is used by the second client device only to decrypt the document and is not otherwise accessible to second client device.

4. The method of claim 1, wherein the expiration event includes one or more of the following:

an expiration time based upon a time the key was created, an expiration time based upon a time the key was sent to the first client device, an expiration time based upon a time the key was sent to the second client device, an expiration time based upon a time the encrypted document was sent to the second client device, an expiration time based upon a time the first client device encrypts the document, an expiration time based upon a time the second client device decrypts the document, a predetermined number of uses of the key to decrypt the encrypted document, a predetermined number of failed attempts to authenticate the second user, a request from the first client device to erase the key, and a request from the second device to erase the key.

5. The method of claim 1, wherein the bit size of the key is dependent upon the geographical location at least one of the first or second client device.

6. The method of claim 1, further comprising:

receiving, by the server, the encrypted document;

sending the encrypted document from the server to the second client device without the key; and

deleting, from the server, the encrypted document after the encrypted document has been sent to the second client device.

7. The method of claim 1, wherein the first client device provides an answer to a security question and the authentication of the second client device includes the second client device providing the answer to the security question as provided by the first client device.

8. The method of claim 1, wherein authentication of the second client device includes the second client device logging into an account with the server, the account being associated with an email address to which the encrypted document was sent.

9. The method of claim 1, wherein the key is created using a random number generator.

10. A method for secure delivery of a document, the method comprising:

sending, by a first client device, a request to a server to create a key and an expiration event for the key to expire, wherein the server is to delete the key in response to the expiration event;

receiving the key from the server;

encrypting, by the first client device, the document using the key;

causing the encrypted document to be sent to a second client device without the key; and

sending instructions to the server on how to authenticate the second client device and enable the server to send the key to the authenticated second client device if the expiration event has not yet occurred.

11. The method of claim 10, wherein the key is used by the first client device only to encrypt the document and is not otherwise accessible to first client device.

12. The method of claim 10, wherein the expiration event includes one or more of the following:

an expiration time based upon a time the key was created, an expiration time based upon a time the key was sent to the first client device, an expiration time based upon a time the key was sent to the second client device, an expiration time based upon a time the encrypted document was sent to the second client device, an expiration time based upon a time the first client device encrypts the document, an expiration time based upon a time the second client device decrypts the document, a predetermined number of uses of the key to decrypt the encrypted document, a predetermined number of failed attempts to authenticate the second user, a request from the first client device to erase the key, and a request from the second device to erase the key.

13. The method of claim 10, wherein the instructions include an answer to a security question and where the authentication of the second client device includes the second client device providing the answer to the security question as provided by the first client device.

14. A machine-readable storage medium storing instructions that, when executed, cause a server to perform a method comprising:

creating a key;

setting an expiration event for the key to expire;

sending the key to a first client device to encrypt a document;

authenticating a second client device;

determining if the expiration event has occurred;

deleting the key if the expiration event has occurred; and

sending the key to the authenticated second client device to decrypt the document if the expiration event has not yet occurred.

15. The machine-readable storage medium of claim 14, wherein the key is used by the first client device only to encrypt the document and is not otherwise accessible to first client device.

16. The machine-readable storage medium of claim 14, wherein the key is used by the second client device only to decrypt the document and is not otherwise accessible to second client device.

17. The machine-readable storage medium of claim 14, wherein the expiration event includes one or more of the following:

an expiration time based upon a time the key was created, an expiration time based upon a time the key was sent to the first client device, an expiration time based upon a time the key was sent to the second client device, an expiration time based upon a time the encrypted document was sent to the second client device, an expiration time based upon a time the first client device encrypts the document, an expiration time based upon a time the second client device decrypts the document, a predetermined number of uses of the key to decrypt the encrypted document, a predetermined number of failed attempts to authenticate the second user, a request from the first client device to erase the key, and a request from the second device to erase the key.

18. The machine-readable storage medium of claim 14, wherein the bit size of the key is dependent upon the geographical location at least one of the first or second client device.

19. The machine-readable storage medium of claim 14, further comprising:

receiving the encrypted document;

sending the encrypted document to the second client device without the key; and

erasing the encrypted document after the encrypted document has been sent to the second client device.

20. The machine-readable storage medium of claim 14, wherein the first client device provides an answer to a security question and the authentication of the second client device includes the second client device providing the answer to the security question as provided by the first client device.

21. The machine-readable storage medium of claim 14, wherein authentication of the second client device includes the second client device logging into an account with the server, the account being associated with an email address to which the encrypted document was sent.

22. The machine-readable storage medium of claim 14, wherein the key is created using a random number generator.

23. A machine-readable storage medium storing instructions that, when executed, cause a first client device to perform a method comprising:

sending a request to a server to create a key and an expiration event for the key to expire, wherein the server is to delete the key in response to the expiration event;

receiving the key from the server;

encrypting a document using the key;

causing the encrypted document to be sent to a second client device without the key; and

sending instructions to the server on how to authenticate the second client device and enable the server to send the key to the authenticated second client device if the expiration event has not yet occurred.

24. The method of claim 23, wherein the key is used by the first client device only to encrypt the document and is not otherwise accessible to first client device.

25. The method of claim 23, wherein the expiration event includes one or more of the following:

an expiration time based upon a time the key was created, an expiration time based upon a time the key was sent to the first client device, an expiration time based upon a time the key was sent to the second client device, an expiration time based upon a time the encrypted document was sent to the second client device, an expiration time based upon a time the first client device encrypts the document, an expiration time based upon a time the second client device decrypts the document, a predetermined number of uses of the key to decrypt the encrypted document, a predetermined number of failed attempts to authenticate the second user, a request from the first client device to erase the key, and a request from the second device to erase the key.

26. The method of claim 23, wherein the instructions include an answer to a security question and where the authentication of the second client device includes the second client device providing the answer to the security question as provided by the first client device.

27. A server comprising:

a processor; and

a memory, coupled to the processor, storing instructions, which when executed by the system, causes the processor to

create a key,

set an expiration event for the key to expire,

send the key from the server to a first client device to encrypt the document,

authenticate a second client device,

determine if the expiration event has occurred,

delete the key if the expiration event has occurred, and

send the key from the server to the authenticated second client device to decrypt the document if the expiration event has not yet occurred.

28. The server of claim 27, wherein the key is used by the first client device only to encrypt the document and is not otherwise accessible to first client device.

29. The server of claim 27, wherein the key is used by the second client device only to decrypt the document and is not otherwise accessible to second client device.

30. The server of claim 27, wherein the expiration event includes one or more of the following:

an expiration time based upon a time the key was created, an expiration time based upon a time the key was sent to the first client device, an expiration time based upon a time the key was sent to the second client device, an expiration time based upon a time the encrypted document was sent to the second client device, an expiration time based upon a time the first client device encrypts the document, an expiration time based upon a time the second client device decrypts the document, a predetermined number of uses of the key to decrypt the encrypted document, a predetermined number of failed attempts to authenticate the second user, a request from the first client device to erase the key, and a request from the second device to erase the key.

31. The server of claim 27, wherein the bit size of the key is dependent upon the geographical location at least one of the first or second client device.

32. The server of claim 27, wherein the instructions further cause the processor to:

receive the encrypted document;

send the encrypted document to the second client device without the key; and

delete the encrypted document after the encrypted document has been sent to the second client device.

33. The server of claim 27, wherein the first client device provides an answer to a security question and the authentication of the second client device includes the second client device providing the answer to the security question as provided by the first client device.

34. The server of claim 27, wherein authentication of the second client device includes the second client device logging into an account with the server, the account being associated with an email address to which the encrypted document was sent.

35. The server of claim 27, wherein the key is created using a random number generator.