Process for verifying the preservation of the integrity of an unprotected request sent by a client to a server by verifying the integrity of the response

• US 5,926,549 A
• Filed: 02/12/1997
• Issued: 07/20/1999
• Est. Priority Date: 02/12/1996
• Status: Expired due to Fees

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Pinkas, Denis
• Primary Examiner(s): Hayes, Gail O.
• Assistant Examiner(s): SAYADIAN, HRAYR
• Application Number:
  US08/799,629
• Time in Patent Office: 888 Days
• Field of Search: 380/23, 380/24, 380/25, 380/49, 340/825.3, 340/825.31, 340/825.34, 395/186, 395/187.01, 395/188.01
• US Class Current: 713/168
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention relates to a process for verifying the preservation of the integrity of an unprotected request sent by an anonymous client to a server, in which only one public key, that of the server, is used. This process is remarkable in that the anonymous client sends, along with his request, a flag which specifies whether or not the server must offer an absolute guarantee of non-repetition of the requests received as well as a unique number, that is, a number which never repeats or has a low probability of repetition, consisting either of a random number with a low probability of repetition or the concatenation of a time indicator and a random number with a certainty of non-repetition, the verification of said integrity being performed during the reception of the response to the request, for which reason the global response includes the response to the request plus the result of a one-way compression function applied to the request, flag and unique number combination, the integrity of the global response moreover being protected either by means of the public key of the server used as a signature key, or by means of a private key established using the public key of the server as an encryption key.

Claims

1. A computer implemented process for verifying the preservation of the integrity of an unprotected request sent by a client to a server which provides a response to the request and in which a signature key of the server is used, comprising adding a flag to a request sent by the client to the server, the flag specifying whether or not the server must offer a guarantee of non-repetition, as well as a unique number which never repeats or has a low probability of repetition, consisting either of a random number with a low probability of repetition or of a concatenation of a time indicator and a random number with a certainty of non-repetition, verifying said integrity by the client during the reception of a global response to the request, the global response including the response to the request plus the result of a one-way compression function applied to the request, flag, and unique number combination, the integrity of the global response moreover being protected by means of the key of the server.

2. The process for verifying the preservation of the integrity of a sent request according to claim 1, characterized in that the signature key of the server is a private key used to sign the global response which private key, upon reception of the global response, is verified by the client using a public signature key of the server.

3. The process for verifying the preservation of the integrity of a sent request according to claim 2, further comprising deciding in advance when sending a request whether or not non-duplication of the unique number is to be absolutely guaranteed by the server and adding to the request the flag specifying whether or not the server must offer said guarantee as well as the unique number formed, then performing a calculation applying the one-way compression function to the request, flag, and unique number combination, storing the calculation locally, and when the server receives the request, if the client has indicated that the server is to guarantee non-repetition, said server tests whether it can guarantee the non-repetition of the unique number, and indicating with a different flag during the response if the guarantee of non-repetition cannot be given, otherwise the server verifies whether or not said unique number has already been received and then sends an error message if the unique number has already been received, or in the opposite case, performs a calculation applying the one-way compression function to the request, flag, and unique number combination received and includes this calculation in its response, the integrity of the global response being protected by means of the key of the server, whereas the client receiving this response first verifies whether the calculation he has stored effectively corresponds to the calculation sent by the server and if this is the case, then verifies the digital signature or the mark depending on the variant used, the preservation of the integrity of the request sent previously being determined when the calculation and the integrity are verified.

4. The process for verifying the preservation of the integrity of a sent request according to claim 3, used in the case of an application in which a client who does not possess any private key desires to register the client'"'"'s public key and make the client known to a server acting as a key certification authority, characterized in that the client, with knowledge of the public key of the key certification authority, sends the certification authority an unprotected request constituted by the public key to be registered, his identity, a flag and a unique number, while performing a calculation applying a one-way compression function to the entire request, storing the calculation locally, and the certification authority, upon receiving said request and verifying that the unique number has not previously been received, acknowledging receipt of said registration request and sending in response a registration number for said request and the result of a calculation performed by applying the one-way compression function to the global request received, all of which is signed with a private key of the certification authority, the client upon receiving said response from the certification authority, verifying whether the calculation stored locally by the client effectively corresponds to the calculation sent by the server so as to verify the signature of said certification authority.

