Universal signature object for digital data

• US 20020048372A1
• Filed: 10/16/2001
• Published: 04/25/2002
• Est. Priority Date: 10/19/2000
• Status: Abandoned Application

• Current Assignee: Message Secure Corp. (BAE Systems Plc)
• Original Assignee: Message Secure Corp. (BAE Systems Plc)
• Inventors: Fong, Kok-Khuan, Madhav, Raj Maharjan, Toh, Eng-Whatt, Teo, Kok-Hoon
• Application Number:
  US09/981,588
• Publication Number:
  US 20020048372A1
• Time in Patent Office: Days
• US Class Current: 380/285
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• 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/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps

Abstract

Systems, methods and computer-readable media for generating and utilizing a universal signature object (100). A universal signature object (100) binds a digital signature (112) to digital data (200), regardless of the file format of the version of the digital data (200). A signing program (400) generates a universal signature object (100) or appends a digital signature (122) to a previously generated universal signature object (100). A universal-signature-object viewer (600) utilizes a universal signature object (100) to display information contained in the universal signature object (100) or generated from the universal signature object (100).

Claims

1. A computer-readable medium storing a universal signature object for binding a digital signature to digital data, the universal signature object comprising:

at least one version of the digital data, wherein each version has a file format;

a digital signature of signature data, wherein the signature data is a function of the digital data; and

information concerning an application compatible with the file format of at least one of the versions.

2. The universal signature object of claim 1 wherein the file format of at least one version is a native file format of the digital data.

3. The universal signature object of claim 1 wherein the file format of at least one version is compatible with more than one application.

4. The universal signature object of claim 1 wherein the file format of at least one version is an alternate file format.

5. The universal signature object of claim 4 wherein the information concerning an application compatible with the file format of at least one of the versions includes information concerning an alternate application compatible with the alternate file format.

6. The universal signature object of claim 5 wherein the information concerning the alternate application includes an embedded executable file of the alternate application.

7. The universal signature object of claim 4 wherein the signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the digital signature.

8. The universal signature object of claim 4 wherein the digital signature is timestamped.

9. The universal signature object of claim 4 further comprising:

a public key, corresponding to a private key used to generate the digital signature.

10. The universal signature object of claim 4 further comprising an additional digital signature by an additional signatory of additional signature data, wherein the additional signature data is a function of the digital data.

11. The universal signature object of claim 10 wherein the additional signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the additional digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the additional digital signature.

12. The universal signature object of claim 10 wherein the additional digital signature is timestamped.

13. The universal signature object of claim 1 wherein the signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the digital signature.

14. The universal signature object of claim 1 wherein the information concerning an application compatible with the file format of at least one of the versions includes information identifying the application compatible with the file format of at least one of the versions.

15. The universal signature object of claim 1 wherein the information concerning an application compatible with the file format of at least one of the versions includes an executable file of the application compatible with the file format of at least one of the versions.

16. The universal signature object of claim 1 wherein the digital signature is timestamped.

17. The universal signature object of claim 1 further comprising:

a public key, corresponding to a private key used to generate the digital signature.

18. The universal signature object of claim 1 further comprising an additional digital signature by an additional signatory of additional signature data, wherein the additional signature data is a function of the digital data.

19. The universal signature object of claim 18 wherein the additional signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the additional digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the additional digital signature.

20. The universal signature object of claim 18 wherein the additional digital signature is timestamped.

21. The universal signature object of claim 18 further comprising:

a public key corresponding to the private key used to generate the additional digital signature.

22. The universal signature object of claim 1 further comprising:

use-permission information regarding permitted use of the universal signature object.

23. The universal signature object of claim 1 wherein the universal signature object is compressed.

24. The universal signature object of claim 1 wherein the universal signature object is encrypted.

25. The universal signature object of claim 1 further comprising:

a universal-signature-object viewer for utilizing the universal signature object.

26. The universal signature object of claim 25 wherein the universal-signature-object viewer for utilizing the universal signature object comprises:

an application launching means for launching the application compatible with the file format of at least one of the versions; and

a viewer means for displaying information concerning the universal signature object.

27. The universal signature object of claim 1 further comprising:

