Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key)
10 claims: 3 independent, 7 dependent
- 1A method for authentication, data communication, storage and retrieval in a distributed key cryptography system, wherein there are provided at least one client system (300), comprising data storage means (311, 313) initially storing at least one encrypted first key encrypting key (Wk), (Wpu1, Wpr1), first and second hashing functions able to compute at least first and second hashes from at least one passphrase, a server system (100) comprising data storage means (111, 121) initially storing a first hash at least one encrypted second key encrypting key (Dk), (Dpr1) encrypted by a second hash value, at least one encrypted symmetric third key (Fk), (F1) being encrypted by means of the first key encrypting key, and encrypted data, the method comprising the following steps:a) the at least one client system (300) hashing the at least one passphrase using the first hashing function, so as to compute the first hash, b) the at least one client system (300) transmitting, via telecommunication means (200, 203), the first hash to the server system (100);c) the server system (100) performing an authentication of the first hash comparing it with the first hash stored on the storage means of the server;d) the server system (100) providing the at least one client system (300) with the at least one second key encrypting key (Dk), (Dpr1) in encrypted form over telecommunication means (200, 203) if said authentication is successful, characterized in that e) the at least one client system (300) hashes the passphrase by means of the second hashing function, so as to produce the second hash;f) the at least one client system (300) utilizes the second hash for decrypting the at least one encrypted second key encrypting key (Dk), (Dpr1);g) the at least one client system (300) utilizes the decrypted second key encrypting key (Dk), (Dpr1) for decrypting the at least one first key encrypting key (Wk), (Wpu1, Wpr1), stored in encrypted form only in storage means (311, 313) of the client system (300);h) the server system (100) transmits the at least one encrypted symmetric third key (Fk), (F1), stored in encrypted form in storage means (111, 121) of the server system (100), to the at least one client system (300);i) the at least one client system (300) decrypts the at least one third Key (Fk), (F1) by means of the at least one first key encrypting key (Wk), (Wpu1, Wpr1);j) the at least one client system (300) decrypts data by means of the at least one third key (Fk), (F1).
- 7System for authentication, data communication, storage and retrieval in a distributed key cryptography system, comprising at least one client system (300), comprising data storage means (311, 313) storing initially at least one encrypted first key encrypting key (Wk), (Wpu1, Wpr1), first and second hashing functions that can perform encryption and decryption operations and able to compute at least first and second hashes from a passphrase string, a server system (100) comprising data storage means (111, 121) initially storing a first hash at least one encrypted second key encrypting key (Dk), (Dpr1) encrypted by a second hash value, at least one encrypted symmetric third key (Fk), (F1) being encrypted by means of the first key encrypting key, and encrypted data, and a) means in the at least one client system (300) for hashing a passphrase using the first hashing function, so as to compute the first hash;b) means in the at least one client system (300) for transmitting, via telecommunication means (200, 203), the first hash to the server system (100);c) means in the server system (100) performing an authentication of the first hash comparing it with the first hash stored on the storage means of the server;d) means in the server system (100) providing the at least one client system (300) with at least one second key encrypting key (Dk), (Dpr1, Dpr2) in encrypted form over telecommunication means (200, 203) if said authentication is successful, characterized in that there are provided e) means in the at least one client system (300) hashing the passphrase by means of the second hashing function, so as to produce a second hash;f) means in the at least one client system (300) for utilizing the second hash for decrypting the at least one encrypted second key encrypting key (Dk), (Dpr1) ;g) means in the at least one client system (300) for utilizing the decrypted second key encrypting key (Dk), (Dpr1) for decrypting the at least one first key encrypting key (Wk), (Wpu1, Wpr1), stored in encrypted form only in storage means (311, 313) of the client system (300);h) means in the server system (100) for transmitting the at least one symmetric third key (Fk), (F1), stored in encrypted form in storage means (111, 121) of the server system (100), to the at least one client system (300);i) means for decrypting the symmetric third key (Fk), (F1) by means of the first key encrypting key (Wk), (Wpu1, Wpr1);j) means in the client system (300) for decrypting data by means of the at least one_symmetric third key (Fk).
- 9A computer program product in a computer usable medium, comprising:a) instructions in at least one client system (300), for initially storing at least one encrypted first key encrypting key (Wk), (Wpu1, Wpr1), first and second hashing functions able to compute at least first and second hashes from at least one passphrase, b) instructions in a server system (100) for initially storing a first hash at least one encrypted second key encrypting key (Dk), (Dpr1) encrypted by a second hash value, at least one encrypted symmetric third key (Fk), (F1) being encrypted by means of the first key encrypting key, and encrypted data, c) instructions in the at least one client system (300) for hashing the at least one passphrase using a first hashing function, so as to produce a first hash, and using a second hashing function so as to produce a second hash;d) instructions in the client system for transmitting, via telecommunication means (200), the first hash to the at least one client system (300);e) instructions in the server system (100) for performing an authentication of the first hash comparing it with the first hash stored in the server system (100);f) instructions in the server system (100) for providing the at least one client system (300) with the at least one second key encrypting key (Dk), (Dpr1), in encrypted form over telecommunication means (200, 203);g) instructions in the at least one client system (300) for hashing the at least one_passphrase by means of the second hashing function, so as to produce the second hash;h) instructions in the at least one client system (300) for utilising the second hash for decrypting the at least one encrypted second key encrypting key (Dk), (Dpr1);i) instructions in the at least one client system (300) for utilizing the decrypted at least one_second key encrypting key (Dk), (Dpr1) for decrypting the at least one first key encrypting key (Wk), (Wpu1, Wpr1 stored in encrypted form in storage means of the at least one_client system (300);j) instructions in the server system (100) for transmitting a symmetric third key (Fk), stored in encrypted form in storage means of the server system (100), to the at least one client system (300);k) instructions in the at least one client system (300) for decrypting data by means of the at least one symmetric third key (Fk);l) instructions in for decrypting the at least one symmetric third key (Fk), (F1) by means of the at least one first key encrypting key (Wk) (Wpu1, Wpr1);
Independent claims3
60 paragraphs, as filed
Technical field
The present invention relates to data communications systems' security and, more particularly, to the secure processing of messages using cryptography. In particular, it refers to authentication methods and to a data management and protection system for data exchanged between server and clients.
Background of the invention
Cryptography algorithms are widely used to ensure the security or integrity of messages in data communications systems. Various types of such algorithms exist and they are mainly divided in two principal classes, namely symmetric and asymmetric key algorithms.
One well known asymmetric key algorithm is the Rivest-Shamir-Aldeman (RSA) algorithm. In such system, the key used for encryption is different from the key used for decryption, i.e. the encryption algorithm is not symmetric, and the decryption key cannot be easily calculated from the encryption key. Thus, one key generally the encryption key, may be published and is called public key, while the paired key is kept secret and is called the private key.
The public key is made available so that anyone can use it to encrypt data which the receiving party then decrypts using his private key. This system is considered secure since no-one can decrypt the data without access to the private key and since knowledge of the public key does not allow to readily obtain the private key.
However, such public key encryption schemes are computationally intensive and demand substantially higher computing resources, such as processing power and memory requirements, for encryption and decryption than symmetric key schemes. In practical implementations, therefore, a message to be transferred is typically first encrypted by a symmetric encryption algorithm using a pseudorandom secret key. The secret key is then encrypted utilizing the public key of the intended recipient, and both the encrypted message and the encrypted secret key are transmitted to the intended recipient. When the message and secret key are delivered, the recipient uses the private key to decrypt the secret key, and then decrypts the message using the secret key.
The larger an encryption key, e.g. 128 bits confronted to 56 bits, the greater is the security provided by the cryptography algorithm. Furthermore, basic security principles suggest to frequently change encryption keys and to use different keys to encrypt a large quantity of data. As a result, encryption keys cannot be easily committed to memory or stored by common users and instead are most commonly stored in centralized non-volatile storage means, such as within one or more databases containing the encryption keys and the encrypted data.
The security of such cryptography systems is therefore limited by the security of the database(s) containing the encryption keys and encrypted data and by the security of the communication channel used to retrieve information from the database. For example, in a networked computer environment where a number of clients share the resources of a common server, the encryption key database may be made accessible over the network, with encryption keys retrieved upon demand over the network. It is obvious that security would be severely compromised if the encryption keys are readily available to anyone or are easily intercepted and used in that or similar situations. It would be desirable, therefore, to provide a mechanism for storing and managing encryption keys for a distributed key storage cryptography system.
Various methods have been proposed in the prior art to provide such means for secure data and key management and distribution, especially in the context of a public key cryptography system.
One method of authentication and storage of private keys in a public key cryptography system is described in the <patcit id="pcit0001" dnum="US6370250A"><text>US-A-6370250</text></patcit>, where private keys are protected within private key storage and communication by the requirement of a password during decryption. Upon receipt of a message encrypted with the public key, both the public and private key are retrieved from a single key storage.
Whilst this and other known methods go some way to alleviating the problem of securing key distribution and storage, they suffer from several disadvantages inherent in storing the secret key(s) and data either on a centralized server database or on a device in the possession of the user, or in requiring the storage of the key(s) needed to decrypt the data to be on a single device.
Firstly, it is possible that the storage devices may be probed to obtain the secret key(s). This is particularly true in the case the key storage is kept on the device in possession of the user.
Furthermore, in the case of a centralized server managing the key storage and distribution, typical key distribution schemes require users to reveal in some form their secret authentication credentials to the server. Such disclosure may enable the server administrators to access the users' secrets, should they desire or be asked to do so.
Document <patcit id="pcit0002" dnum="EP1249981A"><text>EP 1249981</text></patcit> describes a method for the provisioning of security services to the users by means of three alternative schemes for distribution and management of private keys. The first scheme is server-based, password-encrypted scheme. In this scheme, the private key is encrypted with the user's password after generation. This encrypted private key is then sent to the server for storage. The encrypted private key is downloaded to the client machine after login authentication and decrypted by the client when needed for reading mail, decrypting files or signing mail.
The second is a server-based, non-encrypted scheme. In this scheme the private key is encrypted by the public key of a domain-owner and then sent to the server for storage.
When the client requires the private key, it is decrypted using the domain-owner private key and downloaded to the client.
The third is a client-based, password-encrypted scheme. In this scheme, the private key is encrypted with the user's password after generation. It is then stored on local storage such as hard disk, floppy disk, smart card, memory-card, etc. When the client requires the private key, the local copy is read and decrypted. For speed reasons, the local copy may be read into memory when the client is initialised and then decrypted when needed.
The present invention is directed at providing a secure method of enabling encrypted messages to be received and decrypted by an authorised user in such a manner that it can be shown that only the authorised user can access all the secret keys required for the processing of a particular message or data.
Summary of the invention
It is therefore one object of the present invention to provide an authentication and authorization method and system for accessing private keys utilized in decoding an encrypted data transfer, accessible only by the user or only with the authorisation of the user.
It is therefore one object of the present invention to provide an authentication and authorization method and system for accessing secret data which does not require the user to share its own private keys with other users, or with any centralized authorization system or server.
It is another object of the present invention to provide an improved method and system for achieving electronic data transfer security.
It is yet another object of the present invention to provide a method and system for defeating secret key discovery attacks in a distributed key cryptography system. The foregoing objects are achieved by means of a method for authentication, data communication, storage and retrieval according to claim 1. It uses a private key Fk encrypted with a first key encrypting key Wk, which is also encrypted using a second key encrypting key Dk. This latter key is encrypted using a hashed passphrase value H2, obtained by hashing a passphrase PP known only to the authorized user. The system comprises a first data processing system S adapted for data communication with a second data processing system C via a network. The second data processing system is also adapted for data communication with a system user via a network or other communication means.
The first data processing system comprises first data storage means in which are stored in a secure manner the hashed passphrase value H1, the encrypted second key encrypting key, the encrypted private key and encrypted data and messages. The second data processing system comprises second data storage means in which are stored in a secure manner the encrypted first key encrypting key Wk and an executable code that can perform encryption and decryption operations and that can compute at least two distinct hash strings H1 and H2 from one single passphrase string PP received from the user.
Upon receipt of a request initiated by the user, the second data processing system prompts the user to enter a passphrase PP. The first hashed passphrase is transferred to the first data processing system, where it is compared with the stored hash string H1. If they match, the first data processing system transfers to the second data processing system the encrypted second key encrypting key Dk.
A candidate key is obtained by decrypting Dk using the second hashed passphrase H2. The passphrase can be at this stage verified using several means, for example by encrypting a well-known message stored on the second data processing system with the candidate key, transferring it to the first data processing system and comparing it with the encrypted well-known message previously stored. If they match the passphrase is verified and the user is authenticated and authorized.
After the user has been authorized, the first data processing system transmits to the second data processing system the encrypted private key Fk and the encrypted data. The second processing system then decrypts the encrypted first key encrypting key Wk using Dk, decrypts the encrypted private key Fk using the decrypted first key encrypting key Wk and decrypts the data using Fk.
It is noteworthy that interception of any aforementioned transaction is useless since only encrypted keys and encrypted data are transmitted and that such encrypted quantities alone cannot be utilized to decrypt the data without knowledge of the key encrypting key Wk safely stored in encrypted form on the second data processing system.
It is also noteworthy that the authentication and authorization procedure of the user is carried out in two stages, the first one performed by the first data processing system and the second one by the second data processing system only after the first stage has been successfully completed. However, no information received by the first data processing system during the authentication procedure is relative to the encryption keys stored in its data storage. At the same time, the second data processing system must receive the encrypted second key encrypting key before it can readily perform any data decryption.
Brief description of the drawings
Preferred embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 shows a component diagram of an example of a first embodiment of the system for authentication, data communication, storage and retrieval according to the invention;</li><li>Fig.1a shows diagrammatic notation to represent encryption and decryption operations according to the invention;</li><li>Fig. 2 shows the basic scheme of the functional relations between the encrypting/decrypting keys and hashes in the method according to the invention.</li><li>Fig. 3 shows a flow diagram of an embodiment of the method for authentication, data communication, storage and retrieval according to the invention;</li><li>Fig. 4 shows a component diagram of an example of a second embodiment of the system for authentication, data communication, storage and retrieval in case of more than one client system, according to the invention;</li><li>Fig. 5 shows the basic scheme of the functional relations between the encrypting/decrypting keys and hashes of a method according to a second embodiment of the invention;</li><li>Figures 6, 7 and 8 show flow diagrams of the method for authentication, data communication, storage and retrieval according to the second embodiment of the invention.</li></ul>
Detailed description of preferred embodiments of the invention
The figures 2 and 5, show shorthand diagrammatic notation to represent encryption and decryption operations. In particular, both such operations require two input quantities (the data and the key) and produce one output data stream. In the chosen notation, this process is represented by a triangle, where the input and output data are related to the vertices of the triangle's base and where the encryption/decryption key is related to the third vertex. In particular, encryption of a given input will be represented using a dark filled triangle diagram as shown in part (A) of Fig.1a. The corresponding decryption process is represented using the diagram shown in part (B) of Fig.1a.
With particular reference to the figures, there is provided a data processing system 100, generally a server, having in a known manner, a CPU 120, data storage means which can be either unique or separated in different parts for storing different type of data. A part 111 of the storage means can be dedicated to the storage of encryption and decryption keys and a second part of the storage means 110 can be dedicated to the storage of encrypted data. In a known manner, the server 100 has an interface for communicating with telecommunication means 200 to connect to a second data processing system, generally a client 300. The telecommunication means can obviously be of any type used for data transfer.
This client 300, advantageously is a computer or a personal computer and comprises a CPU 320, data storage means for storage of data and of encryption/decryption keys. The data storage means can be either the same or be separated, e.g. the key storage means 311 can be advantageously a magnetic or an optical disc, while the data storage means 320 can be a magnetic hard disc 310.
The user controls and accesses the client 300 by means of a keyboard 202 or of any other suitable interface 201 of the known type.
In such a computer system data communication, storage and retrieval can be performed safely by means of a distributed key cryptography system which is controlled by means of a method for authentication of users and for encrypting and decrypting keys and data according to the invention hereafter described.
The system is at first initialised at the request of users which want to have access to the system. It is noteworthy that such initialisation and registration procedure, overseeing the generation of all encryption keys and hashes, should be performed under the strict control of the user in order to assure total confidentiality. The operations required by the initialisation and registration procedure, including key generation, encryption, storage and transmission, could for example be performed on the client using an executable code obtained from a centralized service authority, for example downloaded as an Internet browser Applet component or executed as a client application. In one possible case, during the registration procedure, the user provides a password or a passphrase PP, which is hashed by means of a hash function 1, producing a hash1 which is transmitted to the server 100 and kept in appropriate storage medium 111. Furthermore, the private key Fk and the two key encrypting keys Dk and Wk are generated, encrypted and stored in appropriate storage media of client 300 and of server 100 as detailed in Fig. 1 and Fig. 2. After all the elements of the preferred embodiment are successfully generated and distributed, the users can work with the system. Advantageously the key storage 311 can be a separate storage media (part A of Fig. 1 and 4) other than the data storage media (part B of Fig. 1 and 4), without departing from the scope of the invention.
During normal operation of the system, the user is prompted to provide his user ID or username and the passphrase PP, stage 600. The client system 300 hashes, step 602, the passphrase PP using hashing function 1, thus producing hash1. The client 300 transmits, via the telecommunication means, hash1 to the server and the latter performs the authentication of hash1 received from the client 300 with the hash 1 previously stored following the initialisation procedure, step 606.
If authentication, step 606, is successful the server 100 provides the client 300 with the encrypting key Dk in encrypted form via telecommunication means 200.
At the same time, in step 604, the passphrase PP is hashed by a second hashing function 2, producing a hash 2 which is stored in storage means of the client system 300 and is used for decrypting the encrypted key Dk, step 610. After the decrypted key Dk is validated, the authentication procedure is completed and the user authenticated.
The decrypted key Dk is then used by the client to decrypt the key encrypting key Wk, which was kept stored in encrypted form in the permanent storage means of the client system 300, step 612.
The user requests a private key Fk, stored in encrypted form in the storage means of the server 100, step 614. The client system 300 decrypts the private key Fk by means of the key Wk, step 616. By means of the decrypted private key Fk, the client system 300 decrypts data, e.g. an encrypted working document or message of any known type, step 620.
The document is either stored in encrypted form in the storage means of the client 300, or preferably in the storage means of the server 100. In the latter case the encrypted document 618 is sent via the telecommunication means 200 to the client system 300. After decryption of the document, the user can work with any appropriate software application on the document.
In this embodiment of the method of the invention the private key Fk is advantageously stored in the storage means of the server in encrypted form, but the server does not have at disposal the decrypting key Wk which is stored only on the client system.
In a second embodiment of the invention, having particular reference to figures 4 to 8, the computer system used in connection with the first embodiment of the method of the invention is basically the same and differs in that there is a second client system 400, connected to the server system 100 by means of the telecommunication line 204, of any appropriate known type, too. The client system 400 is of a known type too, and can be similar or different from the client system 300. Advantageously the second client system 400 can be used by another user 502, either wanting to share data with the first user 501 and/or wanting to work with his own data under the security conditions offered by the system of the invention, in the same manner as described above in connection with the first client system 300.
The initialisation of the computer system can be made in a similar manner as in the first embodiment described above, both for the first client system 300 and for the second client system 400. In this case, with reference to Fig. 5 where k= 1 refers to client 300 and k=2 refers to client 400, each of the client systems generates during initialisation one pair of asymmetric keys, comprising public and private part, respectively Wpu1, Wpr1, Wpu2 and Wpr2, instead of only one symmetric key. Wpu1 and Wpu2, reference 122, can be transmitted and stored, each of them encrypted by means of a community public key Cpu, also in the storage means 121 of the server 100. The community private key Cpr is also transmitted and stored in storage means 121 of the server system in two encrypted forms during initialisation of the system, obtained using the users public keys, Wpu1 and Wpu2, references 125 and 126 and Fig. 5. The first steps of the authentication procedure to the server 100 by first client system 300 and second client system 400 follow a similar pattern as in the first embodiment where only one client system is provided. This authentication procedure is shown in Fig. 6 for the first client server 300, whereby the user 1 is prompted to provide his user ID or username and the passphrase PP1, stage 700. The client system 300 hashes, step 702, the passphrase PP1 using hashing function 1, thus producing hash1 of user 1. The client 300 transmits, via the telecommunication means, hash1 of user 1 to the server 100 and the latter compares hash1 of user 1 received from the client 300 with the hash1 of user 1 stored following the initialisation procedure, step 706.
If this authentication, step 706, is successful the server 100 provides the client 300 with the encrypting key Dpr1 in encrypted form via telecommunication means 203.
At the same time, in step 704, the passphrase PP1 is hashed by a second hashing function 2, producing a hash2 of user 1 which is stored in the storage means 310 of the client system 300 and is used for decrypting the encrypted key Dpr1, step 710. After the decrypted key Dpr1 is validated, the authentication procedure is completed and the user 1 authenticated.
The decrypted key Dpr1 is then used by the client to decrypt, step 712, the decrypting key Wpr1, which was kept stored in encrypted form advantageously in the permanent storage means 313 of the client system 300.
The access procedure for the second client server 400 is shown in Fig. 7, whereby the user 2 is prompted to provide his user ID or username and his own passphrase PP2, preferably different from that of user 1, stage 800. The client system 400 hashes, step 802, the passphrase PP2 using hashing function 1, thus producing hash1 of user 2, The client 400 transmits, via the telecommunication means, hash1 of user 2 to the server 100 and the latter makes the authentication of hash1 of user 2 received from the client 400 with the hash1 of user 2 stored following the initialisation procedure, step 806.
If this authentication, step 806, is successful the server 100 provides the client 400 with the encrypting key Dpr2 in encrypted form via telecommunication means 204.
At the same time, in step 804, the passphrase PP2 is hashed by a second hashing function 2, producing a hash2 of user 2 which is stored in the temporary storage means 420 of the client system 400 and is used for decrypting the encrypted key Dpr2, step 810. After the decrypted key Dpr2 is validated, the authentication procedure is completed and user 2 authenticated.
The decrypted key Dpr2 is then used by the client to decrypt the decrypting key Wpr2, which was kept stored in encrypted form in the permanent storage means 413 of the client system 400.
After authentication of client system 300 and client system 400 has taken place, the two users of the client systems can either work independently using the system as described in the first embodiment or can exchange encrypted data. In this latter case, for example the server will provide client system 300 with the community private key Cpr previously encrypted using Wpu1, step 900. The Cpr is decrypted by client system 300 by means of the decrypting key Wpr1, step 902.
The server system 100 transmits the encrypted key Wpu2 of client system 400 to client system 300. The key Cpr is used by client 300 to decrypt Wpu2, step 906. At the same time client 300 generates a document encrypting key F1, step 912, by means of which it encrypts any message to be sent to client 400, step 914. In the following step client 300 encrypts F1 by means of Wpu2, step 916, and the encrypted document, together with the encrypted document key F1 are sent, step 918, to the server 100 which forwards it to client system 400, step 920.
Client system 400 decrypts the key F1, step 922, by means of Wpr2, which was stored in permanent storage means of client system 400, and subsequently it decrypts the document by means of F1, step 924.
Alternatively to this option or in parallel to it, client system 400 can work separately on the same document or on a different document. If this document already existed it might be either on the storage means of the server system 100, in encrypted form or on the storage means of the client system 400. The client system 400 decrypts by means of Wpr2 the document encrypting key F2, step 904 and successively the document is decrypted by means of the document encrypting key F2, step 906. This message may either be sent to client system 300, to the server system 100, or be kept in the storage means of the client system 300, or the user can choose any combination of the latter, according to its needs.
Obviously the method of the invention can be extended to the case where more than two clients are connected to the server, without departing from the scope of the invention.
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| EP1249981A | Cites | European Patent Office (EPO) |
| US5892828A | Cites | United States of America |
| US6154543A | Cites | United States of America |
7 members in 4 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 03016787 | European Patent Office (EPO) | A | |
| EP20030016787 | – | – | – |
Members7
| Document | Office | Kind | |
|---|---|---|---|
| EP1501238A1 | European Patent Office (EPO) | A1 | |
| US2005033963A1 | United States of America | A1 | |
| EP1501238B1This record | European Patent Office (EPO) | B1 | |
| AT378747T | Austria | T | |
| ATE378747T1 | Austria | T1 | |
| DE60317498D1 | Germany | D1 | |
| DE60317498T2 | Germany | T2 |
63 legal events, as 6 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Notification of lapseLapsedST | ST | FR | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Patent reinstated in contracting state [announced from national office to epo]PGRI | PGRI | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Modification of the scope of the patentLE BREVET A ETE REACTIVE SELON LA DEMANDE DE POURSUITE DE LA PROCEDURE DU 14.07.2010.AEN | AEN | CH | |
| Name/firm changedPFA | PFA | CH | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Fr: translation filedET | ET | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents actLapsedNLV1 | NLV1 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Corresponds to:REF | REF | EP | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| First examination report despatched17Q | 17Q | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Designation fees paidAKX | AKX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1501238
- Publication, DOCDB
- 1501238
- Publication, EPODOC
- EP1501238
- Application
- 3016787
- Application, DOCDB
- 03016787
- Application, EPODOC
- EP20030016787
Titles3
- German
- Verfahren und System zur Schlüsseldistribution mit einem Authentifizierungschritt und einem Schlüsseldistributionsschritt unter Verwendung von KEK (key encryption key)
- English
- Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key)
- French
- Méthode et système de distribution de clé comprenant une étape d'authentification et une de distribution de clé à l'aide de KEK (key encryption key)
Classification
- CPC, 3
- H04L9/0822
- H04L9/3226
- H04L9/3236
- IPC, 3
- H04L9 30
- H04L9 32
- G06F1 00
Designated states1
- Contracting states, 1
- Türkiye
