METHOD FOR AUTHENTICATING A PORTABLE DATA CARRIER

Abstract

A method for authenticating a portable data carrier (10) to a terminal device by the following steps: In the data carrier (10) a public session key (PKSession) is derived (S5) from a public key individual to the data carrier (PKi) which has in its turn been derived (TS32; S1) from a public group key (PK). Further, a secret session key (SKSession) is derived (S4) from a secret key individual to the data carrier (SKi) which has in turn been derived (TS31) from a secret group key (SK). Subsequently, a secret communication key (KK) is agreed on (S7) between the data carrier (10) and the terminal device. Finally, the terminal verifies (S8) the public session key (PKSession) of the data carrier (10).

Description

The present invention relates to a method for authenticating a portable data carrier to a terminal device, as well as an accordingly adapted data carrier and a terminal device.

A portable data carrier, for example in the form of an electronic identity document, comprises an integrated circuit having a processor and a memory. In the memory there are stored data that relate to a user of the data carrier. On the processor there is executable an authentication application via which the data carrier can authenticate itself to a terminal device, for example at a border control or the like in the case of an identity document.

During such an authentication method, a secure data communication between the data carrier and the terminal device is prepared by a secret communication key for symmetric encryption of a subsequent data communication being agreed on, for example by means of the known key exchange method according to Diffie and Hellman or other suitable methods. Further, at least the terminal normally verifies the authenticity of the data carrier, for example on the basis of a certificate.

For carrying out a method for agreeing on the secret communication key, it is necessary that the terminal as well as the data carrier respectively make available a secret key and a public key. The certificate of the data carrier can relate for example to its public key.

When each data carrier of a set or group of data carriers having an individual key pair consisting of a public key and a secret key is personalized, there result problems with regard to the anonymity of the user of the data carrier. It would then be possible to associate each use of the data carrier uniquely with the corresponding user and in this way create for example a complete movement profile of the user. To take account of this aspect, it has been proposed to equip a plurality or group of data carriers respectively with an identical, so-called group key pair consisting of a public group key and a secret group key. This makes it possible to restore the anonymity of a user, at least within the group. This solution is disadvantageous in that if one of the data carriers of the group is compromised, the total group of data carriers must be replaced. If the secret group key of one of the data carriers of the group has been spied out, for example, none of the data carriers of the group can be securely used further. The effort and costs of a necessary replacement campaign can be huge.

The object of the present invention is to propose an authentication method that protects the anonymity of the user and wherein the compromising of one of the data carriers has no adverse effects on the security of other data carriers.

This object is achieved by a method, a data carrier, a terminal device and a system having the features of the independent claims. Advantageous embodiments and developments are stated in the dependent claims.

A method according to the invention for authenticating a portable data carrier to a terminal device comprises the following steps: In the data carrier a public session key is derived from a public key individual to the data carrier. This public key individual to the data carrier has in its turn been derived from a public group key. Further, in the data carrier a secret session key is derived from a secret key individual to the data carrier, which has in its turn been derived from a secret group key. The public key individual to the data carrier and the secret key individual to the data carrier are stored in the data carrier, but not the secret group key and the public group key. Within the framework of the authentication of the data carrier to the terminal device, the public and the secret session keys are used. The data carrier will use its secret session key. The public session key is made available by the data carrier for the terminal device, which uses it within the framework of the authentication of the data carrier.

In particular, a secret communication key can be agreed on between the data carrier and the terminal device. The data carrier has for this purpose the public and the secret session keys. The terminal device in turn has for this purpose a public terminal key and a secret terminal key. Finally, the terminal device verifies the public session key of the data carrier.

A portable data carrier according to the invention therefore comprises a processor, a memory and a data communication interface for data communication with a terminal device, as well as an authentication device. The latter is adapted to derive a secret session key from a secret key individual to the data carrier that is stored in the memory. The authentication device is further adapted to derive a public session key from a public key individual to the data carrier that is stored in the memory. Further, it can agree on a secret communication key with the terminal device. For this purpose, the authentication device uses the public session key and the secret session key.

A terminal device according to the invention, finally, is adapted for data communication with a portable data carrier according to the invention, as well as for agreeing on a secret communication key with the data carrier while using a public terminal key and a secret terminal key. The terminal device is further adapted to verify a public session key of the data carrier, which has been derived from a public group key via a public key individual to the data carrier.