a signing program for modifying the universal signature object to include an additional digital signature.

28. The universal signature object of claim 1 wherein the application compatible with the file format of at least one of the versions includes said version.

30. The universal-signature-object viewer of claim 29 wherein the information concerning the universal signature object displayed by the viewer means comprises at least one data field from the group of data fields comprising:

use-permission information regarding permitted use of the universal signature object;

a list of items contained within the universal signature object;

at least one version of the digital data;

a digital signature;

a name of a signatory of the digital signature;

a timestamp of the digital signature; and

digital signature verification results.

31. The universal-signature-object viewer of claim 29 further comprising:

an edit disabling means for disabling editing capabilities of the application.

32. The universal-signature-object viewer of claim 29 wherein the application launching means searches a computer system on which the universal-signature-object viewer operates to locate the application compatible with the file format of at least one of the versions.

33. The universal-signature-object viewer of claim 29 wherein the information concerning an application compatible with the file format of at least one of the versions comprises an executable file of the application compatible with the file format of at least one of the versions.

34. The universal-signature-object viewer of claim 29 wherein the application compatible with the file format of at least one of the versions operates under the control of the universal-signature-object viewer.

35. The universal-signature-object viewer of claim 29 further comprising:

a verification means for verifying the digital signature.

36. The universal-signature-object viewer of claim 35 wherein the verification means verifies the digital signature against an archived copy of the digital signature obtained from a transaction server.

37. The universal-signature-object viewer of claim 29 further comprising:

a printing means for providing a print copy of information concerning the universal signature object.

38. The universal-signature-object viewer of claim 37 wherein the information concerning the universal signature object comprises at least one data field selected from the group of data fields comprising:

use-permission regarding permitted use of the universal signature object;

a list of items contained within the universal signature object;

at least one version of the digital data;

a digital signature;

a name of a signatory of the digital signature;

a timestamp of the digital signature; and

digital signature verification results.

39. The universal-signature-object viewer of claim 37 wherein the print means digitally watermarks the print copy.

40. The universal-signature-object viewer of claim 29 wherein:

the universal signature object further comprises at least one additional digital signature;

the digital signatures are timestamped; and

the viewer means displays the digital signature in timestamp order.

41. The universal-signature-object viewer of claim 29 wherein the universal-signature-object viewer operates within a browser application.

42. The universal-signature-object viewer of claim 29 wherein the universal-signature-object viewer is incorporated into the universal signature object.

43. The universal-signature-object viewer of claim 42 wherein the universal signature object is a standalone application.

44. The universal-signature-object viewer of claim 29 wherein the universal-signature-object viewer is a network application accessible via a network connection.

46. The method of claim 45 wherein the signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the digital signature.

47. The method of claim 45 wherein the universal signature object further comprises:

a timestamp of the digital signature.

48. The method of claim 47 wherein the signatory verifies the authenticity of the private-public key pair and provides the timestamp.

49. The method of claim 45 further comprising the steps of:

requesting a tracking number from a transaction server; and

transmitting at least a copy of the digital signature to the transaction server.

50. The method of claim 45 wherein at least one of the versions of the digital data has a non-native file format.

51. The method of claim 45 wherein the universal signature object further comprises:

the signatory'"'"'s public key.

52. The method of claim 45 wherein the universal signature object farther comprises:

use-permission information regarding the use of the universal signature object.

53. The method of claim 45 wherein the universal signature object further comprises:

a universal-signature-object viewer for utilizing the universal signature object.

54. The method of claim 53 wherein the universal-signature-object viewer for utilizing the universal signature object comprises:

an application launching means for launching the application compatible with the file format of at least one of the versions; and

a viewer means for displaying information concerning the universal signature object.

55. The method of claim 45 wherein the universal signature object further comprises:

a signing program for modifying the universal signature object to include an additional digital signature.

56. The method of claim 45 further comprising the step of:

in response to the universal signature object of the digital data existing;

using the signatory'"'"'s private key to generate a digital signature of signature data, wherein the signature data is a function of the digital data; and

modifying the universal signature object to include an additional digital signature.

57. The method of claim 56 wherein the signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the digital signature.

