Public key encryption for groups

CROSS-REFERENCE TO RELATED APPLICATIONS

0001This application is a continuation application entitled to the benefit of, and claims priority to, U.S. patent application Ser. No. 11/022,491, filed Dec. 22, 2004, and is also entitled to the benefit of, and claims priority to provisional U.S. Patent Application Ser. No. 60/531,263 filed on Dec. 22, 2003, and U.S. Patent Application Ser. No. 60/531,695, filed on Dec. 23, 2003, the entireties of which are incorporated by reference herein.

FIELD OF THE INVENTION

0002The present invention relates to a system and a method for securely distributing and identifying computer-generated cryptographic keys.

BACKGROUND OF THE INVENTION

0003Businesses and individuals are increasingly dependent on computers and computer-based electronic communication. More and more businesses are moving toward “paperless” modes of operation, and the convenience of the Internet has resulted in individuals using electronic media for various activities, such as communicating via email, banking, paying bills, investing money and shopping, to name but a few. While businesses and individuals desire the convenience of electronic communication, these entities also want to maintain at least the same level of security that more traditional methods of communication offer. However, more traditional methods of communication are inherently more secure than electronic communication because of the relative ease with which computers may be used to intercept the information being communicated between two or more computers. Accordingly, cryptography techniques have been created to secure information being communicated electronically.

0004Cryptography is the study of sending messages in a secret form so that only those authorized to receive the message be are able to read it. Cryptography may be used for any form of communication, but for the purposes of this application, electronic cryptography will be discussed. For electronic communication, a message is transformed into a secret form using a cryptographic key and then may be transformed back into its original or clear form with a cryptographic key. Examples of cryptographic techniques include symmetric encryption, asymmetric encryption and hashing.

0005Symmetric encryption involves using a single shared key among all users communicating with one another. A message is locked (encrypted) with a key and then the same key is used to unlock (decrypt) the message. In order to protect a message when using symmetric encryption, it is vital to have a secure method to exchange the secret key to all users.

0006Asymmetric encryption involves using a key pair to secure information. A key pair is comprised of a private key (decryption key), which is known only to a single user or a limited group of users, and a public key (encryption key), which may be known by anyone. In order to encrypt and decrypt a message, both the private key and public key of the key pair must be used. For example, a message will be encrypted by a sender using the public key of the intended recipient of the message. Once the recipient receives the encrypted message, his or her private key is used to decrypt the message.

0007Hashing involves transforming an input message of any size into an output or hash value of another, generally smaller, size using a mathematical algorithm. The hash value is known as the message digest. The message digest is a “digital fingerprint” of the input message and serves to maintain integrity of the hashed message by allowing a recipient to verify that the message has not been tampered with since being hashed. Ultimately, in order to maintain security of the encrypted and/or hashed message or information, the key or hash function must be protected.

0008A system using more than one cryptographic technique provides a greater level of security for the information being stored and communicated by the system. However, a system with multiple users and applications such as a network computer system, using multiple cryptographic techniques to protect multiple messages and pieces of information, results in a large volume of keys being generated and utilized. However, a user such as a person, computer, or software application may want to send information and/or other data to a select group in a system with multiple members without having to send it to each member individually. For example, a user may want to send a message to one recipient which distributes the message to all the members of a group as opposed to sending a message to each recipient, especially if there are potentially hundreds or thousands of recipients. It may be desirable for any one of the recipients to be able to open the email, for example, and receive the information independently of the other recipients. It may be desirable to know exactly which recipient opened the message for purposes of maintaining the security and integrity of the system. However, in order to achieve this recipient identification with currently available systems, the information, data and/or message would need to be encrypted with a public key for each group member. Each group member would use its private key to decrypt the information and/or data. Although it is more secure to use individual public and private key pairs, it becomes increasingly more time consuming when there are, for example, hundreds or thousands of members in a group. It is less efficient and slower to generate more key pairs. Therefore, there is a need to increase efficiency yet maintain the security associated therewith. There is also a desire to have the capability to know which member of the group has received, opened or decrypted the information using its private key.

SUMMARY OF THE INVENTION

0009The present invention relates to a system and method for public key encryption for groups. The system comprises a user and a group wherein the group is comprised of a group leader and a group of M members where M is equal to or greater than one.

0010According to the method of the present invention, the group leader generates a group public key and a group leader “master” private key. The group leader creates a personalized or watermarked decryption key, also referred to as an individual private key, for each group member. The individual private key uniquely identifies each group member. The group leader distributes the individual private keys to each of the group members. Each group member receives from a user a message encrypted using the group public key. Each of the group members uses its individual private key to decrypt the encrypted message sent by the user to the group.

