Verification protocol

Abstract

A digital signature verification protocol utilises a pair of signature components incorporating a pair of private keys, one of which is a long term key and the other of which is a short term key.

Description

[0002] The present invention relates to data transmission and more particularly to data transmission systems to verify the identity of the parties transmitting data.

[0003] It is well known to communicate data electronically between a pair of correspondents, typically a pair of computer terminals or a personal card and a computer terminal. Widespread use is made of such communication in the banking environment in order to conduct transactions.

[0004] To maintain the integrity of such transactions, it is necessary to implement a system in which the identity of the parties can be verified and for this purpose a number of signature protocols have been developed. Such protocols are based upon El Gamal signature protocols using the Diffie Hellman public key encryption scheme. One commonly used cryptographic scheme is that known as RSA but to obtain a secure transmission, a relatively large modulus must be used which increases the band width and is generally undesirable where limited computing power is available. A more robust cryptographic scheme is that known as the elliptic curve cryptosystem (ECC) which may obtain comparable security to the RSA cryptosystems but with reduced modulus.

[0005] Basically, each party has a private key and a public key derived from the private key. Normally for data transfer, a message is encrypted with the public key of the intended recipient and can then be decrypted by that recipient using the private key that is known only to the recipient. For signature and verification purposes, the message is signed with the private key of the sender so that it can be verified by processing with the public key of the stated sender. Since the private key of the sender should only be known to the sender, successful decryption with the sender's public key confirms the identity of the sender.

[0006] The El Gamal signature protocol gets its security from the difficulty in calculating discrete logarithms in a finite field. El Gamal-type signatures work in any group including elliptic curve groups. For example given the elliptic curve group E(Fq) then for P ε E(Fq) and Q=aP the discrete logarithm problem reduces to finding the integer a. With an appropriately selected underlying curve, this problem is computationally infeasible and thus these cryptosystems are considered secure.

[0007] Various protocols exist for implementing such a scheme. For example, a digital signature algorithm DSA is a variant of the El Gamal scheme. In this scheme a pair of correspondent entities A and B each create a public key and a corresponding private key. The entity A signs a message m of arbitrary length with his private key. The entity B can verify this signature by using A's public key. In each case however, both the sender, entity A, and the recipient, entity B, are required to perform a computationally intensive operations, typically an exponentiation, to generate and verify the signature respectively. Where either party has adequate computing power this does not present a particular problem but where one or both the parties have limited computing power, such as in a “Smart card” application, the computations may introduce delays in the signature and verification process.

[0008] There are also circumstances where the Signor is required to verify its own signature. For example in a public key cryptographic system, the distribution of keys is easier than that of a symmetric key system. However, the integrity of public keys is critical. Thus the entities in such a system may use a trusted third party to certify the public key of each entity. This third party may be a certifying authority (CA), that has a private signing algorithm ST and a verification algorithm VT assumed to be known by all entities. In its simplest form the CA provides a certificate binding the identity of an entity to its public key. This may consist of signing a message consisting of an identifier and the entity's authenticated public key. From time to time however the CA may wish to authenticate or verify its own certificates.

[0009] As noted above, signature verification may be computationally intensive and to be completed in a practical time requires significant computing power. Where one of the correspondents has limited computing capacity, such as the case where a “smart card” is utilized as a cash card, it is preferable to adopt a protocol in which the on card computations are minimized. Likewise, where a large number of signatures are to be verified, a rapid verification facility is desirable.

[0010] It is therefore an object of the present invention to provide a signature and verification protocol that facilitates the use of limited computing power for one of the correspondents and verification of the signature.

[0011] In general terms, the present invention provides a method of generating and verifying a signature between a pair of correspondents each of which shares a common secret integer comprising the steps of generating from a selected integer a session key at one of the correspondents, selecting a component of sold session key and encrypting a message with said selected component, generating a hash of said selected component, and computing a signature component including said common secret integer, said hash and said selected integer and forwarding the signature component, encrypted message and has to the other correspondent. The selected integer may be recovered for the signature component using the common secret integer and the session key encrypted. The balance of the recovered session key may then be used to provide authorized and, optionally, a challenge to the recipient.

[0012] An embodiment of the invention will now be described by way of example only, with reference to the accompanying drawings, in which

[0013] FIG. 1 is a schematic representation of a data transmission system; and

[0014] FIG. 2 is a schematic flow chart of a signature verification protocol.

[0015] FIG. 3 is a schematic flow chart of an alternative protocol; and

[0016] FIG. 4 is a schematic flow chart of a further protocol

