System, Method and Structure for generating and using a compressed digital certificate

• US 20030041110A1
• Filed: 07/25/2001
• Published: 02/27/2003
• Est. Priority Date: 07/28/2000
• Status: Abandoned Application

• Current Assignee: StoryMail, Inc.
• Original Assignee: StoryMail, Inc.
• Inventors: Baldwin, Robert W., Wenocur, Michael L., Illowsky, Daniel H.
• Application Number:
  US09/912,905
• Publication Number:
  US 20030041110A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/104 Grouping of entities
• 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 63/126 the source of the received data
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

System, method, signal, operating model, and computer program for electronic messaging. Systems and method for providing security for communication of electronic messages, interactive sessions, software downloads, software upgrades, and other content from a source to a receiving device as well as signals used for such communications. Systems, methods, signals, device architectures, data formats, and computer program structures for providing authentication, integrity, confidentiality, non-repudiation, replay protection, and other security properties while minimizing the network bandwidth, computational resources, and manual user interactions required to install, enable, deploy and utilize these security properties. System, device, method, computer program, and computer program product for searching and selecting data and control elements in message procedural/data sets for automatic and complete portrayal of message to maintain message intent. System, device, method, computer program, and computer program product for adapting content for sensory and physically challenged persons using embedded semantic elements in a procedurally based message file.

Claims

1. A computer program product for use in conjunction with a computer system having a server and a client, the computer program product comprising a computer readable storage medium and a computer program mechanism embedded therein, the computer program mechanism, comprising:

a program module that directs the computer system and/or components thereof including at least one or the client or server, to function in a specified manner to provide message communications, the message communications occurring in a computer system hardware architecture neutral and operating system neutral and network transport protocol neutral manner for representing a digital certificate, the program module including instructions for;

A. using a common data object header in substantially all communicated data including communicated certificates;

B. providing a plurality of public keys including a first public key and a second public key in a single certificate, each of said at least first and second public keys being associated with its own purpose;

C. providing a Tag Field that functions as a discriminator of different Certificates issued to the same Subject; and

D. representing a Subject Name and a Certificate Issuer Name in one fixed character set determined by the Version Field.

2. A hardware architecture neutral and operating system neutral and network transport neutral method for representing a digital certificate that enables at least encryption and digital signatures using substantially less storage and bandwidth than conventional digital certificates, said method comprising:

A. using a common data object header in substantially all communicated data including communicated certificates;

B. providing a plurality of public keys including a first public key and a second public key in a single certificate, each of said at least first and second public keys being associated with its own purpose;

C. providing a Tag Field that functions as a discriminator of different Certificates issued to the same Subject; and

D. representing a Subject Name and a Certificate Issuer Name in one fixed character set determined by the Version Field.

3. The method in claim 2, wherein said common data object header includes a plurality of fields including a Type field, a Version field, and a Content-Length field.

4. The method in claim 2, wherein said purpose is selected from the group of purposes consisting of encrypting messages, encrypting session keys, signing messages, signing and encrypting data, and combinations thereof.

5. The method in claim 3, wherein a single byte is used to represent a type and a version for the Type Field the Version Field;

and three bytes are used to represent Content-Length in the Content-Length Field.

6. The method in claim 3, wherein a first single byte is used to represent a type in the Type Field and a second single byte is used to represent a Version in the Version Field;

and two bytes are used to represent Content-Length in the Content-Length Field.

7. The method in claim 3, wherein each said byte has a length selected from the set of byte lengths consisting of 8 bits, 10 bits, 12 bits, 16 bits, 24 bits, 32 bits, 64 bits, 96 bits, and 128 bits.

8. The method in claim 3, wherein the Type field is used to identify that the object is a Certificate.

9. The method in claim 3, wherein the version number is used to represent at least one of the following attributes:

(i) Algorithm used by Certificate Issuer to sign the certificate, (ii) Algorithm to be used with the Subject'"'"'s first public key, (iii) Algorithm to be used the Subject'"'"'s second or subsequent public key, (iv) Length of each public key, (v) Length of Certificate Issuer'"'"'s signature, (vi) parameters for the algorithm, (vii) an exponent to use with RSA public key (viii) Character Set of Subject Name, and (ix) Character Set of Issuer Name.

10. The method in claim 3, wherein the version number is used to represent a plurality of attributes selected from the set of attributes consisting of:

