EP1501238A1 - Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key) - Google Patents
Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key) Download PDFInfo
- Publication number
- EP1501238A1 EP1501238A1 EP03016787A EP03016787A EP1501238A1 EP 1501238 A1 EP1501238 A1 EP 1501238A1 EP 03016787 A EP03016787 A EP 03016787A EP 03016787 A EP03016787 A EP 03016787A EP 1501238 A1 EP1501238 A1 EP 1501238A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- key
- client system
- hash
- private
- encrypted
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/0822—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using key encryption key
-
- 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/3226—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 using a predetermined code, e.g. password, passphrase or PIN
-
- 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/3236—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 using cryptographic hash functions
Definitions
- the present invention relates to data communications systems' security and, more particularly, to the secure processing of messages using cryptography.
- it refers to authentication methods and to a data management and protection system for data exchanged between server and clients.
- Cryptography algorithms are widely used to ensure the security or integrity of messages in data communications systems.
- RSA Rivest-Shamir-Aldeman
- 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.
- 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.
- 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.
- 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.
- the recipient uses the private key to decrypt the secret key, and then decrypts the message using the secret key.
- encryption key e.g. 128 bits confronted to 56 bits
- basic security principles suggest to frequently change encryption keys and to use different keys to encrypt a large quantity of data.
- 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.
- 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.
- 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.
- 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.
- the foregoing objects are achieved by means of a method for authentication, data communication, storage and retrieval in a distributed key cryptography system using 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.
- the second data processing system 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.
- 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.
- 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.
- no information received by the first data processing system during the authentication procedure is relative to the encryption keys stored in its data storage.
- the second data processing system must receive the encrypted second key encrypting key before it can readily perform any data decryption.
- the figures 2 and 5 show shorthand diagrammatic notation to represent encryption and decryption operations.
- both such operations require two input quantities (the data and the key) and produce one output data stream.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the users can work with the system.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 usemame 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Storage Device Security (AREA)
- Computer And Data Communications (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- 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.
- 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 US-A-6370250, 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.
- 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.
- 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 in a distributed key cryptography system using 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.
- Preferred embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which:
- 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;
- Fig.1a shows diagrammatic notation to represent encryption and decryption operations according to the invention;
- Fig. 2 shows the basic scheme of the functional relations between the encrypting/decrypting keys and hashes in the method according to the invention.
- Fig. 3 shows a flow diagram of an embodiment of the method for authentication, data communication, storage and retrieval according to the invention;
- 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;
- 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;
- 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.
-
- 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, aCPU 120, data storage means which can be either unique or separated in different parts for storing different type of data. Apart 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, theserver 100 has an interface for communicating with telecommunication means 200 to connect to a second data processing system, generally aclient 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 aCPU 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 magnetichard disc 310. - The user controls and accesses the
client 300 by means of akeyboard 202 or of any othersuitable 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 theserver 100 and kept inappropriate 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 ofclient 300 and ofserver 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 thekey 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. Theclient system 300 hashes,step 602, the passphrase PP usinghashing function 1, thus producing hash1. Theclient 300 transmits, via the telecommunication means, hash1 to the server and the latter performs the authentication of hash1 received from theclient 300 with thehash 1 previously stored following the initialisation procedure,step 606. - If authentication,
step 606, is successful theserver 100 provides theclient 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 asecond hashing function 2, producing ahash 2 which is stored in storage means of theclient 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. Theclient system 300 decrypts the private key Fk by means of the key Wk,step 616. By means of the decrypted private key Fk, theclient 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 theserver 100. In the latter case theencrypted document 618 is sent via the telecommunication means 200 to theclient 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 theserver system 100 by means of thetelecommunication line 204, of any appropriate known type, too. Theclient system 400 is of a known type too, and can be similar or different from theclient system 300. Advantageously thesecond client system 400 can be used by anotheruser 502, either wanting to share data with thefirst 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 thefirst 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 thesecond client system 400. In this case, with reference to Fig. 5 where k= 1 refers toclient 300 and k=2 refers toclient 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 theserver 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 theserver 100 byfirst client system 300 andsecond 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 thefirst client server 300, whereby theuser 1 is prompted to provide his user ID or username and the passphrase PP1,stage 700. Theclient system 300 hashes,step 702, the passphrase PP1 usinghashing function 1, thus producing hash1 ofuser 1,. Theclient 300 transmits, via the telecommunication means, hash1 ofuser 1 to theserver 100 and the latter compares hash1 ofuser 1 received from theclient 300 with the hash1 ofuser 1 stored following the initialisation procedure, step 706. - If this authentication, step 706, is successful the
server 100 provides theclient 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 asecond hashing function 2, producing a hash2 ofuser 1 which is stored in the storage means 310 of theclient 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 theuser 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 theuser 2 is prompted to provide his user ID or usemame and his own passphrase PP2, preferably different from that ofuser 1,stage 800. Theclient system 400 hashes,step 802, the passphrase PP2 usinghashing function 1, thus producing hash1 ofuser 2, Theclient 400 transmits, via the telecommunication means, hash1 ofuser 2 to theserver 100 and the latter makes the authentication of hash1 ofuser 2 received from theclient 400 with the hash1 ofuser 2 stored following the initialisation procedure,step 806. - If this authentication,
step 806, is successful theserver 100 provides theclient 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 asecond hashing function 2, producing a hash2 ofuser 2 which is stored in the temporary storage means 420 of theclient 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 anduser 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 andclient 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 provideclient system 300 with the community private key Cpr previously encrypted using Wpu1,step 900. The Cpr is decrypted byclient system 300 by means of the decrypting key Wpr1,step 902. - The
server system 100 transmits the encrypted key Wpu2 ofclient system 400 toclient system 300. The key Cpr is used byclient 300 to decrypt Wpu2,step 906. At thesame time client 300 generates a document encrypting key F1,step 912, by means of which it encrypts any message to be sent toclient 400,step 914. In the followingstep 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 theserver 100 which forwards it toclient system 400,step 920. -
Client system 400 decrypts the key F1,step 922, by means of Wpr2, which was stored in permanent storage means ofclient 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 theserver system 100, in encrypted form or on the storage means of theclient system 400. Theclient 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 toclient system 300, to theserver system 100, or be kept in the storage means of theclient 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.
Claims (12)
- A method for authentication, data communication, storage and retrieval in a distributed key cryptography system, comprising the following steps:a) at least one client system (300) hashing a passphrase using a first hashing function, so as to produce a first'hash,b) the at least one client system (300) transmitting, via telecommunication means (200), the first hash to a server system (100);c) the server system (100) performing an authentication of the first hash comparing it with a predefined hash;d) the server system (100) providing the at least one client system (300) with at least a second key encrypting key (Dk, Dpr1) in encrypted form over telecommunication means (200);e) the at least one client system (300) hashing the passphrase by means of a second hashing function, so as to produce a second hash;f) the at least one client system (300) utilising the second hash for decrypting the encrypted second key encrypting key (Dk, Dpr1);g) the at least one client system (300) utilising the decrypted second key encrypting key (Dk, Dpr1) for decrypting a first key encrypting key (Wk, Wpr1), stored in encrypted form in storage means (311, 313) of the client system (300);h) the server system (100) transmitting at least one private 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) decrypting the private key (Fk, F1) by means of the first key encrypting key (Wk, Wpr1);l) at least one client system (300) decrypting data by means of the private key (Fk, F1).
- Method according to claim 1, further comprising:storing the first hash in permanent storage means of the server system (100) during an initialisation procedure and storing the second hash only in temporary storage means of the first client system (300) during operation.
- Method according to claim 2, further comprising:before step a) prompting the user to provide a user ID and a passphrase.
- Method according to claim 3, further comprising:carrying out step d) if authentication is successful.
- Method according to claim 4, further comprising:storing the data in encrypted form in storage means of the server (100).
- Method according to claim 5, further comprising:the first key encrypting key (Wk) being of a symmetric type.
- Method according to claim 6, further comprising:providing a second client system (400);providing a second second key encrypting key (Dpr2) and a second private key (F2);replacing the first key encrypting key (Wk) with first public and private keys, (Wpu1, Wpr1) and with second public and private keys (Wpu2, Wpr2).providing community public and private keys (Cpu, Cpr)
- Method according to claim 7, whereby said community public and private keys (Cpu, Cpr), said second second key encrypting key (Dpr2), a second private key (F2) are stored in storage means of the server system (100) and said first public and private keys, (Wpu1, Wpr1) and second public and private keys (Wpu2, Wpr2) are stored in encrypted form in storage means of respective said client systems (300, 400).
- System for authentication, data communication, storage and retrieval in a distributed key cryptography system, comprising:a) means in a client system for hashing a passphrase using a first hashing function, so as to produce a first hash;b) means in the client system (300) for transmitting, via telecommunication means (200), 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 a predefined hash;d) means in the server system (100) providing the client system (300) with a second key encrypting key (Dk) in encrypted form over telecommunication means (200);e) means in the client system (300) hashing the passphrase by means of a second hashing function, so as to produce a second hash;f) means in the client system (300) for utilising the second hash for decrypting the encrypted second key encrypting key (Dk);g) means the client system (300) for utilising the decrypted second key encrypting key (Dk) for decrypting a first key encrypting key (Wk), stored in encrypted form in storage means of the client system (300);h) means in the server system (100) for transmitting a private key (Fk), stored in encrypted form in storage means of the server system (100), to the client system (300);i) means for decrypting the private key (Fk) by means of the first key encrypting key (Wk);l) means in the client system (300) for decrypting data by means of the private key (Fk).
- System according to claim 9, further comprising:a second client system (400);means for providing community public and private keys (Cpu, Cpr), a second second key encrypting key (Dpr2) and a second private key (F2);means for replacing the first key encrypting key (Wk) with first public and private keys, (Wpu1, Wpr1) and second public and private keys (Wpu2, Wpr2);means in the server system (100) for storing in storage means of server system (100) said community public and private keys (Cpu, Cpr), said second second key encrypting key (Dpr2), a second private key (F2);means for storing said first public and private keys, (Wpu1, Wpr1) and second public and private keys (Wpu2, Wpr2) in encrypted form in storage means of respective said client systems (300, 400).
- A computer program product in a computer usable medium, comprising:a) instructions in a client system for hashing a 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;b) instructions in the client system for transmitting, via telecommunication means (200), the first hash to the server system (100);c) instructions in the server system (100) for performing an authentication of the first hash comparing it with a predefined hash;d) instructions in the server system (100) for providing the client system (300) with a second key encrypting key (Dk) in encrypted form over telecommunication means (200);e) instructions in the client system (300) for hashing the passphrase by means of a second hashing function, so as to produce a second hash;f) instructions in the client system (300) for utilising the second hash for decrypting the encrypted second key encrypting key (Dk);g) instructions in the client system (300) for utilising the decrypted second key encrypting key (Dk) for decrypting a first key encrypting key (Wk), stored in encrypted form in storage means of the client system (300);h) instructions in the server system (100) for transmitting a private key (Fk), stored in encrypted form in storage means of the server system (100), to the client system (300);i) instructions in for decrypting the private key (Fk) by means of the first key encrypting key (Wk);l) instructions in the client system (300) for decrypting data by means of the private key (Fk).
- A computer program product according to claim 11, further comprising:instructions for providing community public and private keys (Cpu, Cpr), a second second key encrypting key (Dpr2) and a second private key (F2);instructions for replacing the first key encrypting key (Wk) with first public and private keys, (Wpu1, Wpr1) and second public and private keys (Wpu2, Wpr2);
instructions in the server system (100) for storing in storage means of the server system (100) said community public and private keys (Cpu, Cpr), said second second key encrypting key (Dpr2), a second private key (F2);instructions for storing said first public and private keys, (Wpu1, Wpr1) and second public and private keys (Wpu2, Wpr2) in encrypted form in storage means of respective said client systems (300, 400).
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AT03016787T ATE378747T1 (en) | 2003-07-23 | 2003-07-23 | METHOD AND SYSTEM FOR KEY DISTRIBUTION WITH AN AUTHENTICATION STEP AND A KEY DISTRIBUTION STEP USING KEK (KEY ENCRYPTION KEY) |
EP03016787A EP1501238B1 (en) | 2003-07-23 | 2003-07-23 | Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key) |
DE60317498T DE60317498T2 (en) | 2003-07-23 | 2003-07-23 | Method and system for key distribution with an authentication step and a key distribution step using KEK (key encryption key) |
US10/897,836 US20050033963A1 (en) | 2003-07-23 | 2004-07-22 | Method and system for authentication, data communication, storage and retrieval in a distributed key cryptography system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03016787A EP1501238B1 (en) | 2003-07-23 | 2003-07-23 | Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key) |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1501238A1 true EP1501238A1 (en) | 2005-01-26 |
EP1501238B1 EP1501238B1 (en) | 2007-11-14 |
Family
ID=33483933
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03016787A Expired - Lifetime EP1501238B1 (en) | 2003-07-23 | 2003-07-23 | Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key) |
Country Status (4)
Country | Link |
---|---|
US (1) | US20050033963A1 (en) |
EP (1) | EP1501238B1 (en) |
AT (1) | ATE378747T1 (en) |
DE (1) | DE60317498T2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2990818A1 (en) * | 2012-05-21 | 2013-11-22 | Myocean It | Method for transfer of digital documents between set of terminals, involves deciphering symmetrical key using private asymmetrical key associated with terminal, and deciphering document using deciphered symmetrical key |
CN103561023A (en) * | 2013-10-31 | 2014-02-05 | 曙光云计算技术有限公司 | Method and device for sending and receiving communication information |
EP3299990A1 (en) * | 2016-09-23 | 2018-03-28 | Synology Incorporated | Electronic device server and method for communicating with server |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006071695A (en) * | 2004-08-31 | 2006-03-16 | Yamatake Corp | Encrypting and decrypting program, and encryption system |
US7477908B2 (en) | 2004-12-13 | 2009-01-13 | Research In Motion Limited | Messaging protocol/service switching methods and devices |
US7636940B2 (en) * | 2005-04-12 | 2009-12-22 | Seiko Epson Corporation | Private key protection for secure servers |
US20080276309A1 (en) * | 2006-07-06 | 2008-11-06 | Edelman Lance F | System and Method for Securing Software Applications |
US8683549B2 (en) * | 2007-03-23 | 2014-03-25 | Microsoft Corporation | Secure data storage and retrieval incorporating human participation |
CA2702780C (en) * | 2008-05-12 | 2016-08-30 | Research In Motion Limited | Security measures for countering unauthorized decryption |
US20100153342A1 (en) * | 2008-12-17 | 2010-06-17 | Alistair Duncan | Vim next generation - migration |
US9047477B2 (en) * | 2009-05-26 | 2015-06-02 | Microsoft Technology Licensing, Llc | Distributed key encryption in servers |
US8862889B2 (en) * | 2011-07-02 | 2014-10-14 | Eastcliff LLC | Protocol for controlling access to encryption keys |
US8856519B2 (en) | 2012-06-30 | 2014-10-07 | International Business Machines Corporation | Start method for application cryptographic keystores |
US9294267B2 (en) * | 2012-11-16 | 2016-03-22 | Deepak Kamath | Method, system and program product for secure storage of content |
US9639687B2 (en) * | 2014-11-18 | 2017-05-02 | Cloudfare, Inc. | Multiply-encrypting data requiring multiple keys for decryption |
US10237270B2 (en) | 2016-09-29 | 2019-03-19 | International Business Machines Corporation | Distributed storage of authentication data |
US10560476B2 (en) | 2017-02-22 | 2020-02-11 | International Business Machines Corporation | Secure data storage system |
US11451521B2 (en) * | 2018-10-18 | 2022-09-20 | Paypal, Inc. | Systems and methods for encrypted data transmission |
EP3699800A1 (en) * | 2019-02-22 | 2020-08-26 | Atos Information Technology GmbH | Method of distributing an object in a document management system, computer program, document management system |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5892828A (en) * | 1996-10-23 | 1999-04-06 | Novell, Inc. | User presence verification with single password across applications |
US6154543A (en) * | 1998-11-25 | 2000-11-28 | Hush Communications Anguilla, Inc. | Public key cryptosystem with roaming user capability |
EP1249981A1 (en) * | 2001-04-02 | 2002-10-16 | NuMeme Limited | A security service system and method |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6069957A (en) * | 1997-03-07 | 2000-05-30 | Lucent Technologies Inc. | Method and apparatus for providing hierarchical key system in restricted-access television system |
US6834112B1 (en) * | 2000-04-21 | 2004-12-21 | Intel Corporation | Secure distribution of private keys to multiple clients |
US6950523B1 (en) * | 2000-09-29 | 2005-09-27 | Intel Corporation | Secure storage of private keys |
-
2003
- 2003-07-23 EP EP03016787A patent/EP1501238B1/en not_active Expired - Lifetime
- 2003-07-23 DE DE60317498T patent/DE60317498T2/en not_active Expired - Lifetime
- 2003-07-23 AT AT03016787T patent/ATE378747T1/en not_active IP Right Cessation
-
2004
- 2004-07-22 US US10/897,836 patent/US20050033963A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5892828A (en) * | 1996-10-23 | 1999-04-06 | Novell, Inc. | User presence verification with single password across applications |
US6154543A (en) * | 1998-11-25 | 2000-11-28 | Hush Communications Anguilla, Inc. | Public key cryptosystem with roaming user capability |
EP1249981A1 (en) * | 2001-04-02 | 2002-10-16 | NuMeme Limited | A security service system and method |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2990818A1 (en) * | 2012-05-21 | 2013-11-22 | Myocean It | Method for transfer of digital documents between set of terminals, involves deciphering symmetrical key using private asymmetrical key associated with terminal, and deciphering document using deciphered symmetrical key |
CN103561023A (en) * | 2013-10-31 | 2014-02-05 | 曙光云计算技术有限公司 | Method and device for sending and receiving communication information |
EP3299990A1 (en) * | 2016-09-23 | 2018-03-28 | Synology Incorporated | Electronic device server and method for communicating with server |
Also Published As
Publication number | Publication date |
---|---|
DE60317498T2 (en) | 2008-11-06 |
EP1501238B1 (en) | 2007-11-14 |
ATE378747T1 (en) | 2007-11-15 |
DE60317498D1 (en) | 2007-12-27 |
US20050033963A1 (en) | 2005-02-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10803194B2 (en) | System and a method for management of confidential data | |
CN109495274B (en) | Decentralized intelligent lock electronic key distribution method and system | |
KR100734162B1 (en) | Method and apparatus for secure distribution of public/private key pairs | |
US6317829B1 (en) | Public key cryptography based security system to facilitate secure roaming of users | |
EP1501238B1 (en) | Method and system for key distribution comprising a step of authentication and a step of key distribution using a KEK (key encryption key) | |
CN108768951B (en) | Data encryption and retrieval method for protecting file privacy in cloud environment | |
US6834112B1 (en) | Secure distribution of private keys to multiple clients | |
US7688975B2 (en) | Method and apparatus for dynamic generation of symmetric encryption keys and exchange of dynamic symmetric key infrastructure | |
EP0725512B1 (en) | Data communication system using public keys | |
US7395549B1 (en) | Method and apparatus for providing a key distribution center without storing long-term server secrets | |
KR101130415B1 (en) | A method and system for recovering password protected private data via a communication network without exposing the private data | |
EP0755598A1 (en) | Computer network cryptographic key distribution system | |
WO2002037749A1 (en) | Secure authentication of users via intermediate parties | |
US7266705B2 (en) | Secure transmission of data within a distributed computer system | |
CN110932851A (en) | PKI-based multi-party cooperative operation key protection method | |
EP1079565A2 (en) | Method of securely establishing a secure communication link via an unsecured communication network | |
US11917056B1 (en) | System and method of securing a server using elliptic curve cryptography | |
WO2000022496A2 (en) | System and method of sending and receiving secure data using anonymous keys | |
JP3684266B2 (en) | Access control method and system for encrypted shared data | |
KR100681005B1 (en) | Key roaming method, and method for the same | |
KR100401063B1 (en) | the method and the system for passward based key change | |
US20240214187A1 (en) | System and Method of Creating Symmetric Keys Using Elliptic Curve Cryptography | |
Reddy et al. | Data Storage on Cloud using Split-Merge and Hybrid Cryptographic Techniques | |
CN116346329A (en) | Encryption data supervision method and system based on cryptographic technology | |
CN113162766A (en) | Key management method and system for key component |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK |
|
17P | Request for examination filed |
Effective date: 20050725 |
|
AKX | Designation fees paid |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
17Q | First examination report despatched |
Effective date: 20050902 |
|
17Q | First examination report despatched |
Effective date: 20050902 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 60317498 Country of ref document: DE Date of ref document: 20071227 Kind code of ref document: P |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080225 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080214 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080214 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 |
|
ET | Fr: translation filed | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080414 |
|
26N | No opposition filed |
Effective date: 20080815 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080215 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20080731 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20080723 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090731 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090731 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20080723 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080515 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: AEN Free format text: LE BREVET A ETE REACTIVE SELON LA DEMANDE DE POURSUITE DE LA PROCEDURE DU 14.07.2010. Ref country code: CH Ref legal event code: PFA Owner name: EISST LTD Free format text: EISST LIMITED#6-8 UNDERWOOD STREET#LONDON N17 JQ (GB) -TRANSFER TO- EISST LTD#FAIRFAX HOUSE 15 FULWOOD PLACE#LONDON WC1V 6AY (GB) |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20071114 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20100722 Year of fee payment: 7 |
|
PGRI | Patent reinstated in contracting state [announced from national office to epo] |
Ref country code: CH Effective date: 20100727 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100731 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100731 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20120717 Year of fee payment: 10 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20130723 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20170127 Year of fee payment: 14 Ref country code: FR Payment date: 20170130 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20170810 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 60317498 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20180330 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170731 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20180723 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180723 |