[0017] Referring therefore to FIG. 1, a data transmission system 10 includes a plurality of correspondents 12a, 12b, . . . 12t, (generically referred to by reference numeral 12) interconnected by a data transmission link 16. The correspondents 12 are typically electronic terminals having a limited computing capacity, and in the present example, the correspondent 12 may be considered to be in the form of a “smart card” having limited memory and computing capacity. The data transmission system 10 also includes a correspondent 14 that in this embodiment may be a terminal in a banking institution, connected by the transmission link 16 to respective ones of the terminals 12. Such connection will typically be on a transient basis as correspondents 12 periodically access the system 10 but may be permanent connections.

[0018] The correspondents 12,14 each have encryption units indicated at 18,20 that establish a common cryptosystem. In the example provided, it will be assumed that the encryption units 18,20 implement an elliptic curve cryptosystem with established underlying curve parameters and seed point P on that curve.

[0019] Each of the correspondents 12 also includes a memory 22 in which is embedded a respective secret integer d used as a long term private key by the correspondent 12 for multiple transactions. The correspondent 14 has a public key QB and a number of precomputed values of dQB is stored in an addressable memory 24 on the correspondent 12 to facilitate signature

[0020] A number generator 26 is included on each card to generate a statistically unique but unpredictable integer at the start of each session for use as a short term private key that will change at each transaction.

[0021] The correspondent 14 similarly includes a memory 28 having a databank which stores the respective long term private key d of each of the correspondents 12 and correlates it to the identity of the respective one of the correspondents 12.

[0022] To Initiate a verification protocol, one of the correspondents 12 formulates a message m and generates a random integer k from the generator 26 which acts as a short term private key during the transmission session. Using the seed point P, it computes a session key r which corresponds to kP. kP is in fact a point on the underlying curve with coordinates (x,y).

[0023] A first signature component e is generated by encrypting a message m using the binary representation of the x coordinate so that e=Ex(m).

[0024] A second signature component e′ is generated by hashing the x coordinate of the session key r such that e′=h(x). A suitable cryptographic hash function is used such as the secure Hash Algorithm (SHA-1) proposed by the U.S. National Institute for Standards and Technology (NIST).

[0025] A third signature component s is generated of the general form s=ae+k (mod n) where a is the long term private key, e is a value derived by hashing a message string and k is the short term private key. In this embodiment the signature component s has the specific form

