Slave secure sockets layer proxy system
US-2020084029-A1 · Mar 12, 2020 · US
US11368439B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11368439-B2 |
| Application number | US-202016806357-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 2, 2020 |
| Priority date | Oct 13, 2015 |
| Publication date | Jun 21, 2022 |
| Grant date | Jun 21, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A non-transitory computer-readable storage medium comprising instructions stored thereon. When executed by at least one processor, the instructions may be configured to cause a computing system to at least receive a message, the message including a header, an encrypted symmetric key, and an encrypted body, decrypt the encrypted symmetric key using a private key to generate a decrypted symmetric key, decrypt the encrypted body using the decrypted symmetric key to generate a decrypted body, and store the header, the decrypted symmetric key, and the decrypted body in long-term storage.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving a message, the message including a header, an encrypted symmetric key, and an encrypted body; decrypting the encrypted symmetric key using a private key to generate a decrypted symmetric key; decrypting the encrypted body using the decrypted symmetric key to generate a decrypted body; storing the decrypted symmetric key in long-term storage; storing an identification of a recipient of the message, in association with the decrypted symmetric key, in the long-term storage; displaying the decrypted body; and responding to a request to forward the message to the recipient by: re-encrypting the decrypted body using the decrypted symmetric key; re-encrypting the decrypted symmetric key; and sending the header, the re-encrypted body, and the re-encrypted symmetric key to the recipient. 2. The method of claim 1 , wherein the receiving the message includes receiving an email message via an electronic network. 3. The method of claim 1 , wherein the displaying the decrypted body comprises displaying the decrypted body in response to a request to read the message. 4. The method of claim 1 , wherein the displaying the decrypted body comprises responding to a request to read the message by retrieving the header and the decrypted body from long-term storage and displaying the header and the decrypted body. 5. The method of claim 1 , wherein the method comprises not storing the encrypted body after decrypting the encrypted body. 6. The method of claim 1 , further comprising erasing the encrypted body after decrypting the encrypted body. 7. The method of claim 1 , wherein the header of the message includes the identification of the recipient of the message. 8. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to at least: receive a message, the message including a header, an encrypted symmetric key, and an encrypted body; decrypt the encrypted symmetric key using a private key to generate a decrypted symmetric key; decrypt the encrypted body using the decrypted symmetric key to generate a decrypted body; store the decrypted symmetric key in long-term storage; store an identification of a recipient of the message, in association with the decrypted symmetric key, in the long-term storage; display the decrypted body; and respond to a request to forward the message to the recipient by: re-encrypting the decrypted body using the decrypted symmetric key; re-encrypting the decrypted symmetric key; and sending the header, the re-encrypted body, and the re-encrypted symmetric key to the recipient. 9. The non-transitory computer-readable storage medium of claim 8 , wherein the receiving the message includes receiving an email message via an electronic network. 10. The non-transitory computer-readable storage medium of claim 8 , wherein the displaying the decrypted body comprises displaying the decrypted body in response to a request to read the message. 11. The non-transitory computer-readable storage medium of claim 8 , wherein the displaying the decrypted body comprises responding to a request to read the message by retrieving the header and the decrypted body from long-term storage and displaying the header and the decrypted body. 12. The non-transitory computer-readable storage medium of claim 8 , wherein the instructions are further configured to cause the computing system to not store the encrypted body after decrypting the encrypted body. 13. The non-transitory computer-readable storage medium of claim 8 , wherein the instructions are further configured to cause the computing system to erase the encrypted body after decrypting the encrypted body. 14. The non-transitory computer-readable storage medium of claim 8 , wherein the header of the message includes the identification of the recipient of the message. 15. A computing system comprising: at least one processor; and a non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause the computing system to at least: receive a message, the message including a header, an encrypted symmetric key, and an encrypted body; decrypt the encrypted symmetric key using a private key to generate a decrypted symmetric key; decrypt the encrypted body using the decrypted symmetric key to generate a decrypted body; store the decrypted symmetric key in long-term storage; store an identification of a recipient of the message, in association with the decrypted symmetric key, in the long-term storage; display the decrypted body; and respond to a request to forward the message to the recipient by: re-encrypting the decrypted body using the decrypted symmetric key; re-encrypting the decrypted symmetric key; and sending the header, the re-encrypted body, and the re-encrypted symmetric key to the recipient. 16. The computing system of claim 15 , wherein the receiving the message includes receiving an email message via an electronic network. 17. The computing system of claim 15 , wherein the displaying the decrypted body comprises displaying the decrypted body in response to a request to read the message. 18. The computing system of claim 15 , wherein the displaying the decrypted body comprises responding to a request to read the message by retrieving the header and the decrypted body from long-term storage and displaying the header and the decrypted body. 19. The computing system of claim 15 , wherein the instructions are further configured to cause the computing system to erase the encrypted body after decrypting the encrypted body. 20. The computing system of claim 15 , wherein the header of the message includes the identification of the recipient of the message.
using key encryption key · CPC title
Proxy, i.e. using intermediary entity to perform cryptographic operations · CPC title
Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use · CPC title
using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates · CPC title
Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.