Network side channel for a message board
First Claim
1. In a messaging board server using a legacy protocol to post data messages for multiple clients, a method of extending the functionality and data properties offered by the legacy protocol, without modifying the legacy protocol so as to maintain support for clients with only legacy capabilities, the method comprising the acts of:
- receiving legacy data, including a main body of a data message, for posting on a messaging board over an unsecured legacy channel using a legacy protocol for supporting legacy clients;
participating in the creation of a secure side channel for exchanging extended data properties and supporting functionalities not offered by the legacy protocol;
receiving over the secure side channel extended data that includes a client hash value, created by a client when hashing at least a portion of the legacy data, and metadata for defining extended data properties that extend the legacy protocol;
creating a server hash value by hashing at least a portion of the legacy data received over the unsecured legacy channel;
linking the legacy data and the extended data; and
comparing the client hash value with the server hash value to ensure that the legacy data has not been altered for extending the functionality of the legacy protocol by securing the unsecured legacy channel without having modified the legacy protocol.
2 Assignments
0 Petitions
Accused Products
Abstract
The present invention allows for extending the functionality and data properties of a messaging board protocol, while maintaining support for legacy clients. A secure side channel is provided that allows functionalities and data properties not supported by a legacy protocol to be implemented. The unsecured legacy channel that uses a legacy protocol, however, is maintained. Legacy data can be sent over the legacy channel and subsequently linked up with the data properties sent over the secure side channel for extending the data properties. Because side channel is secure, a hashing and comparison of legacy data on the client and the server side allows for securing the unsecured legacy channel, thereby extending the functionality of the legacy protocol.
-
Citations
35 Claims
-
1. In a messaging board server using a legacy protocol to post data messages for multiple clients, a method of extending the functionality and data properties offered by the legacy protocol, without modifying the legacy protocol so as to maintain support for clients with only legacy capabilities, the method comprising the acts of:
-
receiving legacy data, including a main body of a data message, for posting on a messaging board over an unsecured legacy channel using a legacy protocol for supporting legacy clients; participating in the creation of a secure side channel for exchanging extended data properties and supporting functionalities not offered by the legacy protocol; receiving over the secure side channel extended data that includes a client hash value, created by a client when hashing at least a portion of the legacy data, and metadata for defining extended data properties that extend the legacy protocol; creating a server hash value by hashing at least a portion of the legacy data received over the unsecured legacy channel; linking the legacy data and the extended data; and comparing the client hash value with the server hash value to ensure that the legacy data has not been altered for extending the functionality of the legacy protocol by securing the unsecured legacy channel without having modified the legacy protocol. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. In a client that posts messages to a messaging board server using a legacy protocol, a method of extending the functionality and data properties offered by the legacy protocol without modifying the legacy protocol so as to maintain support for clients with only legacy capabilities, the method comprising the acts of:
-
posting legacy data, including a main body of a message, on a messaging board over an unsecured legacy channel using a legacy protocol that supports legacy clients; establishing a secure side channel when exchanging extended data for supporting data properties and functionality not offered by the legacy protocol; creating a client hash value by hashing at least a portion of the legacy data; and sending over the secure side channel extended data that includes metadata for defining extended data properties and the client hash value; and correlating the legacy data sent on the unsecured legacy channel with the extended data sent over the secure side channel to ensure that the legacy data over the unsecured legacy channel has not been altered. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23)
-
-
24. In a client that receives messages from a network server using a legacy protocol, a method of extending the functionality and data properties offered by the legacy protocol without modifying the legacy protocol so as to maintain support for clients with only legacy capabilities, the method comprising the acts of:
-
receiving legacy data, including at least one main body of a message, from a network server to be received over an unsecured legacy channel using a legacy protocol that supports legacy clients; establishing a secure side channel when exchanging extended data for supporting data properties and functionality not offered by the legacy protocol; receiving over the secure side channel extended data that includes metadata for defining extended data properties and a server hash value, which is a hash of at least a portion of the legacy data received over the unsecured legacy channel; linking the legacy data and the extended data; creating a client hash value by hashing at least a portion of the legacy data received over the unsecured channel; and comparing the client hash value with the server hash value to ensure that the legacy data has not been altered. - View Dependent Claims (25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35)
-
Specification