0011Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

0012The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:

0013<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a system for public key encryption for groups in accordance with the present invention.

0014<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating the method of public key encryption for groups in accordance with the present invention.

0015<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of a method of distributing keys by the group leader in accordance with the present invention.

0016<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of a computer network system suitable for use with the present invention.

0017<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram illustrating a compact and secure authentication token employing public key encryption for groups in accordance with the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

0018The following description of the preferred embodiment(s) is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses. The present application has broad potential applications and utility, which is contemplated to be adaptable to a wide range of entities for distributing and identifying cryptographic keys within a system, preferably a computer network system. For example, it is contemplated that the present invention would be beneficial for use by any bank that provides online banking services, such as statement review, bill paying and/or investing, to its customers. Additionally, it is contemplated that the system and method of the present invention would be equally beneficial to be used by any retail business that provides online retail services. Further, the system and method of the present invention would be beneficial to any business using computers to store, access, process or use information, particularly if that business uses an intranet for communication between multiple locations. The following description is provided herein solely by way of example for purposes of providing an enabling disclosure of the invention, but does not limit the scope or substance of the invention.

0019<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a system <b>10</b> for public key encryption for groups in accordance with the present invention. Preferably, the system <b>10</b> is a computer network system. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the system <b>10</b> of the present invention comprises a user <b>12</b> and a group <b>14</b>. The group <b>14</b> is comprised of a group leader <b>16</b> and a group of M members <b>18</b>, where M is greater than or equal to one. It is presumed that the group leader <b>16</b> is to be trusted by all group members <b>18</b> and that the public key encryption system is secure. A group member <b>18</b> includes, but is not limited to, a person, a computer, or a software application. The group illustrated in <figref idref="DRAWINGS">FIG. 1</figref> has M members with M equal to or greater than one. There is no limit to the number of users and group members in the system.

0020<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating the method of public key encryption for groups in accordance with the present invention. The group leader <b>16</b> generates a group public key and a group leader “master” private key as shown in step <b>21</b>. The group leader <b>16</b> creates a personalized watermarked or decryption key <b>30</b>, also referred to as an individual private key, for each group member <b>18</b> as shown in step <b>22</b>. The individual private key <b>30</b> uniquely identifies each group member <b>18</b>. The group leader <b>16</b> distributes the individual private keys <b>30</b> to each of the group members <b>18</b> as shown in step <b>23</b>. Once the private keys <b>30</b> have been distributed, communication with the group <b>14</b> may be accomplished by encrypting a message using the group public key. All group members <b>18</b> then receive the message as shown in step <b>24</b>. Finally, each of the group members <b>18</b> uses its individual private key to decrypt the encrypted message sent by the user <b>12</b> to the group <b>14</b> as shown in step <b>25</b>.

0021<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of illustrating a method of distributing a public-private key pair by the group leader <b>16</b> to the group members <b>18</b> in accordance with step <b>23</b> of <figref idref="DRAWINGS">FIG. 2</figref>. The group leader <b>16</b> generates a public key for the group <b>14</b> and the individual private key <b>30</b> for each of the group members <b>18</b>. The group public key and the respective private keys <b>30</b> thus define a unique public-private key pair for each group member <b>18</b>. The group leader <b>16</b> distributes each private key to the respective group member <b>18</b> for which it was generated. Each group member <b>18</b> is then able to decrypt with its own private key <b>30</b>, independently of the other group members <b>18</b>, any message encrypted with the single group public key. However, because each private key <b>30</b> is personalized, the system <b>10</b> discourages unauthorized disclosure of any group member's private key <b>30</b> to unauthorized third parties.

0022The public-private key pair can be generated in accordance with a standard or proprietary asymmetric encryption method. Examples of such asymmetric encryption methods suitable for use with the present invention include, but are not limited to, RSA, Rabin, variants of RSA, and variants of Rabin. However, the following discussion assumes that the public and private keys used are established in accordance with RSA encryption.

0023When the group leader <b>16</b> generates a public-private key pair for use in the RSA encryption method, the group leader <b>16</b> selects two large prime numbers, represented by (p, q) in equations (1) and (2), according to known RSA principles. Preferably, the minimum size of each of p and q is at least 512 bits. N, which represents the first part of the RSA public key for the group, may be computed as follows: <br /><i>N=p×q</i>  (1)<br />φ(<i>N</i>)=(<i>p−</i>1)×(<i>q−</i>1)  (2)