5. The process for verifying the preservation of the integrity of a sent request according to claim 3, characterized in that in an object management system using the protocol SNMP (Simple Network Management Protocol), the client is an SNMP manager and the server corresponds to an SNMP agent in order to retrieve public information while ensuring that the response returned by said SNMP agent in fact corresponds to the command contained in the request, which request includes a flag and a unique number and is sent by the SNMP manager without protection, while a calculation is then performed by applying a one-way compression function to the entire request, said calculation being stored locally, while the SNMP agent receiving the request verifies that the unique number has not already been received and upon said verification sends in response the requested information associated with the request as well as the result of the calculation performed by applying the one-way compression function to the global request received, signed with an SNMP agent signature key, then upon receiving said response, verifying by the manager whether the calculation stored locally effectively corresponds to the calculation sent by the SNMP agent and if upon verification, using the public key of the SNMP agent, verifying the signature of said SNMP agent.

6. The process for verifying the preservation of the integrity of a sent request according to claim 2, used in the case of an application in which a client who does not possess any private key desires to register the client'"'"'s public key and make the client known to a server acting as a key certification authority, characterized in that the client, with knowledge of the public key of the key certification authority, sends the certification authority an unprotected request constituted by the public key to be registered, his identity, a flag and a unique number, while performing a calculation applying a one-way compression function to the entire request, storing the calculation locally, and the certification authority, upon receiving said request and verifying that the unique number has not previously been received, acknowledging receipt of said registration request and sending in response a registration number for said request and the result of a calculation performed by applying the one-way compression function to the global request received, all of which is signed with a private key of the certification authority, the client upon receiving said response from the certification authority, verifying whether the calculation stored locally by the client effectively corresponds to the calculation sent by the server so as to verify the signature of said certification authority.

7. The process for verifying the preservation of the integrity of a sent request according to claim 2, characterized in that in an object management system using the protocol SNMP (Simple Network Management Protocol), the client is an SNMP manager and the server corresponds to an SNMP agent in order to retrieve public information while ensuring that the response returned by said SNMP agent in fact corresponds to the command contained in the request, which request includes a flag and a unique number and is sent by the SNMP manager without protection, while a calculation is then performed by applying a one-way compression function to the entire request, said calculation being stored locally, while the SNMP agent receiving the request verifies that the unique number has not already been received and upon said verification sends in response the requested information associated with the request as well as the result of the calculation performed by applying the one-way compression function to the global request received, signed with an SNMP agent signature key, then upon receiving said response, verifying by the manager whether the calculation stored locally effectively corresponds to the calculation sent by the SNMP agent and if upon verification, using the public key of the SNMP agent, verifying the signature of said SNMP agent.

8. The process for verifying the preservation of the integrity of a sent request according to claim 1, characterized in that during sending of the request, the flag and the unique number, an additional piece of data is added to the request, said additional piece of data containing a marking key encrypted under a public encryption key of the server, said marking key being decryptable by the server using a corresponding private decryption key to mark the global response, and then verifying of the global response by the client.

9. The process for verifying the preservation of the integrity of a sent request according to claim 8, further comprising deciding in advance when sending a request whether or not non-duplication of the unique number is to be absolutely guaranteed by the server and adding to the request the flag specifying whether or not the server must offer said guarantee as well as the unique number formed, then performing a calculation applying the one-way compression function to the request, flag, and unique number combination, storing the calculation locally, and when the server receives the request, if the client has indicated that the server is to guarantee non-repetition, said server tests whether it can guarantee the non-repetition of the unique number, and indicating with a different flag during the response if the guarantee of non-repetition cannot be given, otherwise the server verifies whether or not said unique number has already been received and then sends an error message if the unique number has already been received, or in the opposite case, performs a calculation applying the one-way compression function to the request, flag, and unique number combination received and includes this calculation in its response, the integrity of the global response being protected by means of the key of the server, whereas the client receiving this response first verifies whether the calculation he has stored effectively corresponds to the calculation sent by the server and if this is the case, then verifies the digital signature or the mark depending on the variant used, the preservation of the integrity of the request sent previously being determined when the calculation and the integrity are verified.