In the method according to the invention it is no longer necessary to store the secret group key in the data carrier. Therefore, such key cannot be spied out upon an attack on the data carrier. Secret session keys of other, non-attacked data carriers of a group of data carriers can be used further. It is not possible to track the user of the data carrier on the basis of the secret session key of the data carrier, which might be employed in a challenge-response method for authentication to the terminal device, because this session key changes from one use to the next.

Preferably, the terminal device verifies the public session key of the data carrier by means of a certificate of the public group key, which certificate is stored on the data carrier. For this purpose, the terminal device first checks the certificate. Thereafter the terminal device reconstructs the derivation of the public session key from the public group key via the public key individual to the data carrier. The derivation information necessary therefor is made available by the data carrier. In this way the data carrier can be authenticated as a data carrier of the group associated with the group key pair, but not be tracked on the basis of a certificate individual to the data carrier, which certificate is not provided according to the invention. Only the certificate of the public group key, said certificate being identical for all data carriers of the group, is stored on the data carrier, thereby preserving the anonymity of the user of the data carrier.

According to a preferred embodiment, the public key individual to the data carrier and the secret key individual to the data carrier are derived from the public group key and the secret group key and stored in the data carrier in a personalization phase of the data carrier. The certificate of the public group key can likewise be incorporated into the data carrier and stored in this phase.

Preferably, the secret key individual to the data carrier is derived from the secret group key by using a first random number. For this purpose, there can be used any suitable operation that can take up as input data—inter alia—the secret group key as well as the first random number (and) process them into the secret key individual to the data carrier. For example, there can be used mathematical operations, such as multiplication, exponentiation or the like. The public key individual to the data carrier can then be derived by means of the previously derived secret key individual to the data carrier. This is expedient e.g. when the public group key has also been formed using the secret group key, for example by means of modular exponentiation, as known from the Diffie-Hellman key exchange method. It is also possible to derive the public key individual to the data carrier from the public group key in a different way.

In a similar way the derivation of the secret session key from the secret key individual to the data carrier and of the public session key from the public key individual to the data carrier is also effected in randomized fashion, i.e. in dependence on a second random number. Here, too, there can be used different derivation operations which permit as input data at least respectively the respective key individual to the data carrier and the second random number. Normally, the derivation of the secret session key differs from the derivation of the public session key. However, the same second random number is usually used for the derivation of both keys of the session key pair. Since a new session key pair is derived upon each use of the data carrier, i.e. upon each authentication to a terminal device, it is not possible to track the data carrier on the basis of the session keys.

According to a preferred embodiment of the method according to the invention, the secret communication key is agreed on by means of a known Diffie-Hellman key exchange method. This method is based on a specified primitive root modulo a specified prime number. The secret key individual to the data carrier is derived from the secret group key by multiplication by the first random number. The public key individual to the data carrier is computed from an exponentiation of the primitive root by the secret key individual to the data carrier. In so doing, the public group key is formed by exponentiation of the primitive root by the secret group key. The method according to the invention—with session keys preferably varying in randomized fashion—can thus be integrated without any substantial changes into known similar protocols—which provide a key pair firmly bound to the data carrier and use the Diffie-Hellman method.

The secret session key can be formed by multiplication of the secret key individual to the data carrier by the second random number. Then the public session key is derived by exponentiation of the key individual to the data carrier by the second random number. In this way it results that the public session key can be computed by forming an exponentiation of the public group key by the product of the first and second random numbers.

In order for the terminal to be able to verify the public session key of the data carrier, the data carrier sends to the terminal device the public session key, the product of the first and second random numbers as well as the certificate of the public group key.

The terminal device verifies the public session key—after checking the certificate of the public group key—by forming an exponentiation of the public group key by the product of the two random numbers. This computation yields, as described hereinabove, exactly the public session key—as long as the latter has been derived from the public group key via the public key individual to the data carrier in the prescribed fashion. The public session key can thus be verified solely using the public group key. In this way the data carrier is authenticated as belonging to the public group key, while heeding the anonymity of the user of the data carrier and without requiring a certificate individual to the data carrier.

A data carrier is understood here to be for example an electronic identity document, a chip card, a SIM card, a secure MultiMediaCard or a secure USB token. The terminal device can be an arbitrary authentication partner. In particular, it can be a local or a remote terminal, a remote server or another data carrier.