(i) Algorithm used by Certificate Issuer to sign the certificate, (ii) Algorithm to be used with the Subject'"'"'s first public key, (iii) Algorithm to be used the Subject'"'"'s second or subsequent public key, (iv) Length of each public key, (v) Length of Certificate Issuer'"'"'s signature, (vi) parameter(s) for an algorithm, (vii) an exponent to use with RSA public key, (viii) Character Set of Subject Name, and (ix) Character Set of Issuer Name.

11. The method in claim 3, wherein the Version number is used to represent at least four attributes selected from the set of attributes consisting of:

(i) Algorithm used by Certificate Issuer to sign the certificate, (ii) Algorithm to be used with the Subject'"'"'s first public key, (iii) Algorithm to be used the Subject'"'"'s second or subsequent public key, (iv) Length of each public key, (v) Length of Certificate Issuer'"'"'s signature, (vi) parameter(s) for an algorithm, (vii) an exponent to use with RSA public key, (viii) Character Set of Subject Name, and (ix) Character Set of Issuer Name.

12. The method in claim 2, wherein said plurality of public keys include at least two public keys that have the same size (same length) and system parameters.

13. The method in claim 2, wherein said system parameters include an RSA Exponent or Diffie-Helman Generator.

14. The method in claim 2, wherein the Tag Field is treated as an unsigned integer that is incremented with each Certificate issued to the Subject.

15. The method in claim 2, wherein said unsigned integer has a four byte value.

16. The method in claim 14, wherein said treatment as an unsigned integer providing a mechanism for identifying which of a plurality of certificates having the same Subject Name is more recent than another certificate having that Subject.

17. The method in claim 16, wherein this treatment and mechanism replaces the validity dates found with X.509 or X.509-type certificates.

18. The method in claim 2, wherein the Tag Field is treated as ASCII characters to represent the expiration date of the Certificate.

19. The method in claim 18, wherein the Tag Field is treated as four ASCII characters to represent the expiration date of the Certificate as a two digit month number and a two digit year number.

20. The method in claim 2, wherein the Subject Name and Certificate Issuer Name are represented as two-byte characters.

21. The method in claim 20, wherein the two-byte characters comprise two-byte Unicode characters.

22. The method in claim 2, wherein the Version Field is used to indicate any additional fields that are present in the certificate.

23. A hardware architecture neutral and operating system neutral and network transport neutral method for representing a digital certificate that enables at least encryption and digital signatures using substantially less storage and bandwidth than conventional digital certificates, said method comprising the steps of:

using a common data object header in substantially all communicated data including communicated certificates;

providing a plurality of public keys including a first public key and a second public key in a single certificate, each of said at least first and second public keys being associated with its own purpose;

providing a Tag Field that functions as a discriminator of different Certificates issued to the same Subject; and

representing a Subject Name and a Certificate Issuer Name in one fixed character set determined by the Version Field;

said common data object header includes a plurality of fields including a Type field, a Version field, and a Content-Length field;

said purpose is selected from the group of purposes consisting of encrypting messages, encrypting session keys, signing messages, signing and encrypting data, and combinations thereof;

at most two bytes are used to represent a type and a version for the Type Field the Version Field; and

at most three bytes are used to represent Content-Length in the Content-Length Field;

the Type field is used to identify that the object is a Certificate;

the Version number is used to represent a plurality of attributes selected from the set of attributes consisting of;

(i) Algorithm used by Certificate Issuer to sign the certificate, (ii) Algorithm to be used with the Subject'"'"'s first public key, (iii) Algorithm to be used the Subject'"'"'s second or subsequent public key, (iv) Length of each public key, (v) Length of Certificate Issuer'"'"'s signature, (vi) exponent to use with RSA public key, (vii) Character Set of Subject Name, and (vii) Issuer Name;

said plurality of public keys include at least two public keys that have the same size and the same system parameters;

the Tag Field is treated as an unsigned integer that is incremented with each Certificate issued to the Subject;

said treatment as an unsigned integer providing a mechanism for identifying which of a plurality of certificates having the same Subject Name is more recent than another certificate having that Subject;

the Tag Field is treated as ASCII characters to represent the expiration date of the Certificate;

the two-byte characters comprise two-byte Unicode characters; and

the Version Field is used to indicate any additional fields that are present in the certificate.

24. A method for representing a digital certificate, said method comprising:

using a common data object header in all communicated data including communicated certificates;

providing a plurality of public keys including a first public key and a second public key in a single certificate;

providing a first field that functions as a discriminator of different certificates issued to the same subject; and

representing a subject name and a certificate issuer name in one fixed character set determined by a second field.