0024The group leader <b>16</b> also generates a pair of public and private exponents (e, d), where e is the second part of the public key for the group <b>14</b> and d is a master private key that is used to manufacture the private keys <b>30</b> for all of the group members <b>18</b>. The exponents e and d are selected such that the product of e and d satisfies equation (3): <br /><i>e×d</i>=1 mod φ(<i>N</i>)  (3)<br /> The private exponent d becomes the group leader's private key. In addition, as stated previously, the group leader <b>16</b> utilizes the private exponent d to create a personalized decryption key <b>30</b>, also referred to as an individual private key, for each of the group members. The decryption keys d_iare computed according to the following equation (4): <br /><i>d</i>_i<i>=d</i>+HASH₃₂(<i>d,N,e</i>,ID_b<i>,Z</i>)×φ(<i>N</i>)  (4)<br /> where + and × are ordinary integer addition and multiplication operations, ID_iis a personal identifier for the specific group member i, such as name or email address; HASH₃₂represents a one-way hash function in which the first 32 bits of the output are utilized; and Z represents a data string that is shared among all group members. The personal identifier ID_imay be any unique value, but is preferably a meaningful data string such as a user's name or email address. The hash algorithm may be any standard or proprietary hash algorithm. An example of a suitable hash algorithm includes, but is not limited to, SHA-1. In the present embodiment, the hash algorithm preferably provides an output of at least 32 bits. However, it is within the scope of the present invention that larger numbers of output bits (such as 64 or the like) may likewise be used for even greater security, but that a hash function that produces at least that many bits will then be required. Z may be any additional control data, but unlike the ID_iis not usually personalized to the individual user. An example of control data that might be used for Z is a timestamp.

0025A first group member (Group Member 1) would thus have a private key computed as shown in equation (5): <br /><i>d</i>_l<i>=d</i>+HASH₃₂(<i>d,N,e</i>,ID_l<i>,Z</i>)×φ(<i>N</i>)  (5)<br /> where ID₁is the personal identifier for Group Member 1 such as name or email address.

0026The ID is the factor or component that makes each decryption key unique. However, this value is included in the hash function so that this identifying information is preferably not explicitly in the key.

0027It will be noted that the hash function in equation (4) utilizes both parts of the public key (N, e) for the group. It may be appreciated that the individual private keys may alternatively be computed instead by hashing the public key certificate Cert_N, which incorporates both N and e therein, according to equation (6): <br /><i>d</i>_i<i>=d</i>+HASH₃₂(<i>d</i>,Cert_N,ID_i<i>,Z</i>)×φ(<i>N</i>)  (6)

0028Once the individual private keys d_ihave been computed according to one of the foregoing approaches, the group leader <b>16</b> then distributes the individual private keys d_ito the i-th member in the group in a secure manner. The group leader retains the master decryption key d. There are any number of ways to distribute keys as is known to one of ordinary skill in the art. If the system and method of the present invention are to be utilized for “external” communications between one certifying entity and another, then a preferred way is for the group leader <b>16</b> to distribute private keys d_ialong with a group public key certificate Cert_N, which as noted previously incorporates both parts (N, e) of the public key for the group. The public key certificate Cert_Nidentifies the purpose of the private key.

0029In operation, a user <b>12</b> uses the asymmetric encryption algorithm for which the keys were established to encrypt a message for the group <b>14</b>, using the group's public key (N, e), and sends it to the group <b>14</b>.

0030In the instance that RSA encryption is used, the message is encrypted by the user in accordance with equation (7). <br /><i>C=T</i>^emod <i>N</i>  (7)<br /> wherein <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0031">C is the encrypted message,</li><li id="ul0002-0002" num="0032">T is the unencrypted message, and</li><li id="ul0002-0003" num="0033">e and N are defined as above.</li></ul></li></ul>

0034Likewise, the group leader and each of the group members <b>18</b> may decrypt the encrypted message using RSA decryption, independently of the other group members, using their personalized decryption keys or individual private keys in accordance with equations (8) and (9), respectively. <br /><i>T=C</i>^dmod <i>N</i>  (8)<br /><i>T=C</i>^dimod <i>N</i>  (9)<br /> wherein <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0035">T is the unencrypted message,</li><li id="ul0004-0002" num="0036">C is the encrypted message, and</li><li id="ul0004-0003" num="0037">d, d_iand N are as defined above.</li></ul></li></ul>