10. The process for verifying the preservation of the integrity of a sent request according to claim 9, used in the case of an application in which a client who does not possess any private key desires to register the client'"'"'s public key and make the client known to a server acting as a key certification authority, characterized in that the client, with knowledge of the public key of the key certification authority, sends the certification authority an unprotected request constituted by the public key to be registered, his identity, a flag and a unique number, while performing a calculation applying a one-way compression function to the entire request, storing the calculation locally, and the certification authority, upon receiving said request and verifying that the unique number has not previously been received, acknowledging receipt of said registration request and sending in response a registration number for said request and the result of a calculation performed by applying the one-way compression function to the global request received, all of which is signed with a private key of the certification authority, the client, upon receiving said response from the certification authority, verifying whether the calculation stored locally by the client effectively corresponds to the calculation sent by the server so as to verify the signature of said certification authority.

11. The process for verifying the preservation of the integrity of a sent request according to claim 9, characterized in that in an object management system using the protocol SNMP (Simple Network Management Protocol), the client is an SNMP manager and the server corresponds to an SNMP agent in order to retrieve public information while ensuring that the response returned by said SNMP agent in fact corresponds to the command contained in the request, which request includes a flag and a unique number and is sent by the SNMP manager without protection, while a calculation is then performed by applying a one-way compression function to the entire request, said calculation being stored locally, while the SNMP agent receiving the request verifies that the unique number has not already been received and upon said verification sends in response the requested information associated with the request as well as the result of the calculation performed by applying the one-way compression function to the global request received, signed with an SNMP agent signature key, then upon receiving said response, verifying by the manager whether the calculation stored locally effectively corresponds to the calculation sent by the SNMP agent and if upon verification, using the public key of the SNMP agent, verifying the signature of said SNMP agent.

12. The process for verifying the preservation of the integrity of a sent request according to claim 1, further comprising deciding in advance when sending a request whether or not non-duplication of the unique number is to be absolutely guaranteed by the server and adding to the request the flag specifying whether or not the server must offer said guarantee as well as the unique number formed, then performing a calculation applying the one-way compression function to the request, flag, and unique number combination, storing the calculation locally, and when the server receives the request, if the client has indicated that the server is to guarantee non-repetition, said server tests whether it can guarantee the non-repetition of the unique number, and indicating with a different flag during the response if the guarantee of non-repetition cannot be given, otherwise the server verifies whether or not said unique number has already been received and then sends an error message if the unique number has already been received, or in the opposite case, performs a calculation applying the one-way compression function to the request, flag, and unique number combination received and includes this calculation in its response, the integrity of the global response being protected by means of the key of the server, whereas the client receiving this response first verifies whether the calculation he has stored effectively corresponds to the calculation sent by the server and if this is the case, then verifies the digital signature or the mark depending on the variant used, the preservation of the integrity of the request sent previously being determined when the calculation and the integrity are verified.

13. The process for verifying the preservation of the integrity of a sent request according to claim 12, used in the case of an application in which a client who does not possess any private key desires to register the client'"'"'s public key and make the client known to a server acting as a key certification authority, characterized in that the client, with knowledge of the public key of the key certification authority, sends the certification authority an unprotected request constituted by the public key to be registered, his identity, a flag and a unique number, while performing a calculation applying a one-way compression function to the entire request, storing the calculation locally, and the certification authority, upon receiving said request and verifying that the unique number has not previously been received, acknowledging receipt of said registration request and sending in response a registration number for said request and the result of a calculation performed by applying the one-way compression function to the global request received, all of which is signed with a private key of the certification authority, the client upon receiving said response from the certification authority, verifying whether the calculation stored locally by the client effectively corresponds to the calculation sent by the server so as to verify the signature of said certification authority.

14. The process for verifying the preservation of the integrity of a sent request according to claim 12, characterized in that in an object management system using the protocol SNMP (Simple Network Management Protocol), the client is an SNMP manager and the server corresponds to an SNMP agent in order to retrieve public information while ensuring that the response returned by said SNMP agent in fact corresponds to the command contained in the request, which request includes a flag and a unique number and is sent by the SNMP manager without protection, while a calculation is then performed by applying a one-way compression function to the entire request, said calculation being stored locally, while the SNMP agent receiving the request verifies that the unique number has not already been received and upon said verification sends in response the requested information associated with the request as well as the result of the calculation performed by applying the one-way compression function to the global request received, signed with an SNMP agent signature key, then upon receiving said response, verifying by the manager whether the calculation stored locally effectively corresponds to the calculation sent by the SNMP agent and if upon verification, using the public key of the SNMP agent, verifying the signature of said SNMP agent.