Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
  • H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
  • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash

Definitions

• the field of the invention is that of securing electronic transactions, in particular implementing authentication, electronic signature and payment operations, carried out through communication networks such as the Internet for example.
• the invention relates to a technique for controlling secure transactions involving a physical device owned by a user, and which can be used to carry out transactions with several providers or suppliers of distinct goods or services.
• a certificate makes it possible in particular to verify the validity of a public cryptographic key used on a computer network, and is a message comprising, at a minimum, a public key, an identifier of its holder, a period of validity, an identification of a certification authority, as well as a cryptographic signature of these various data, produced by means of the secret key of this certification authority issuing the certificate.
• Reading the certificate makes it possible to authenticate with certainty the sender of a message received in the case of the signature and the identifier of the one who authenticates in the case of authentication.
• X.509 standard and more particularly X.509v3 defined in RFC3280 (Request For Comment No. 3280) published by the IETF (Internet Engineering Task Force).
• the certificates Ci issued by a certification authority then link the different public keys Pi to the identifiers Idi, as well as to any other information.
• n triples Pi, Si, Ci
• Idi a public key
• Ci a private key
• the client When he then wants to carry out a secure transaction with the i th provider, the client signs a hazard sent by the provider (we then speak of authentication) or a message (we then speak of electronic signature) using his secret key If and by associating with it the corresponding certificate Ci provided by the certification authority (which can, if necessary, be the service provider itself), according to standardized protocols.
• a disadvantage of the prior art technique cited above is that it does not allow a certification authority or a service provider to simply and remotely ensure that the certificate Ci which it issues or that it uses certifies a public key Pi corresponding to a private key Si stored in a given physical device.
• the behavior of a physical device can be completely simulated by software, so that at a distance, it is impossible for the service provider to know if it corresponds to a physical device or indeed to a software emulation of a such device.
• this physical device is the support of a paid subscription to a service provided by the provider (for for example, Internet access to newspaper articles published in a daily newspaper). Access to the paid service is conditioned for the user by opening a session with the service provider, during which he authenticates himself by means of his physical device.
• a paid subscription to a service provided by the provider for for example, Internet access to newspaper articles published in a daily newspaper.
• the service provider it is therefore particularly important for the service provider to ensure that the customer who wishes to access the service is indeed in possession of the physical device, in order to avoid that several people can access (simultaneously or not) the service, by paying a single subscription. , which would be the case if the subscription medium could be cloned (for example if the subscription medium was a set "username / password" or a private key (even encrypted) stored on a hard disk) .
• devices are made available to users.
• physical cards such as smart cards or USB “dongles”("Universal Serial Bus” for “universal serial bus”), which are conventionally associated with a pair of asymmetric keys (P 0 , S 0 ) comprising a private key S 0 and a public key P 0 .
• the private key S 0 is an electronic element which must remain secret, and which is therefore stored in a protected space of the physical device, protected from any attempted intrusion.
• the public key P 0 can be stored for free reading in the physical device, or be delivered to the user on an external medium, such as a floppy disk, CD-Rom, paper document, or a reserved space a data server.
• This pair of keys (S 0 , P 0 ) is created in the factory, before the device is marketed and put into service.
• Such a physical device also conventionally comprises calculation means making it possible to implement an asymmetric cryptographic algorithm for authentication and / or signature.
• RSA Raster-Shamir-Adleman
• DSA DSA
• GQ Guardou-Quisquater
• GPS GPS type algorithms
• this asymmetric cryptographic algorithm may be subject to the prior presentation of a carrier code (or PESf code for "Personal Identification Number") initialized during a phase of (pre) personalization of the physical device, and managed according to conventional techniques, which are not the subject of the present patent application.
• a carrier code or PESf code for "Personal Identification Number”
• the physical device can then be sold in this form to a user, by a means of distribution independent of any service provider.
• the user of the physical device also called a client, must have a C 1 certificate binding the public key issued by the service provider, or by an independent certification authority.
• P 0 of the device and an identifier Id 1 relevant for the service provider (note: in systems where the anonymity of the user vis-à-vis the service provider must be preserved, the identifier Id 1 is different from the civil identity user).
• This operation can be carried out with n separate service providers, so that the client is assigned n certificates ⁇ C l5 C2, ..., C n ⁇ binding n identifiers (Id 1 , Id 2 , ..., Id n J (each of them being relevant for a given service provider) to said public key P 0 .
• the only method allowing a service provider or a certification authority to ensure that the transaction in progress is carried out using a given physical device is based on the physical manipulation of the device by the service provider or the certification authority. Indeed, it can then read itself the public key P 0 or Pi in the device, in the case where it is stored there; otherwise, he can have the device sign a hazard, using the secret key S 0 or Si, and then verify the result of this signature using the public key P 0 or Pi supplied by the client on a medium external.
• the invention particularly aims to overcome these drawbacks of the prior art.
• an objective of the invention is to provide a technique for controlling secure transactions implementing a physical device associated with several pairs of asymmetric keys and capable of being used to conclude transactions with several distinct providers, making it possible to s '' ensure that a transaction is carried out using a physical device given, while guaranteeing non-traceability of the user by all or part of the service providers.
• Another objective of the invention is to propose such a technique which is simple to implement and introduces little additional complexity into the physical devices used and very few modifications in the software and server of service providers or certification authorities.
• Another object of the invention is to provide such a technique which is reliable and makes it possible to obtain a strong non-repudiation property, so as to create, for the provider, an environment of trust.
• the invention also aims to propose such a technique which makes it possible, if necessary, to ensure the traceability of the client by one or more certification authorities.
• the invention is based on a completely new and inventive approach to securing electronic transactions carried out by means of a physical device of the USB "dongle" type, chip card, etc., for which it is desired to ensure the non - user traceability.
• the technique of the invention is based: on the one hand, on the use of several pairs of asymmetric keys of the device, each pair being associated with a distinct identifier of the client, and making it possible to ensure its non-traceability to with regard to the various service providers with which it comes into contact; and secondly on the intervention, to introduce an additional degree of security, of a particular certification authority (ACP), to which the various certification third parties and the various service providers place all their trust.
• ACP certification authority
• This particular certification authority issues, prior to the commissioning of the physical device (USB dongle, smart card, etc.), a certificate relating to this physical device (and not, as in the prior art, a certificate relating to an identifier of its holder), which makes it possible to verify that the first public key P 0 of the physical device indeed corresponds to a first private key S 0 stored, in accordance with good practice, in a secret zone of the device.
• the ACP therefore certifies the physical device.
• a provisional certificate C'i produced (generally by the device itself) using the secret key S 0 whose corresponding public key P 0 is certified by the ACP, makes it possible to guarantee that a second public key Pi of the physical device corresponds to a second device private key If also stored, in accordance with good practice, in a secret and inviolable zone of the device.
• This public device key Pi is the one used by the client to carry out a transaction with an i th provider.
• the verification of the validity of the device certificate Ci and the examination of the ⁇ info> field is a guarantee, for the provider, that it is, even remotely, in the presence of a real physical device, and not equipment (computer, PDA, etc.) which fraudulently reproduces its behavior.
• a chain of trust is thus built up, between a service provider who places his trust in a trusted third party verifying the factory and provisional certificates, and who himself trusts the particular certification authority issuing the factory certificate C 0 .
• the transaction control method according to the invention uses the commitment of the ACP to assure a provider that a customer who wishes to initiate a secure transaction has a device physical, which has been certified by the CPA.
• the control techniques according to the prior art only ensure the identification of a user, if necessary using a chain of authentications and certifications based on the use of a succession of authorities.
• the method according to the invention comprises, in addition to certifying the identity of the user, the prior certification of the physical device subsequently owned by this user. This ensures a provider, possibly remotely, that the user who authenticates with him has a physical device. Only this assurance allows the establishment of the transaction control process to continue.
• the generation, on the fly, by the physical device, of other pairs of asymmetric keys corresponding to a need to establish a secure transaction between a provider and a user ensures the non-repudiation of the keys generated, because the use of the secret key S 0 to certify this pair of keys. Indeed, S 0 cannot be substituted by another key due to the certification by the ACP of P 0 , the certificates which result from the signature by S 0 of the pairs of asymmetric keys cannot be repudiated.
• such a control method is implemented for at least two second pairs of asymmetric keys of said device, each associated with an identifier (Idi) of said user, and each of said device certificates (Ci) issued during said issuing steps. one of said second public device keys (Pi) to said associated identifier (Idi).
• the physical device can thus be used during transactions with several providers, with each of whom the user is identified by a separate Idi identifier.
• said characteristic information of said physical device belongs to the group comprising the following information:
• said provider consults said information ( ⁇ info>) characteristic of said device certificate (Ci).
• such a control method comprises a phase of personalization of said physical device, during which said first pair of asymmetric keys, said factory certificate (C 0 ), and said information ( ⁇ info>) of said factory certificate uniquely to said physical device, so as to reduce the risks of fraudulent transactions.
• This personalization phase can be done for example in the factory, before marketing the device.
• said factory certificate (C 0 ) and provisional certificate (C'i) are stored in at least one memory area in free reading of said physical device. They are thus easily accessible for the service provider or the trusted third party.
• At least one of said first and second verification steps is carried out by said service provider.
• said first certification key (S T ) is a private key and said second certification key (P ⁇ ) is a public key.
• said particular certification authority uses a symmetric key (K), so that said first certification key (S T ) and said second certification key (P ⁇ ) are identical.
• the invention also relates to a physical device owned by a user and intended to be used during secure transactions, said physical device carrying at least a first pair of asymmetric keys, comprising a first public device key (P 0 ) and a first key. private device (S 0 ) corresponding.
• P 0 public device key
• S 0 private device
• such a device also carries a factory certificate (C 0 ), issued after verification that said private device key S 0 is housed in an inviolable zone of said physical device), corresponding to the signature of said first device key.
• said factory certificate (C 0 ) is stored in said physical device before it is put into service.
• the invention also relates to a computer program product downloadable from a communication network and / or stored on a computer-readable medium and / or executable by a microprocessor, which comprises program code instructions for the implementation of at least one step of the secure transaction control method as described above.
• the invention also relates to a system for controlling secure transactions on a communication network, implementing a physical device owned by a user and carrying at least a first pair of asymmetric keys, comprising a first public device key (P 0 ). and a corresponding first private device key (S 0 ).
• such a control system comprises at least: a particular certification server connected to said network, delivering to said physical device, after verification that said private device key S 0 is housed in an inviolable zone of said physical device and prior to its commissioning, a factory certificate (C 0 ) corresponding to the signature of said first public device key (P 0 ) and information ( ⁇ info>) characteristic of the physical device by a first certification key (S T ) of said particular certification server (ACP); a trusted third party (44) verifying said factory certificate (C 0 ) by means of a second certification key (P ⁇ ) corresponding to said first certification key (S T ), and a provisional certificate (Ci) stored in said physical device, corresponding to the signature of a second public device key (Pi) by said first private device key (S 0 ), by means of said first public device key (P 0 ), and delivering to said user, in in the case of positive verification, a device certificate (Ci) corresponding to the signature by said trusted third party
• FIG. 1 illustrates the principle of the certification, by a particular certification authority, of the public key of a physical device, during a phase of personalization of the device
• FIG. 2 shows the principle of creating a second pair of asymmetric keys (Pi, Si), as well as a provisional certificate Ci in a physical device
• FIG. 3 illustrates a block diagram of the different steps implemented in the method for controlling secure transactions of the invention
• FIG. 4 describes the different exchanges between a user and different servers of the invention, via a communication network, within the framework of the method of FIG. 3. 7. Description of an embodiment of the invention
• the general principle of the invention is based on the certification of the public keys P 0 and Pi of a physical device, making it possible to guarantee to a provider, during a secure transaction (possibly remotely), that he is dealing well with real physical device, in which the corresponding private keys S 0 and Si are stored, while ensuring the non-traceability, by the service provider, of the user of this device.
• a particular certification authority, or ACP, 10 has a pair of asymmetric keys (PT, ST) comprising a public key PT and a private key ST kept in a secret and inaccessible zone 101.
• asymmetric keys PT, ST
• Such an ACP 10 is for example the manufacturer of the physical device: the secret zone 101 in which the private key S T is stored is then a particular physical device (a smart card for example) owned by the manufacturer, or a protected memory zone with restricted access of one of its devices IT.
• the public key P T is published by the ACP 10, or supplied on request to potential providers likely to need it (ie to trusted third parties likely to carry out transactions with the owner of the physical device 13) .
• a pair of asymmetric keys (P 0 , S 0 ) is recorded therein comprising a public key P 0 , stored in a zone 131 accessible for reading from the device 13, and a private key S 0 stored in a protected area 132 of this device 13.
• This protected or tamper-resistant area 132 is designed so as to prevent the reading of the private key S 0 and to resist any attempt at software or hardware intrusion.
• the use of the private key S 0 by the device 13 is strongly constrained: in particular, as explained below, the device 13 cannot use this device private key S 0 to produce external data signatures.
• the public key P 0 can also be communicated to the holder of the physical device 13 on an external medium, independent of the device itself.
• the operations illustrated in FIG. 1 are carried out before the marketing of the physical device, in the factory, during a personalization phase. If it is a certification authority independent of the manufacturer, these operations can be carried out at the end of the production lines, before the distribution of the physical devices to the end users.
• the physical device 13 communicates via the ACP 10 its public device key P 0 .
• the factory certificate C 0 issued by the ACP 10 may correspond to the signature by the ACP 10 of the public key of the device P 0 and of the field ⁇ info>, which is a field grouping together a set of information characteristic of the device 13 (for example, the name of the manufacturer, the type of device, the nature of the cryptographic signature algorithms used by the device, etc.).
• A denotes a cryptographic signature algorithm, of RSA type for example
• the ACP thus initially certifies that the device private key S 0 is housed in a physical device 13 with characteristics given by the ⁇ info> field.
• the ⁇ info> field can be stored in free reading in the area referenced 131 of the device 13, or on an external medium, or simply be communicated to providers or third parties of trust who might need it.
• the ACP 10 (manufacturer or trusted third party) naturally agrees to produce such factory certificates C 0 (ie such signatures with its private key S T ) only for public keys P 0 corresponding to private keys stored in a physical device of a given type.
• the certification operations of FIG. 1 can also, in an alternative embodiment of the invention, be shared for several manufacturers of physical devices of different types.
• the ACP 10 is a trusted third party independent of all of the manufacturers, who holds the private key S T and who, in order to produce the factory certificate C 0 of a given physical device 13, signs with its private certification key S T , the pair (P 0 , ⁇ info>).
• the characteristic information contained in the ⁇ info> field makes it possible, for example, to provide information on the nature of the device 13, namely a USB "dongle", a smart card, etc. It can also be the product reference used by the manufacturer to designate one of the devices it builds.
• the factory certificate C 0 can be signed in the factory certificate C 0 , such as the name of the manufacturer ( ⁇ name of the manufacturer), the type of cryptographic algorithm used ( ⁇ algorithm type>), device serial number, etc.
• the key K can be shared between the manufacturer of the physical device 13 and a (or a few rare) trusted third parties, whose manufacturer knows that they will keep this key K secret; in this case, only these third parties or the manufacturer himself can verify the certificate. It is also conceivable that the key K is only used by an ACP 10 independent of the manufacturer, who signs the factory certificate C 0 with symmetric key, only on request from the manufacturer of physical devices 13. Likewise, this ACP 10 will be the only one ability to verify factory certificates C 0 , at the request of providers wishing to carry out a transaction with the associated physical devices 13. Again, this ACP 10 can of course be the manufacturer itself.
• the quadruplet (P 0 , S 0 , C 0 , ⁇ info>) can be characteristic of a given physical device 13, or be the same for all the physical devices 13 having identical characteristics described in the ⁇ info> field. In the latter case, it is not necessary to call on the ACP 10 during the personalization of the device 13, because the quadruplet (P 0 , S 0 , C 0 , ⁇ info>) consists of one and only one times for a given series of devices.
• the physical device 13 in which the certificate C 0 has been registered by the ACP 10 is sold by a means of distribution independent of any service provider, for example in a large area or at an authorized reseller.
• Such a recording comprises: a first operation for creating a second pair of asymmetric device keys (Pi, Si), which will be used during exchanges with the service provider n ° i; a second operation of issuing a device certificate Ci by a trusted third party.
• the physical device 13 comprises, in a free-read memory area 1311, a first public key of the device P 0 , a factory certificate C 0 , and possibly an ⁇ info> field which has not been shown in FIG. 2. It also comprises, in a tamper-proof memory area 1321, a first secret key of device S 0 .
• asymmetrical Pi, Si
• this couple is created by the physical device 13 itself. Indeed, many cryptographic devices are capable of self-generating their keys, according to a technique conventionally called “on board key generation”. It is an APDU ("Application Protocol Data Unit") which triggers the key generation process (Pi, Si).
• the public device key Pi is then housed in an area 1312 of the physical device 13 accessible for reading, and the private device key Si is housed in an inviolable area 1322, having specific access conditions. Indeed, such a tamper-evident zone 1322 is neither accessible in reading nor in writing, and only a suitable cryptographic signature algorithm can use this secret device key Si.
• this use is subject to the correct prior presentation of a carrier code (or PIN code).
• the key generation APDU (Pi, Si) implemented in the physical device 13 also performs an additional operation, consisting in signing the second public device key Pi with the first key deprived of device S 0 housed in the inviolable zone 1321.
• the pair of asymmetric keys additional (Pi, Si) is created outside of the physical device 13, for example by a computer equipped with a security module.
• a specific APDU is then implemented in the physical device 13, which makes it possible: to introduce the second private device key Si in the inviolable zone
• Such an operation for generating a triplet can be carried out several times, to equip the physical device 13 with a plurality of such triplets, and therefore authorize the user to carry out secure transactions with several separate providers, while ensuring its non-traceability.
• the issuance of the provisional certificate Ci must constitute the only possible use of the first device private key S 0 .
• the first device private key S 0 can only be used to sign, within a single APDU, public keys Pi, that they have been generated by the physical device or introduced into it in the form of a pair of asymmetric keys (Pi, Si).
• the physical device 13 has been acquired by a user 40, who wishes to use it to access the services offered by a provider 43, via a communication network 42, for example the global Internet network.
• a provider 43 may for example be a service provider (access to a weather service, or to a geolocation service for example) or a seller of goods (merchant on the Internet for example).
• the physical device 13 serves for example as a support for a paid subscription subscribed by the user 40 from the provider 43 (for example a subscription to a daily horoscope published on the Internet).
• the user 40 To be able to access the services of the provider 43, the user 40 must register with a trusted third party, that is to say be issued a device certificate Ci, which contains the signature by the trusted third party 44 of the public device key Pi, of an identifier Idi of the user, as well as other information, such as the date of validity of the certificate, etc.
• a trusted third party that is to say be issued a device certificate Ci, which contains the signature by the trusted third party 44 of the public device key Pi, of an identifier Idi of the user, as well as other information, such as the date of validity of the certificate, etc.
• the identifier Idi can differ from the civil identity of the user. It will be noted that the problem of the correspondence between the identifier Idi and the real identity of the user is not the subject of the present invention and will therefore not be described here in more detail. For a solution to this problem, reference may be made for example to French patent document FR 04 08992 in the name of the same applicants as the present patent application.
• the trusted third party 44 who may be the service provider 43, must have the following elements 31: the public device keys P 0 and Pi; factory certificates C 0 and provisional C'i; an identifier Idi of the user 40; characteristic information ⁇ info> of the physical device 13.
• Trusted third party 44 must also have other information required according to the X509 standard cited above, such as the validity date of the device certificate Ci to be issued, certain information relating to the use of the different keys, etc.
• the trusted third party performs various additional verifications in the context of the invention.
• the trusted third party performs the verification E33 of the factory certificate C 0 , using the public key P T of the particular certification authority 10, in order to verify that the public device key P 0 which has been transmitted to the service provider 43 corresponds to a secret key S 0 stored in a physical device described by the ⁇ info> field.
• Such an operation E33 consists in verifying that the signature of the public device key P 0 and of the ⁇ info> field contained in the factory certificate C 0 is exact.
• the trusted third party 44 can end E36 in the transaction, and refuse to issue the device certificate Ci.
• the trusted third party acquires the certainty that the public key P 0 corresponds to a private key S 0 housed in a physical device 13 with characteristics ⁇ info>, and can then proceed to verify E34 of the provisional certificate Ci, using the first public device key P 0 .
• the trusted third party 44 can end E36 the exchanges with the user 40. If, on the other hand, the signature C'i of the second public key of device Pi is exact, the trusted third party 44 acquires the certainty (insofar as he trusts the ACP 10) that the public key of device Pi corresponds well to a device private key If stored on a physical device 13 whose characteristics are specified in the ⁇ info> field, and it can therefore access the request of the user 40, by issuing E35 of the device certificate Ci .
• the trusted third party 44 delivers to the user 40 a device certificate Ci corresponding to the signature of the public device key Pi, of the identifier Idi and of information characteristic of the physical device.
• the various verifications E33 to E34 described above in relation to FIG. 3 can be performed by the provider 43 itself or by a trusted third party 44 (AC), also connected to the network 42.
• the provider 43 transmits the two factory certificates C 0 and provisional C'i to the trusted third party 44 by the through the network 42.
• the certification server 45 of the ACP 10, which created the factory certificate C 0 of the physical device 13, communicates or communicated its public key P T to the verification server or AC 44.
• the trusted third party 44 only has to use, on the one hand, the public certification key P ⁇ of the certification server 45 to verify E33 the authenticity of the factory certificate C 0 , and on the other hand, the device public key P 0 of device 13 to verify E34 the authenticity of the provisional certificate CV
• the verification of the factory certificate C 0 can be carried out by a trusted third party 44 or by the ACP. This last case is particularly relevant in the case of the use of a symmetric key K
• the trusted third party 44 When the trusted third party 44 has issued the device certificate Ci, the latter is transmitted to the user's communication terminal 41 via the communication network 42 to which the provider's registration server 43 is connected.
• a user 40 can register E35 with one or more different trusted third parties, each of which will issue a separate device certificate Ci linking the public key Pi of the physical device 13 to an identifier Idi of the user 40, relevant to the trusted third party considered.
• the user can then begin to carry out secure transactions with the service provider 43: to do this, he uses his physical device 13 to sign a provided hazard by the service provider (we speak then of authentication) or a message (we speak then of signature) thanks to its secret device key Si, and by associating with it the corresponding device certificate Ci, according to standard protocols which do not subject of this patent application and are therefore not described here in more detail.
• the invention does not modify the mode of use of a physical device for performing authentication, signing, or even doing encryption.
• providers who need the device certificate Ci for example to verify an authentication, or a signature, or to encrypt a message
• the content of this field ⁇ info> gives assurance to providers 43 who interact with a user 40 that the user is in possession of a physical device 13 with characteristics contained in the ⁇ info> field.
• the quadruplet (P 0 , S 0 , C 0 , ⁇ info>) can be the same for all physical devices of the same given type, described in the ⁇ info> field (for example for all USB "dongles" produced by the same manufacturer), so that all these devices carry the same private device key S 0 .
• the quadruplet (P 0 , S 0 , C 0 , ⁇ info>) can be specific to a given physical device. This second solution is more advantageous in terms of security, and makes it possible to better counter possible fraud attempts by users.
• the quadruplet (P 0 , S 0 , C 0 , ⁇ info>) is specific to each device, it is always possible for a fraudster to fraudulently seize the private key of device S 0 , but this fraud can be countered by introducing one or more of the following measures: the trusted third party issuing the device certificates Ci puts the fraudulent quadruplet (P 0 , S 0 , C 0 , ⁇ info>) in opposition, and refrains from issuing Ci device certificates to users presenting this quadruplet during the registration phase; the trusted third party communicates the list of the fraudulent quadruplet (s) that it has been able to detect to the ACP 10, which can then publish it or make it available to all the trusted third parties or service providers who trust it, so that none of them issue more Ci device certificates to users with such quadruplets; Finally, each trusted third party puts in opposition all of the Ci device certificates which have already been issued from a quadruplet identified as fraudulent, in order to prevent such Ci device certificates
• the invention therefore allows secure transactions to be carried out between a user, who owns a physical device, and one or more providers, while ensuring the non-traceability of the user by the different providers.
• the device certificate Ci is issued by a certification authority independent of the service provider, the latter has access only to the device certificate Ci, and therefore to the extension field ⁇ info> which is associated with it.
• this ⁇ info> field contains only generic information on the physical device, the provider cannot then establish a link between the Idi identifier associated with the device certificate Ci and the physical device itself (identified in the embodiment described above by a single quadruplet (P 0 , S 0 , C 0 , ⁇ info>).

Landscapes

• Engineering & Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=36129841

Family Applications (1)

Country Status (3)

Families Citing this family (22)

Family Cites Families (6)

• 2006
  • 2006-07-18 WO PCT/EP2006/064384 patent/WO2007012584A1/fr not_active Ceased
  • 2006-07-18 EP EP06777839A patent/EP1908215A1/de not_active Withdrawn
  • 2006-07-18 US US11/996,179 patent/US20080250246A1/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events