Encrypting and transmitting data

• US 9,876,772 B1
• Filed: 07/02/2015
• Issued: 01/23/2018
• Est. Priority Date: 07/16/2012
• Status: Active Grant

• Current Assignee: Wickr Inc. (Amazon.com, Inc.)
• Original Assignee: Wickr Inc. (Amazon.com, Inc.)
• Inventors: Statica, Robert, Coppa, Kara Lynn, Howell, Christopher A.
• Primary Examiner(s): Zee, Edward
• Application Number:
  US14/791,214
• Time in Patent Office: 936 Days
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/84 output devices, e.g. displays or monitors
• CPC Class Codes: G06F 2203/04104 Multi-touch detection in digitiser, i.e. details about the simultaneous detection of a plurality of touching locations, e.g. multiple fingers or pen and finger
• CPC Class Codes: G06F 2203/04808 Several contacts: gestures triggering a specific function, e.g. scrolling, zooming, right-click, when the user establishes several contacts with the surface simultaneously; e.g. using several fingers or a combination of fingers and pen
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/0488 using a touch-screen or digitiser, e.g. input of commands through traced gestures
• CPC Class Codes: G06F 3/04886 by partitioning the display area of the touch-screen or the surface of the digitising tablet into independently controllable areas, e.g. virtual keyboards or menus
• CPC Class Codes: G06V 20/64 Three-dimensional objects
• CPC Class Codes: H04L 2209/24 Key scheduling, i.e. generating round keys or sub-keys for block encryption
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0421 Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 9/08 Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords network architectures or network communication protocols for supporting key management in a packet data network H04L63/06
• CPC Class Codes: H04L 9/0816 Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
• CPC Class Codes: H04L 9/0822 using key encryption key
• CPC Class Codes: H04L 9/0825 using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
• CPC Class Codes: H04L 9/0841 : involving Diffie-Hellman or related key agreement protocols
• CPC Class Codes: H04L 9/0869 : involving random numbers or seeds
• CPC Class Codes: H04L 9/30 : Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/3066 : involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
• CPC Class Codes: H04L 9/3236 : using cryptographic hash functions

Abstract

A message having at least one intended recipient is encrypted using a first key. The first key is encrypted with a second key associated with the recipient. At least two of the encrypted message, the encrypted first key, and an identifier associated with the at least one recipient are encapsulated in a secure communication protocol encapsulation. The secure communication protocol encapsulation is transmitted to a server.

Claims

1. A system, comprising:

a processor configured to;

encrypt a message intended for at least one recipient and one or more message control options using a first key;

encrypt the first key using both a second key associated with the at least one recipient and at least one parameter associated with the recipient'"'"'s device, wherein the at least one parameter associated with the recipient'"'"'s device is used as an input to seed the encryption of the first key;

encapsulate the encrypted message, the one or more encrypted message control options, the encrypted first key, and an identifier associated with the at least one recipient in a secure communication protocol encapsulation; and

transmit the secure communication protocol encapsulation to a first server; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system of claim 1 wherein the secure communication protocol is Transport Layer Security (TLS).

3. The system of claim 1, wherein the processor is further configured to:

encapsulate the encrypted message, the one or more encrypted message control options, the encrypted first key, and the identifier associated with the at least one recipient in a digital security bubble encapsulation prior to being encapsulated in the secure communication protocol encapsulation.

4. The system of claim 1 wherein the processor is further configured to obtain the second key and the identifier associated with the at least one recipient.

5. The system of claim 4 wherein the second key and the identifier are obtained from a second server.

6. The system of claim 1 wherein the identifier comprises a device identifier.

7. The system of claim 6 wherein the device identifier is based, at least in part, on at least one hardware identifier.

8. The system of claim 1 wherein the identifier comprises an application identifier.

9. The system of claim 1 wherein the second key is a public key.

10. The system of claim 9 wherein the processor is configured to request a plurality of public keys and a plurality of device identifiers associated with a plurality of recipients.

11. The system of claim 10 wherein the processor is further configured to encrypt the first key with each of the received public keys to produce a plurality of encrypted first keys.

12. A method, comprising:

encrypting a message intended for at least one recipient and one or more message control options using a first key;

encrypting the first key using both a second key associated with the at least one recipient and at least one parameter associated with the recipient'"'"'s device, wherein the at least one parameter associated with the recipient'"'"'s device is used as an input to seed the encryption of the first key;

encapsulating the encrypted message, the one or more encrypted message control options, the encrypted first key, and an identifier associated with the at least one recipient in a secure communication protocol encapsulation; and

transmitting the secure communication protocol encapsulation to a first server.

13. The method of claim 12, wherein the secure communication protocol is Transport Layer Security (TLS).

14. The method of claim 12, further comprising:

encapsulating the encrypted message, the one or more encrypted message control options, the encrypted first key, and an identifier associated with the at least one recipient in a digital security bubble encapsulation prior to being encapsulated in the secure communication protocol encapsulation.

15. The method of claim 12 further comprising obtaining the second key and the identifier associated with the at least one recipient.

16. The method of claim 12 wherein the identifier comprises a device identifier based, at least in part, on at least one hardware identifier.

17. The method of claim 12 wherein the identifier comprises an application identifier.

18. A computer program product embodied in a non-transitory tangible computer readable storage medium and comprising computer instructions for:

encrypting a message intended for at least one recipient and one or more message control options using a first key;

encrypting the first key using both a second key associated with the at least one recipient and at least one parameter associated with the recipient'"'"'s device, wherein the at least one parameter associated with the recipient'"'"'s device is used as an input to seed the encryption of the first key;

encapsulating the encrypted message, the one or more encrypted message control options, the encrypted first key, and an identifier associated with the at least one recipient in a secure communication protocol encapsulation; and

transmitting the secure communication protocol encapsulation to a first server.

19. The computer program product of claim 18, wherein the secure communication protocol is Transport Layer Security (TLS).

20. The computer program product of claim 18, further comprising computer instructions for:

encapsulating the encrypted message, the one or more encrypted message control options, the encrypted first key, and an identifier associated with the at least one recipient in a digital security bubble encapsulation prior to being encapsulated in the secure communication protocol encapsulation.