s=d.h (dQB//e′)+k (mod n)

[0026] where n is the order of the underlying curve. The signature component s is obtained by retrieving the precomputed value of dQB from memory 24 of correspondent 12 and concatenating it with the hash value of x and then hashing the result.

[0027] A signature including signature components s, e and e′ is then forwarded to the correspondent 14. Upon receipt the correspondent 14 retrieves the long term private key d from the databank 28 based on the indicated identity of the correspondent 12 and together with its own public key, QB and the received component e′ computes the hash h=dQB//e′. From that and the signature component s, a value k′ can be obtained which should correspond to k.

[0028] Utilizing the computed value of k and the seed point P, a function associated with the computed value of the short term key, namely the value of the x coordinate of kP, x′, can be obtained. The computed value of x′ is then hashed and a comparison made to verify that the resultant value of the hash corresponds with the received value of e′. At that stage, verification of the correspondents has been obtained and the only exponentiation required is the initial computation of kP.

[0029] The computation of the session key r and the subsequent use of a portion of that session key enables a secure authorization to be returned by the correspondent 14. Having computed the value of the coordinate x, the correspondent 14 can then compute the coordinate y and use it to encrypt a message m′ as authorization. Thus the correspondent 14 responds to the correspondent 12 by forwarding a message including Ey(m′). Upon receipt, the correspondent 12 knows they coordinate of the session key R and can recover the message m′ that conveniently includes a challenge. The correspondent 12 decrypts the message and returns the challenge to the correspondent 14 so that the correspondents are then verified and synchronized. Further messages may then be transferred between the correspondents 12,14 using the session key r as the encryption key.

[0030] It will be seen, therefore, that in the above protocol, a pair of keys are utilised and the correspondent 14 retains control of one of the keys that provides a long term private key and utilizes these to recover the short term session key computed by the correspondent 12. The recovered short term key can then be used for verification with other transmitted signature components, e.g. by checking e′.

[0031] Alternatively, the structure of the recovered value of the key could be indicative of verification, for example, by the pattern, number or distribution of digits so that the recovered value may be compared with predetermined parameters for verification. By virtue of the relationship between the recovered component and the information forwarded, the other portion of the session key can be utilized to reply and establish synchronization.

[0032] In this embodiment, it will be noted that the signature verification is performed in a computationally expedient manner without exponentiation and so may be performed relatively quickly.

[0033] It will also be noted that the system 10 may function as a public key encryption system between the correspondents 12 or correspondents 12, 14 but where rapid verification is required, it may use the attributes of a symmetric key protocol.

[0034] As will be exemplified below, alternative signatures may be used and generally any El Gamal signing equation may be used. An alternative embodiment of signature verification may be implemented using the DSS signature protocol, as shown in FIG. 3. In this protocol, a short term public key r is derived by expowienting the group generator α with a random integer k, i.e. r=αk. (If an elliptic curve cyptosystem is utilised, then the exponentiation is performed by a k fold addition of the point P so that r=kP).

[0035] With the DSS protocol, the signature component s is of the form

s=k −1 (h(m)+dr) (mod n)

[0036] where d is a long tern private key and m is the message. The values of signature components s, r and the message m is forwarded by the correspondent 12 to the correspondent 14.

[0037] Correspondent 14 shares the long term private key d and so can retrieve the short term private key k from the identity k=s (h(m)+dr).

[0038] As the values of r, m and s are sent and, d is known by the correspondent 14, k can be computed.

[0039] As noted above, k can be arranged to have a specific structure, such as a specific pattern or a certain number of 1's and this may be used as verification. Alternatively, the verification may be checked by computing a value of r from the recovered k (i.e. r=αk) and comparing it with the transmitted r. This step requires an exponentiation and therefore is computationally more demanding but may be utilised where desirable.

[0040] Again, by sharing the long tern private key d, a verification can be performed in a simple yet effective manner by extracting the short term private key, k.

[0041] In each of the above examples, the signature verification is performed between a pair of correspondents. The characteristics of the protocol may be utilised to verify a signature issued by a certifying authority CA, such as a bank, constituted by correspondent 14.

[0042] In this embodiment, the correspondent 14 receives a certificate purporting to have been issued by it. The correspondent 14 verifies the authenticity of the certificate using the long term private key d to extract the short term private key k. The structure of the private key k can then be checked or the key k used to derive information relating to the short tern public key, r, included in the message. Again, verification can be obtained without extensive computation in an expedient manner and allows the verification of certificates received by the correspondent 14, i.e. a bank or financial institution.

[0043] This embodiment may be exemplified using the digital signature algoritbm,DSA, which is a special case of the El Gamal signature scheme. For key generation in the El Gamal signature scheme, each correspondent A and B creates a public key and corresponding private key. In order to set up the underlying cryptosystem in a group Fp, the entities A and B select primes p and q such that q divides p−1. A generator g is selected such that it is an element of order q in Fp and the group used is {g0, g1, g2, . . . gq−1}.

[0044] In the digital signature algorithm (DSA) key generation is performed by selecting a random integer din the interval [1, q−1] and computing a long term public key y=gd mod p. The public key information is (p, q, g, y) and the long term private key is d, while in the general El Gamal scheme the public key information is (p, g, y) and the private key is d.

[0045] In a DSA signature scheme the signature components r and s are given by:

r= (gk mod p)mod q; and

s=k −1 (h(m)+dr)mod q

[0046] where typically:

[0047] d is a random integer, the signors long term private key and is typically 160-bits;

[0048] p is typically a 1024-bit prime;

[0049] q is a 160-bit prime where q divides p−1;

[0050] g is the generator such that y=gd mod p;

[0051] h(m) is typically a SHA-1 hash of the message m;

[0052] k is a randomly chosen 160-bit value for each signature; and

[0053] the signature for m is the pair (r, s).

[0054] Normally to verify A's signature (r, s) on the message m, the recipient B should obtain A's authentic public key information (p, q, g, y), and verify that 0<r<q and 0<s<q. Next the values w=s−1 mod q and h(m) are computed. This is followed by computing uI=w h(m) mod q and u2=r w mod q and v=(gu1yu2 mod p) mod q. The signature is accepted if and only if v=r. It may be seen therefore that in some cases if the owner of the signature wants to verify its own signature at a later stage it may be time consuming to retrieve the public key information and perform the steps above, which include a pair of exponentiations.

[0055] A fast signature verification by the certifying authority CA may be implemented as shown in FIG. 4 using the long term private key d of the certifying authority as the verifier. In this case the original signor has knowledge of p, q, g, y, h(m), r and s. Thus the verifier need only recover the short term private key k used in the signature and verify the value of k thus obtained in order to verify the signature. The verifier thus calculates z=(h(m)+dr) mod q . The value z−1 is calculated by inverting z mod q and used to compute k′−1=s(z−1)mod q. k′ may be calculated by inverting k′−1 mod q. The verifier then evaluates r=gk* mod p mod q and verifies that k=k′. Thus it may be seen that this verification step uses the long term private key d rather than the long term public key y to avoid exponentiation. Naturally many of the calculations above can be sped up using pre-computed tables.

[0056] An alternate El Gamal signature method is shown in FIG. 5 and has signature components (s, e) where:

r=gk mod p;

e=h (m||r) where || indicates concantenation; and

s= (de+k)mod p

[0057] where p is a large public prime, g is a public generator, m is a message, h is a hash function, d is a long term private key, y=gd mod p is the corresponding long term public key and k is a secret random integer used as a short term private key.

[0058] To generate a certificate, the correspondent 14 signs a message m containing the identity of one of the correspondents 12 and that correspondents public key. The message is signed using the long term public key and a short term session key k of the correspondent 14 and a certificate issued to the correspondent 12 including the signature components s,e. The public information is retained by the correspondent 14. The certificate may be used by the correspondent 12 and verified by recipients using the public key of correspondent 14.

[0059] When a certificate is presented to the correspondent 14, a rapid verification may be obtained using the long tern private key d.

[0060] In fast signature verification using the private key d the public information of p, g, y, h, m, r, e and private key d is known by the verifier. Thus the verifier need only recover the short term private key k and verify k in order to verify the signature. The verifier calculates k′=(s−de) mod p, r′=gk* mod p and e′=h(m||r′e). If e=e′ this verifies k=k′. Only one exponentiation is required in this verification to facilitate the process. Alternatively the characteristics of the recovered value of k may be sufficient to satisfy verification as discussed above.

[0061] Thus it may be seen that a particular advantage of the present invention is where a signor signs data which for example may reside on the signors computer. This can be later verified without use of the correponding public key, instead the signor can use its private key to verify the data. This is also very useful for some applications with limited computational power such as smartcards.

[0062] In a data communication system that includes a certifying authority, the certifying authority (CA) or key distribution centre would sign data frequently before it is installed into the various communications systems and then could verify the signatures later. Thus the CA does not require the public key information to verify the signatures but simply uses the long term private key to verify, as all the other parameters are stored within the secure boundary of the signor. It will also be noted that as the long term private key d is used it is not necessary to retain the short tern private key k so that the overhead associated with the system is minimised.

[0063] A further application is in the verification of software such in pay-per-use software applications. A request for access to a server may be controlled by a certificate issued by the server and presented by the user of the software. The authenticity of the certificate may then be verified using the servers private key as described above in an expeditious manner.

[0064] While the invention has been described in connection with specific embodiments thereof and in specific uses, various modifications thereof will occur to those skilled in the art without departing from the spirit of the invention as set forth in the appended claims. For example, in the above description of preferred embodiments, use is made of multiplicative notation however the method of the subject invention may be equally well described utilizing additive notation. It is well known for example that the elliptic curve algorithm equivalent of the DSA, i.e. ECDSA is the elliptic curve analog of a discrete logorithm algorithm that is usually described in a setting of Fp*, the multiplicative group of the integers modulo a prime There is correspondence between the elements and operations of the group Fp* and the elliptic curve group E(Fq). Furthermore, this signature technique is equally well applicable to functions performed in a field defined over F2.

[0065] The present invention is thus generally concerned with an encryption method and system and particularly an elliptic curve cryptograhic method and system in which finite field elements is multiplied in a processor efficient manner. The cryptographic system can comprise any suitable processor unit such as a suitably programmed general-purpose computer.

Claims

1. A method of verifying a digital signature generated by a signor in a data communication system, said signature having signature components incorporating a pair of private keys, said method comprising the steps of applying a first of said private keys to said signature to recover a value equivalent to a function associated with a second of said private keys and comparing said recovered value with said function to determine the authenticity of said signature.

2. A method according to claim I wherein said recovered value is used to compute a value of one of said signature components and said computed value and said signature component are compared to verify said signature.

3. A method according to claim l wherein the structure of said recovered value is compared with predetermined parameters to verify said signature.

4. A method according to claim 1 wherein one of said keys is a long term key and the other of said keys is a short term key generated for each signature.

5. A method according to claim 4 wherein said recovered value corresponds to said short term key.

6. A method according to claim 5 wherein said recovered value is used to compute a short term public key derived from said private key and included in said signature components.

7. A method according to claim S wherein at least a portion of said recovered value is hashed by a cryptographic bash function and a resultant hash value is compared to one of said signature components for verification.

8. A method of verifying a digital signature generated by a signor in a computer system, said signor having a private key d and a public key y, derived from an element g and said private key d said method comprising the steps of signing a message m in said computer system by: a) generating a first signature component by combining at least said element g and a signature parameter k according to a first mathematical function; b) generating a second signature component by mathematically combining said first signature component with said private key d, said message m and said signature parameter k; and said signor verifying said signature by: c) recovering a value k′ from said signature without using said public key y, and; d) utilizing said recovered value k′ in said first mathematical function to derive a value r′ to verify said signature parameter k and k′ are equivalent.