As indicated several times hereinabove, the same public and secret group keys are respectively used for deriving secret keys individual to the data carrier and public keys individual to the data carrier of a plurality of different data carriers which form a group of data carriers. It is of course possible to provide several groups of data carriers which are respectively associated with their own group key pair.

Hereinafter the invention will be described by way of example with reference to the attached drawings. Therein are shown:

FIG. 1 a preferred embodiment of a data carrier according to the invention in schematic fashion, and

FIGS. 2 and 3 steps of a preferred embodiment of the method according to the invention for authenticating the data carrier from FIG. 1 to a terminal device.

Referring to FIG. 1, a data carrier 10, which is represented here as a chip card, comprises data communication interfaces 20, 20′, a processor 30 as well as different memories 40, 50 and 60. The data carrier 10 can also be present in a different design.

As data communication interfaces 20, 20′ the data carrier 10 comprises a contact pad 20 for contact-type data communication as well as an antenna coil 20′ for contactless data communication. Alternative data communication interfaces can be provided. It is further possible that the data carrier 10 supports only one kind of data communication, i.e. only contact-type or contactless.

The non-volatile, non-rewritable ROM memory 40 comprises an operating system (OS) 42 of the data carrier 10, which controls the data carrier 10. At least parts of the operating system 42 can also be stored in the non-volatile, rewritable memory 50. The latter can be present for example as a flash memory.

The memory 50 comprises an authentication device 52 by means of which an authentication of the data carrier 10 to a terminal device can be carried out. In so doing, the keys 54, 56 individual to the data carrier that are likewise stored in the memory, as well as a digital certificate 58, find their application. The mode of operation of the authentication device 52, the keys 54, 56 and the certificate 58 as well as their roles during an authentication process will be described more precisely with reference to FIGS. 2 and 3. The memory 50 can contain further data, for example data relating to its user.

The volatile, rewritable RAM memory 60 serves as the working memory of the data carrier 10.

The data carrier 10 can comprise further features (not shown) when it constitutes for example an electronic identity document. These features can be applied, for example imprinted, visibly on a surface of the data carrier 10 and designate the user of the data carrier, for example through his name or a photo.

Referring to FIGS. 2 and 3, an embodiment of the method for authenticating the data carrier 10 to a terminal device will now be described more precisely. In FIG. 2 there are shown preparatory steps. These can be carried out for example during the manufacture of the data carrier 10, e.g. in a personalization phase.

In a first step S1 a secret group key SK as well as a public group key PK are formed. The key PK is computed as the result of an exponentiation of a specified primitive root g modulo a specified prime number p. All hereinafter described computations are to be read modulo the prime number p, without this always being explicitly stated. The two keys SK and PK form a group key pair and provide the basis for the hereinafter described key architecture for a group of data carriers 10 of the same kind.

In step S2 there is formed a certificate C_PK which is used for verification of the public group key PK.

Step S3 takes place during the personalization of the data carrier 10. In so doing, the data carrier 10, which constitutes a data carrier of a specified group of data carriers, is equipped with a key pair individual to the data carrier SK_i, PK_i, which is derived from the group key pair SK, PK in randomized fashion, i.e. in dependence on a first random number RND_i. In this way, each data carrier 10 of the group is equipped with its own key pair individual to the data carrier which differs from a corresponding key pair of another data carrier of the group, due to the randomized component upon the key derivation. On the other hand, all data carriers 10 of the group are connected by the fact that their key pairs have been derived from the same group key pair SK, PK.

In substep TS31 a secret key SK, individual to the data carrier is derived by the secret group key SK being multiplied by the random number RND_i.

The public key individual to the data carrier PK, is computed subsequently in substep TS32 as the result of an exponentiation of the hereinabove mentioned primitive root g by the previously formed secret key individual to the data carrier SK_i.

The thus derived keys SK; and PK, are stored in substep TS33 together with the random number RND_i and the certificate C_PK in the data carrier 10. The latter is thus adapted to carry out by means of its authentication device 52 an authentication to a terminal device, as will be described more precisely with reference to FIG. 3.

For preparing a key agreement with the terminal device (cf. step S7), the authentication device 52 derives a secret session key SK_Session in step S4. This secret session key SK_Session forms a session key pair together with the hereinafter described public session key PK_Session (cf. step S5). This key pair is used in the data carrier by the authentication device 52 only in connection with a single authentication to a terminal device, however. For carrying out each future, further authentication a new session key pair is respectively derived from the key pair individual to the data carrier SK_i, PK_i by the authentication device 52, in the hereinafter described fashion.