58. The method of claim 57 wherein the universal signature object further comprises:

a timestamp of the digital signature.

59. The method of claim 57 further comprising the steps of:

requesting a tracking number from a transaction server; and

transmitting at least a copy of the digital signature to the transaction server.

60. The method of claim 57 wherein the universal signature object further comprises:

the signatory'"'"'s public key.

29. A universal-signature-object viewer for utilizing a universal signature object comprising at least one version of digital data, wherein each version has a file format;

a digital signature of signature data, wherein the signature data is a function of the digital data; and

information concerning an application compatible with the file format of at least one of the versions, the universal-signature-object viewer comprising;

an application launching means for launching the application compatible with the file format of at least one of the versions; and

a viewer means for displaying information concerning the universal signature object.

45. A method for digitally signing digital data, comprising:

accessing a signatory'"'"'s private-public key pair;

authenticating the private-public key pair; and

in response to a universal signature object of the digital data not existing;

using the signatory'"'"'s private key to generate a digital signature of signature data, wherein the signature data is a function of the digital data; and

generating the universal signature object of the digital data, the universal signature object comprising;

at least one version of the digital data, wherein each version has a file format;

the digital signature; and

information concerning an application compatible with the file format of at least one of the versions.

61. A signing program for binding a digital signature to digital data, the signing program comprising:

a key-accessing means for accessing a signatory'"'"'s private-public key pair;

a key-verification means for authenticating the private-public key pair;

a universal-signature-object generating means for, in response to a universal signature object of the digital data not existing;

using the signatory'"'"'s private key to generate a digital signature of signature data, wherein the signature data is a function of the digital data; and

generating the universal signature object of the digital data, the universal signature object comprising;

at least one version of the digital data, wherein each version has a file format;

the digital signature; and

information concerning an application compatible with the file format of at least one of the versions.

62. The signing program of claim 61 wherein the signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the digital signature.

63. The signing program of claim 61 wherein the universal signature object further comprises:

a timestamp of the digital signature.

64. The signing program of claim 61 further comprising:

a transaction tracking means for requesting a tracking number from a transaction server.

65. The signing program of claim 64 wherein the transaction tracking means transmits the digital signature to the transaction server.

66. The signing program of claim 61 wherein at least one of the versions of the digital data has a non-native file format.

67. The signing program of claim 61 wherein the universal signature object further comprises:

the signatory'"'"'s public key.

68. The signing program of claim 61 wherein the universal signature object further comprises:

use-permission information regarding the use of the universal signature object.

69. The signing program of claim 61 wherein the universal signature object further comprises:

a universal-signature-object viewer for utilizing the universal signature object.

70. The signing program of claim 69 wherein the universal-signature-object viewer for utilizing the universal signature object comprises:

an application launching means for launching the application compatible with the file format of at least one of the versions; and

a viewer means for displaying information concerning the universal signature object.

71. The signing program of claim 61 wherein the universal signature object further comprises:

a signing program for modifying the universal signature object to include an additional digital signature.

72. The signing program of claim 61 wherein the universal-signature-object generating means further performs the step of:

in response to the universal signature object of the digital data existing;

using the signatory'"'"'s private key to generate a digital signature of signature data, wherein the signature data is a function of the digital data; and

modifying the universal signature object to include an additional signature.

73. The signing program of claim 72 wherein the signature data is selected from the group comprising:

one of the versions of the digital data;

the universal signature object, prior to inclusion of the digital signature;

a hash of one of the versions of the digital data; and

a hash of the universal signature object, prior to inclusion of the digital signature.

74. The signing program of claim 72 wherein the universal signature object further comprises:

a timestamp of the digital signature.

75. The signing program of claim 72 further comprising:

a transaction tracking means for requesting a tracking number from a transaction server.

76. The signing program of claim 75 wherein the transaction tracking means transmits the digital signature to the transaction server.

77. The signing program of claim 61 wherein the signing program is integrated with a primary application to provide digital signing capability for the files utilized by the primary application.

78. The signing program of claim 61 wherein the signing program operates within a browser application.

79. The signing program of claim 61 wherein the signing program is a standalone application.