9. A method as defined in claim 8, wherein g is an element of order q in a field Fp*.

10. A method as defined in claim 8, wherein g is a point of prime order n in E(Fq), such that E is an elliptic curve defined over the field Fq.

11. A method as defined in claim 8, wherein said element g is a point on an elliptic curve over a finite field Fq.

12. A method as defined in claim 8, said signature parameter k being a randomly selected integer in the interval [1, q−1], and said first signature component having a form defined by r=gk mod p mod q, wherein p and q are primes such that q divides p−1.

13. A method as defined in claim 12, including calculating a value e=h(m) wherein h is a hash function, and wherein said second signature component s=k−1(e+dr) mod q.

14. A method as defined in claim 13, said step of recovering said value k′ including: (a) calculating a value z=(h(m)+dr)mod q, (b) calculating z−1 inverting z mod q; (c) calculating k′−1=s(z−1) mod q; and (d) calculating k′ by inverting k−1 mod q.

15. A method as defined in claim 14, said step of verifying k including the steps of calculating r′=gk′ mod p mod q and comparing r′ to r in order to verify k=k′.

16. A method as defined in claim IS, including utilizing precomputed tables in said calculations.

17. A method as defined in claim 10, said signature parameter k being a statistically unique and unpredictable integer k selected in an interval [2, n−2] and said first signature component having a form defined by r=x, mod n wherein n is an n co-ordinate of a private key.