The session key pair is likewise formed using a randomized component. For this purpose, a second random number RND_Session is generated or made available by the authentication device 52. The secret session key SK_Session is then computed from a multiplication of the secret key individual to the data carrier SK_i by the second random number RND_Session.

The public session key PK_Session derived in step S5 as the result of the exponentiation of the public key individual to the data carrier PK_i by the second random number RND_Session. In step S6 the authentication device 52 sends to the terminal device the public session key PK_Session, the value RND_i*RND_Session resulting from the multiplication of the first and second random numbers, as well as the certificate C_PK.

In step S7 a communication key KK is now agreed on between the authentication device 52 of the data carrier 10 and the terminal device. This key serves to encrypt a subsequent data communication between the data carrier 10 and the terminal device by means of a symmetric encryption method. The key agreement can be carried out by known methods, for example the Diffie-Hellman key exchange method.

Finally, the terminal device checks in step S8 the authenticity of the data carrier 10. For this purpose, it checks in a first substep TS81 the certificate C_PK of the public group key PK which is known to the terminal. Subsequently, the terminal device verifies the public session key PK_Session of the data carrier 10. For this purpose, the terminal device computes the result of the exponentiation of the public group key by the product RND_i*RND_Session of the two random numbers and compares this result with the public session key PK_Session. Through this computation the terminal device reconstructs the derivation of the public session key PK_Session, starting out from the public group key PK via the public key individual to the data carrier PK_i. This holds since

$\begin{array}{cc}{\mathrm{PK}}_{\mathrm{Session}}={\mathrm{PK}}_i^\left({\mathrm{RND}}_{\mathrm{Session}}\right)& \left(\mathrm{cf}.\mathrm{step}S5\right)\\ =\left(g^\left({\mathrm{SK}}_i\right)\right)^\left({\mathrm{RND}}_{\mathrm{Session}}\right)& \left(\mathrm{cf}.\mathrm{substep}\mathrm{TS}32\right)\\ =\left(g^\left(\mathrm{SK}*{\mathrm{RND}}_i\right)\right)^\left({\mathrm{RND}}_{\mathrm{Session}}\right)& \left(\mathrm{cf}.\mathrm{substep}\mathrm{TS}31\right)\\ =\left(g^\mathrm{SK}\right)^\left({\mathrm{RND}}_i*{\mathrm{RND}}_{\mathrm{Sessio}}\right)& \left(\mathrm{math}.\mathrm{reformulation}\right)\\ =\mathrm{PK}^\left({\mathrm{RND}}_i*{\mathrm{RND}}_{\mathrm{Session}}\right)& \left(\mathrm{cf}.\mathrm{step}S1\right).\end{array}$

If the result matches the public session key PK_Session, the data carrier 10 is considered verified. In the contrary case the terminal device aborts the authentication process.

The method thus makes it possible that the user of the data carrier 10 can remain anonymous, at least within the group of data carriers that are associated with the same group key pair SK, PK. It is not possible to trace the use of the data carrier 10 back to the user, because session keys SK_Session, PK_Session are used that vary per session, on the one hand, and the verification of the data carrier 10 is effected only by means of the certificate C_PK of the public group key PK—which is identical for all data carriers of the group—and not by means of a certificate individual to the data carrier, on the other hand. Further, it is advantageous that one can dispense with storing the secret group key SK in the data carriers 10 of the group.

Within the framework of the present solution, a multiplication can be an arbitrary group-specific multiplication, and an exponentiation an arbitrary group-specific exponentiation. Multiplication and exponentiation can be carried out on the basis of the discrete logarithm or on the basis of elliptical curves. Moreover, a modified derivation can be used upon the derivation for example of the individual key SK_i=SK*RND_i in order to make it more difficult to compute SK. For example, there can be chosen: SK_i=RND_îSK.

Claims

1.-15. (canceled)

16. A method for authenticating a portable data carrier to a terminal device, the steps deriving (S5) a public session key (PKSession) from a public key (PKi) individual to the data carrier derived (TS32) from a public group key (PK), and deriving (S4) a secret session key (SKSession) from a secret key (SKi) individual to the data carrier derived (TS31) from a secret group key (SK), in the data carrier; anonymously authenticating (S8) the data carrier to the terminal device, using the secret session key (SKSession) in either or both the data carrier and the public session key (PKSession) in the terminal device.

