Methods, systems, and data structures for secure data content presentation

• US 20030174841A1
• Filed: 03/15/2002
• Published: 09/18/2003
• Est. Priority Date: 03/15/2002
• Status: Abandoned Application

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Nault, Gabe, Burch, Lloyd
• Application Number:
  US10/099,417
• Publication Number:
  US 20030174841A1
• Time in Patent Office: Days
• US Class Current: 380/277
• CPC Class Codes: H04L 2209/34 Encoding or coding, e.g. Huffman coding or error correction
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods, systems, and data structures are provided for secure data content presentation. A client makes a request to access data content on a remote server. A key is associated with the data content. Moreover, the key and the data content are delivered to the client. In one embodiment, a proxy server generates the key and provides the data content along with the key to the client. The client validates the key prior to presenting the data content.

Claims

1. A method for secure data content presentation, comprising:

receiving from a client a request for data content located on a remote server;

obtaining the data content from the remote server using the request;

generating a key based on the data content; and

sending to the client the data content and the key.

2. The method of claim 1, wherein in receiving the request, the request is a Uniform Resource Locator (URL) address.

3. The method of claim 1, wherein in obtaining the data content, the remote server is a World Wide Web (WWW) server.

4. The method of claim 1, wherein in generating the key, the key is a digital signature.

5. The method of claim 1, wherein in generating the key, the key is generated using a checksum operation performed against the content data.

6. The method of claim 1, wherein in receiving the request, the client is a WWW browser.

7. The method of claim 1 wherein in sending the data content, the data content is sent using a Secure Sockets Layer (SSL) data communication protocol over the Internet.

9. The method of claim 7, wherein in receiving the data content, the data content and the key are sent by a proxy server.

10. The method of claim 7, wherein in validating the key, the key is validated within a World Wide Web (WWW) browser by processing a validation set of executable instructions before attempting to present the data content within the WWW browser.

11. The method of claim 7, wherein in validating the key, the key is validated by performing one or more metrics against the data content to produce a value, and wherein the key is validated if the value equals the key.

12. The method of claim 7, wherein in receiving the data content, the key is a signature for the data content.

13. The method of claim 7, further comprising re-establishing an unaltered version of the data content if the key is not validated and then displaying the unaltered version of the content data.

15. The method of claim 7, further comprising presenting notification data indicating that the data content has been altered if the key is not validated.

17. The system of claim 15, wherein the client, the proxy server, and the remote server are interfaced over the World Wide Web (WWW) using an Internet connection.

19. The system of claim 15, wherein the client uses the key to detect modifications in the data content when the key is not validated, and prevents the changes from being presented on the client.

20. The system of claim 15, wherein the client presents a notification of any detected modifications in the data content when the key is not validated.

21. The system of claim 15, wherein the key is at least one of a signature for the data content and a checksum value for the data content.

23. The data structure of claim 20, wherein the remote server is a World Wide Web (WWW) server, the client is a WWW browser, and the key is a signature for the data content.

24. The data structure of claim 20, wherein the client presents a notification if the key is not validated.

25. The data structure of claim 20, wherein the data content is a WWW page.

26. The data structure of claim 20, wherein the client validates the key immediately prior to attempting to present the data content.

27. The data structure of claim 20, wherein the client presents an unaltered version of the data content if the key is not validated.

8. A method for secure data content presentation, comprising:

sending a request for data content, wherein the data content is accessible to a remote server;

receiving the data content along with a key for the data content; and

validating the key before presenting the data content, and if the key is valid presenting the data content.

14. The method of claim 8, wherein in re-establishing the unaltered version of the data content, the unaltered version of the data content is reconstructed using a Cyclical Redundancy Check (CRC) operation.

16. A secure data content presentation system, comprising:

a client;

a proxy server;

a remote server; and

wherein the client requests data content from the remote server through the proxy server, and the proxy server acquires the data content from the remote server and generates a key based on the data content, the proxy server transfers the data content and the key to the client, and the client validates the key before presenting the data content.

18. The system of claim 16, wherein the client is a WWW browser, and the remote server is a WWW server.

22. A data structure residing on a computer readable medium used for secure data content presentation, comprising:

data content representing data requested from a remote server by a client;

a key generated by a proxy server, wherein the key uniquely identifies the data content and is operable to be validated by the client; and

wherein the data content and the key are sent from the proxy server to the client, and the client validates the key before presenting the data content.