0038A group member <b>18</b> can correctly recover the message because of equation (10) set forth below. <br /><i>C</i>^dimod <i>N=C</i>^d<i>×C</i>^HASH^{<sub2>32</sub2>}^{(N,e,IDi,Z)×φ(N)}mod <i>N=T</i>  (10)<br /> wherein <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0039">C^HASH^{<sub2>32</sub2>}^{(N,e,IDi,Z)×φ(N)}=1 mod N.</li></ul></li></ul>

0040Other asymmetric decryption methods such as RSA, Rabin, variants of RSA, and variants of Rabin can be used. Preferably, an asymmetric encryption method such as RSA decryption is used.

0041In the event of a key being disclosed to a third party, the group leader <b>16</b> may use p and q to identify the group member <b>18</b> who disclosed the decryption key so the group leader <b>16</b> knows which group member opened it. This can be accomplished by searching the list of member-decryption key pairs or recomputing the decryption key according to equation (6) to see which ID_iwill result in a d_ithat matches the disclosed private key. Thus, an advantage of the system and method of the present invention is that by sending a personalized decryption or individual private key, it is possible to identify the group member <b>18</b> who is the discloser.

0042An application in which the system and method of the present invention may be employed is for compact and secure authentication tokens in a computer network system.

0043<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of a computer network system <b>40</b> suitable for use with the present invention. The computer network system <b>40</b> is comprised of a user <b>42</b>, a webserver <b>44</b>, a login authentication server <b>46</b>, an application server <b>48</b>, a server <b>50</b>, and database <b>52</b>. The user <b>42</b> logs into the computer network system <b>40</b> and enters its userid and password. This information is transmitted by the webserver <b>44</b> to the login authentication server <b>46</b> which authenticates the information and creates a token which is transmitted to the webserver <b>44</b>. The webserver <b>44</b> transmits the token to the application server <b>48</b>. The token should be verifiable by the application server <b>48</b> of its origin. The application server <b>48</b> communicates with the mainframe <b>50</b> to provide the user with the requested service.

0044The token that is created by the login authentication server <b>46</b> is referred to as an authentication token. It is typically issued as a cookie. The token has no size limitation. However, it is preferable for the token to be as compact as possible. One of ordinary skill in the art will recognize that the degree of compaction depends upon the encryption method employed. Additionally, the token may be encrypted to ensure the confidentiality of its contents. The token may also be wrapped with additional information and/or data. The token is signed and encrypted with a token encryption key as illustrated in <figref idref="DRAWINGS">FIG. 5</figref>. While the login authentication server <b>46</b> needs to sign the token only once, it may encrypt the token more than once. The exact number of encryption operations is determined by the specific encryption technique used. Thus, it is preferred to use the system and method of public key encryption for groups of the present invention. If there is more than one application server <b>46</b>, all application servers share the same public key. With this approach, a token is signed and then encrypted only once regardless of the number of application servers. If an attacker were to successfully break into an application server <b>46</b> and steal the token key, the confidentiality of the tokens would be compromised and in such situation, it would be desirable to be able to identify with ease which token key has been compromised. This is an advantage offered with the system and method of the present invention. With this system and method, there will be only one public encryption key for all servers. However, each application server <b>48</b> will have a personalized decryption key or individual private token key from which one cannot determine the decryption key of another application server. These private keys, although different, perform the same function, namely to correctly decrypt a message using the same public key. Since the decryption keys are personalized, it makes it possible to identify a compromised application server from the information contained in the compromised decryption key.

0045The system of public key encryption for groups of the present invention when used for authentication tokens preferably employs an asymmetric encryption method. More preferably, RSA encryption is used. If RSA encryption is used to generate an authentication token, a token is first signed using the standard RSA signature scheme. The signed token is expanded due to the attached RSA signature. The signed token is then encrypted using the method of public key encryption for groups of the present invention. To validate the authentication token, the encrypted signed token is decrypted by a group member using its individual private key, and the decrypted token is verified to confirm the authenticity of the token by using the RSA signature process.

0046It will therefore be readily understood by those persons skilled in the art that the present invention is susceptible of broad utility and application. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and the foregoing description thereof, without departing from the substance or scope of the present invention. Accordingly, while the present invention has been described herein in detail in relation to its preferred embodiment, it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made merely for purposes of providing a full and enabling disclosure of the invention. The foregoing disclosure is not intended or to be construed to limit the present invention or otherwise to exclude any such other embodiments, adaptations, variations, modifications and equivalent arrangements.