17. The method according to claim 16, wherein the terminal device verifies the public session key (PKSession) by a certificate (CPK) of the public group key (PK), which certificate is stored in the data carrier, by the terminal device first checking (TS81) the certificate (CPK) and thereafter reconstructing (TS82) the derivation of the public session key (PKSession) from the public group key (PK) via the public key (PKi) individual to the data carrier.

18. The method according to claim 16, wherein the public key (PK) individual to the data carrier and the secret key (SKi) individual to the data carrier are derived from the public group key (PK) and the secret group key (SK), respectively, and stored (S3) in the data carrier (10) in a personalization phase of the data carrier.

19. The method according to claim 16, wherein the secret key (SKi) individual to the data carrier is derived from the secret group key (SK) while using a first random number (RNDi).

20. The method according to claim 16, wherein the public session key (PKSession) and the secret session key (SKSession) are derived from the public key (PKi) individual the data carrier and the secret key (SKi) individual to the data carrier, respectively, while using a second random number (RNDSession).

21. The method according to claim 16, including the steps of agreeing on a communication key (KK) between the data carrier and the terminal device while using the public session key (PKSession) and the secret session key (SKSession) of the data carrier as well as a public terminal key and a secret terminal key of the terminal device; wherein the communication key (KK) is agreed on by a Diffie-Hellman key exchange method which is based on a specified primitive root (g) modulo a specified prime number,the secret key (SKi) individual to the data carrier is derived (TS31) from the secret group key (SK) by multiplication by the first random number (RNDi), andthe public key (PKi) individual to the data carrier formed (TS32) by exponentiation of the primitive root (g) by the secret key individual to the data carrier (SKi),wherein the public group key (PK) is formed (S1) by exponentiation of the primitive root (g) by the secret group key (SK).

22. The method according to claim 16, wherein the secret session key (SKSession) is derived (S4) by multiplication of the secret key (SKi) individual to the data carrier by the second random number (RNDSession), and the public session key (PKSession) is derived (S5) by exponentiation of the public key (PKi) individual to the data carrier by the second random number (RNDSession).

23. The method according to claim 16, wherein the data carrier sends to the terminal device the public session key (PKSession), the product (RNDi*RNDSession) of the first random number (RNDi) and the second random number (RNDSession) as well as the certificate (CPK) of the public group key (PK).

24. The method according to claim 16, wherein the terminal device, for verifying the public session key (PKSession), forms an exponentiation of the public group key (PK) by the product (RNDi*RNDSession) of the first random number (RNDi) and the second random number (RNDSession).

25. The method according to claim 16, wherein, for deriving public keys (PKi) individual to the data carrier and secret keys (SKi) individual to the data carrier of a plurality of different data carriers, the same public and secret group keys (PK; SK) are respectively used.

26. A portable data carrier, comprising a processor, a memory and a data communication interface providing data communication with a terminal device, as well as an authentication device, wherein the authentication device of the data carrier is configured to derive a public session key PKSession) from a public key (PKi) individual to the data carrier that is stored in the memory, to derive a secret session key (PKSession) from a secret key (SKi) individual to the data carrier that is stored in the memory, and to use the secret session key (SKSession) within the framework of an authentication to the terminal device.

27. The data carrier according to claim 26, wherein the data carrier is configured to authenticate itself to a terminal device according to the method recited in claim 16.

28. A terminal device for data communication with the portable data carrier recited in claim 16, wherein the terminal device is arranged, using a public terminal key and a secret terminal key, to agree on a communication key (KK) with the portable data carrier and to verify a public session key (PKSession) of the data carrier which has been derived from a public group key (PK) via a public key (PKi) individual to the data carrier.

29. The terminal device according to claim 28, wherein the terminal device is arranged to verify the public session key (PKSession) of the data carrier by a certificate (CPK) of the public group key (PK), said certificate being stored in the data carrier, by the terminal device first checking the certificate (CPK) and thereafter reconstructing the derivation of the public session key (PKSession) from the public group key (PK) via the public key (PKi) individual to the data carrier.

30. A system comprising the portable data carrier recited in claim 27 and the terminal device recited in claim 28, arranged to carry out the method recited in claim 17.