18. A method as defined in claim 17, including calculating a value e=h(m) wherein h is a hash function and said second signature component is given by s=k−1( (e+dr) mod n.

19. A method as defined in claim 18, said recovering said value k′ includes: (a) calculating a value z=(h(m)+dr) mod n; (b) calculating z−1 by inverting z mod n; (c) calculating k′−1=s(z−1) mod n, and (d) calculating k′ by inverting k−1 mod n.

20. A method as defined in claim 19, said step of verifying k including the steps of calculating r′=gk′ mod n and comparing r′ to r in order to verify k=k′.

21. A method as defined in claim 9, said signature parameter k being a randomly selected integer in an interval [1, p−1], and said first signature component having a form defined by e=h(m||r) wherein r=gk mod p, h is a hash function and || denotes concantenation

22. A method as defined in claim 21, said second signature component being defined by s=(de+k) mod p.

23. A method as defined in claim 22, said step of recovering said value k′ includes: (a) calculating a value k′=(s−de) mod p; (b) calculating a value r′=gk mod p; (c) calculating a value e′=h(m||r′); and (d) comparing said value e′ to e in order to verify k′=k.

24. A method of verifying the authenticity of a certificate issued by a certifying authority in an electronic data communication system, said method including the steps of said certifying authority including in said certificate a pair of signature components derived from a pair of private keys, said certifying authority retaining one of said private keys, said certifying authority receiving said certificate and applying said private key to said signature components to derive therefrom a value corresponding to a function of the over of said private keys and comparing said derived value with said function to determine the authenticity of said certificate.

25. A method according to claim 24 wherein said derived value is compared with predetermined parameters to determine the authenticity of said certificate.

26. A method according to claim 24 wherein said derived value corresponds to said other key.

27. A method according to claim 26 wherein said one key is a long term private key used in a plurality of signatures and said other key is a short term key derived for each signature.

28. A method according to claim 26 wherein said signature components include a public key derived from said other key and said method includes the step of deriving a corresponding public key from said derived value and comparing said public key in said signature components with said corresponding public key.

29. A data communication system having a pair of correspondents connected by a data communication link, each of said correspondents having a cryptographic function to implement a public key cryptographic scheme utilising a pair of private keys, one of said private keys being utilised for multiple communications between said correspondents and the other of said private keys being generated by one of said correspondents at each communication, said one private key being shared by said correspondents to permit the other of said private keys to be recovered by said other correspondent from a digital signature generated by said one correspondent and compared to a signature component of said digital to verify the authenticity of said one correspondent.

30. A data communication system according to claim 29 wherein said cryptographic functions implement all elliptic curve cryptosystem.