US20090034714A9 - Systems and methods for identity-based encryption and related cryptographic techniques - Google Patents

Systems and methods for identity-based encryption and related cryptographic techniques Download PDF

Info

Publication number
US20090034714A9
US20090034714A9 US11/431,410 US43141006A US2009034714A9 US 20090034714 A9 US20090034714 A9 US 20090034714A9 US 43141006 A US43141006 A US 43141006A US 2009034714 A9 US2009034714 A9 US 2009034714A9
Authority
US
United States
Prior art keywords
receiver
key
ibe
public key
identity
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
Application number
US11/431,410
Other versions
US7634087B2 (en
US20070041583A1 (en
Inventor
Dan Boneh
Matthew Franklin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Leland Stanford Junior University
University of California Davis
Original Assignee
Individual
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US11/431,410 priority Critical patent/US7634087B2/en
Assigned to BOARD OF TRUSTEES OF THE LELAND STANFORD JUNIOR UNIVERSITY reassignment BOARD OF TRUSTEES OF THE LELAND STANFORD JUNIOR UNIVERSITY ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BONEH, DAN
Assigned to UNIVERSITY OF CALIFORNIA DAVIS reassignment UNIVERSITY OF CALIFORNIA DAVIS ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FRANKLIN, MATTHEW
Publication of US20070041583A1 publication Critical patent/US20070041583A1/en
Publication of US20090034714A9 publication Critical patent/US20090034714A9/en
Priority to US12/589,880 priority patent/US8130964B2/en
Application granted granted Critical
Publication of US7634087B2 publication Critical patent/US7634087B2/en
Priority to US13/369,165 priority patent/US9356779B2/en
Assigned to VENTURE LENDING & LEASING VI, INC., VENTURE LENDING & LEASING VII, INC. reassignment VENTURE LENDING & LEASING VI, INC. SECURITY AGREEMENT Assignors: VOLTAGE SECURITY, INC.
Assigned to VOLTAGE SECURITY, INC. reassignment VOLTAGE SECURITY, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: VENTURE LENDING & LEASING VI, INC., VENTURE LENDING & LEASING VII, INC.
Assigned to JPMORGAN CHASE BANK, N.A. reassignment JPMORGAN CHASE BANK, N.A. SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ARCSIGHT, LLC, ENTIT SOFTWARE LLC
Assigned to JPMORGAN CHASE BANK, N.A. reassignment JPMORGAN CHASE BANK, N.A. SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ARCSIGHT, LLC, ATTACHMATE CORPORATION, BORLAND SOFTWARE CORPORATION, ENTIT SOFTWARE LLC, MICRO FOCUS (US), INC., MICRO FOCUS SOFTWARE, INC., NETIQ CORPORATION, SERENA SOFTWARE, INC.
Assigned to MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC), MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.), BORLAND SOFTWARE CORPORATION, MICRO FOCUS (US), INC., ATTACHMATE CORPORATION, SERENA SOFTWARE, INC, NETIQ CORPORATION reassignment MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC) RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Assignors: JPMORGAN CHASE BANK, N.A.
Assigned to MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC) reassignment MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC) RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Assignors: JPMORGAN CHASE BANK, N.A.
Adjusted expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0838Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these
    • H04L9/0847Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these involving identity based encryption [IBE] schemes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • H04L9/3066Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
    • H04L9/3073Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy involving algebraic varieties, e.g. elliptic or hyper-elliptic curves involving pairings, e.g. identity based encryption [IBE], bilinear mappings or bilinear pairings, e.g. Weil or Tate pairing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/04Masking or blinding

Definitions

  • the field of the present invention relates generally to cryptographic systems.
  • Public-key cryptographic systems allow two people to exchange private and authenticated messages without requiring that they first have a secure communication channel for sharing private keys.
  • One of the most widely used public-key cryptosystem is the RSA cryptosystem disclosed in U.S. Pat. No. 4,405,829.
  • the RSA cryptosystem is currently deployed in many commercial systems. It is used by web servers and browsers to secure web traffic, it is used to ensure privacy and authenticity of e-mail, it is used to secure remote login sessions, and it is at the heart of electronic credit-card payment systems. In short, RSA is frequently used in applications where security of digital data is a concern.
  • each person has a unique pair of keys: a private key that is a secret and a public key that is widely known.
  • This pair of keys has two important properties: (1) the private key cannot be deduced from knowledge of the public key alone, and (2) the two keys are complementary, i.e., a message encrypted with one key of the pair can be decrypted only with the complementary key.
  • both the public key and the private key in a pair are generated together as the output of a key generation algorithm that takes as input a random seed. Consequently, in these cryptosystems, people cannot choose a desired public or private key, but must simply use the keys that are generated for them by a key generation algorithm.
  • CA trusted certificate authority
  • Shamir envisioned a new type of public key encryption scheme (described in A. Shamir, “Identity-based cryptosystems and signature schemes”, in Advances in Cryptology—Crypto ' 84, Lecture Notes in Computer Science, Vol. 196, Springer-Verlag, pp. 47-53, 1984).
  • a person's public key consists of a public identifier, which may be the person's name and network address, or combination of name and e-mail address, social security number, street address, telephone number, or office address.
  • a method of encrypting a first piece of information to be sent by a sender to a receiver uses an encryption key generated from a second piece of information.
  • a bilinear map and the encryption key are used to encrypt at least a portion of the first piece of information to be sent from the sender to the receiver.
  • the bilinear map may be symmetric or asymmetric.
  • the bilinear map may be based on a Weil pairing or a Tate pairing defined on an algebraic group derived from an elliptic curve. More generally, the bilinear map may be based on a pairing defined on algebraic varieties.
  • encrypting the portion of the first piece of information can be completed prior to generating a decryption key corresponding to the encryption key.
  • the second piece of information is known to the receiver prior to the generation of a decryption key corresponding to the encryption key.
  • the second piece of information may comprise a character string such as an e-mail address, name or other identifier associated with the receiver, according to different embodiments of the invention.
  • the second piece of information may also include, according to various embodiments, an attribute associated with the receiver or information corresponding to a time or times, such as a date or series of dates defining one or more time intervals.
  • a decryption key may be provided based on a time that a request for the decryption key is received relative to the information corresponding to a time.
  • the second piece of information may include a message identifier, a credential identifier or a message subject identifier.
  • a message key is generated from the encryption key using a bilinear map, and a cryptographic hash function is applied to the message key.
  • encrypting the portion of the first piece of information includes generating a mask from the second piece of information using a bilinear map. The mask is applied to the portion of the second piece of information.
  • An embodiment of the invention is directed to a method of decrypting ciphertext which has been encrypted by a sender using an identity-based encryption key associated with a receiver.
  • a decryption key derived from the encryption key is obtained.
  • At least a portion of the ciphertext is decrypted using a bilinear map and the decryption key.
  • the bilinear map may be symmetric or asymmetric.
  • the bilinear map may be based on a Weil pairing or a Tate pairing defined on an algebraic group derived from an elliptic curve.
  • the ciphertext is obtained prior to creating the decryption key.
  • the first piece of information is known to the receiver prior to obtaining the ciphertext and prior to obtaining the decryption key.
  • the decryption key may be obtained by sending a request to a private key generator, including information sent together with the ciphertext.
  • An embodiment of the invention is directed to a method of generating a decryption key corresponding to an encryption key.
  • An algebraic group, a group action, and a master key are provided.
  • the encryption key is generated based on a first piece of information.
  • the decryption key is generated based on the group action, the master key and the encryption key.
  • the group action is capable of being calculated in polynomial time.
  • generation of the decryption key in the absence of the master key would require greater than polynomial time.
  • Another embodiment of the invention is directed to a method of providing system parameters for a cryptographic system.
  • Algebraic groups 1 and 2 having an order q are provided, together with associated group actions.
  • a bilinear map is provided that maps pairs of points in 1 to points in 2 .
  • a system parameter representing a member P of G 1 and a system parameter representing a member P pub of G 1 are provided, where P pub is based on the group action of a master key s applied to P.
  • a system parameter representing a set of one or more hash functions H 1 , H 2 , H 3 , or H 4 are provided.
  • a system parameter representing a size n of a message space is provided.
  • the bilinear map may be asymmetric or symmetric.
  • the bilinear map is based on a Weil pairing or a Tate pairing defined on a portion of an elliptic curve.
  • the algebraic group G 1 is defined by an elliptic curve defined over a field of order p and the order q is less than the order p.
  • the length of p is at least 1024 bits and the length of q is no greater than 160 bits.
  • Another embodiment of the invention is directed to a method for managing cryptographic communication including generating shares of a master key.
  • the shares are stored in separate systems.
  • a request from a receiver to obtain a private key is responded to in the separate systems by generating from the respective shares of the master key, corresponding respective shares of the private key.
  • the receiver constructs the private key from the shares of the private key, where the private key corresponds to identifying information of the receiver.
  • Another embodiment of the invention is directed to a method for communicating between a sender and a receiver.
  • a message to be sent from the sender to the receiver is encrypted, and the message is sent from the sender to the receiver.
  • a request for a decryption key is received from the receiver of the message. After receiving the request for the decryption key, information indicating that the receiver has received the message is generated, and the decryption key is provided to the receiver.
  • a return address of the sender is included in the message, and an acknowledgment that the message has been received is sent to the return address.
  • an identification of the message is included in an acknowledgment and the acknowledgment is sent to the sender.
  • the encryption key is derived based on a return address of the sender.
  • Another embodiment of the invention is directed to a method for communicating between a sender and a receiver having a credential. Identifying information of the receiver is obtained. A credential required for the receiver to gain a decryption key is specified, and an encryption key is derived from the identifying information of the receiver and the credential. A message to be sent from the sender to the receiver is encrypted using the encryption key and a bilinear map, and the message is sent from the sender to the receiver. A request for a decryption key is received from the receiver of the message. It is determined whether the receiver has the credential, and if the receiver has the credential, the decryption key is provided to the receiver. The receiver then may use the decryption key and the bilinear map to decrypt the message.
  • Another embodiment of the invention is directed to a method of communicating between a sender and a receiver involving storing a decryption key on a target system.
  • Sets of decryption keys associated with times messages may be decrypted are derived, and the decryption keys are stored on the target system.
  • An encryption key is derived from a string associated with a time a message is to be decrypted.
  • a message is encrypted using the encryption key.
  • the message is received on the target system, and the message is decrypted using a bilinear map and the corresponding decryption key.
  • Another embodiment of the invention is directed to a method of communicating between a sender and receiver involving entities having different responsibilities.
  • a set of decryption keys is derived from a master key and a set of strings associated with different responsibilities.
  • the decryption keys are provided to entities having the respective responsibilities.
  • An encryption key is derived from a string associated with one of the different responsibilities.
  • a message to be sent from the sender to the receiver is encrypted using the encryption key and a bilinear map.
  • An entity having a particular responsibility receives the message and decrypts the message using the respective decryption key and the bilinear map.
  • the string corresponding to the particular responsibility comprises a subject line of an e-mail.
  • FIG. 1 is a block diagram illustrating a cryptosystem according to an embodiment of the invention, showing steps taken by a sender, a receiver, and a private key generator (PKG), and information communicated between them.
  • PKG private key generator
  • FIG. 2 is a block diagram illustrating steps performed by a PKG when generating a private key according to an embodiment of the invention.
  • FIG. 3 is a block diagram illustrating steps performed by a sender when computing a secret message key and using it to encrypt a message intended for a receiver according to an embodiment of the invention.
  • FIG. 4 is a block diagram illustrating steps performed by a receiver when computing a secret message key and using it to decrypt ciphertext received from a sender according to an embodiment of the invention.
  • FIG. 5 is a block diagram illustrating a distributed PKG, according to an embodiment of the invention.
  • FIG. 6 is a block diagram illustrating elements in a cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • FIG. 7 is a block diagram illustrating steps performed by a sender when encrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • FIG. 8 is a block diagram illustrating steps performed by a receiver when decrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • FIG. 9 is a block diagram illustrating steps performed by an escrow when decrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an alternate embodiment of the invention.
  • FIG. 10 is a block diagram illustrating a system for managing credentials in an identity based encryption system according to an embodiment of the invention.
  • FIG. 11 is a block diagram illustrating a system with key delegation according to an embodiment of the invention.
  • FIG. 12 is a block diagram illustrating an encryption system with return receipt according to an embodiment of the invention.
  • the techniques of the present invention are generally implemented on computers connected by a communication medium.
  • the computers are connected by the Internet or another computer network, any communication medium may be used.
  • One embodiment of the invention comprises an identity-based encryption system that uses a secret message key derived from identity-based information.
  • the message key may be used by a sender to encrypt a message, and by a receiver to decrypt the message.
  • the secret message key is computed by the sender from an identity-based public key of the receiver.
  • the same message key may be computed by the receiver from the receiver's private key, which is derived from the receiver's identity-based public key.
  • Both sender and receiver compute the same secret key using a bilinear map. For example, in one embodiment, an asymmetric or symmetric bilinear map ê: 0 ⁇ 1 ⁇ 2 is used where 0 , 1 , 2 are (not necessarily distinct) algebraic groups.
  • the bilinear map is symmetric and often denote it as ê: 1 ⁇ 1 ⁇ 2 .
  • a bilinear map ê that is non-degenerate and efficiently computable will be referred to as an admissible map. It is preferable in some embodiments of the invention that the bilinear map be admissible.
  • a certain variant (involving the map ê) of the computational Diffie-Hellman problem is hard.
  • the map ê is admissible and the orders of 0 , 1 , 2 have a very large prime factor q.
  • the orders of 0 , 1 and 2 may be equal to each other. Without loss of generality, the following description assumes for simplicity that the orders of 0 , 1 , and 2 are all of prime order q.
  • an admissible map ê: 0 ⁇ 1 ⁇ 2 is used to realize an identity-based cryptosystem, as follows.
  • a sender uses a public key Q ID ⁇ 1 associated with a public identifier ID for the intended receiver.
  • the receiver uses a complementary private key d ID ⁇ 1 .
  • the private key is computed from the public key Q ID , a secret master key s ⁇ * q , and a group action of * q on 1 .
  • d ID sQ ID . Since the secret master key s is known only by a trusted PKG, users normally cannot themselves compute private keys.
  • the public key Q ID may be obtained by (1) using a conventional character encoding scheme to map the public identifier ID to a corresponding binary string in ⁇ 0, 1 ⁇ *, and (2) using a hash function H 1 : ⁇ 0, 1 ⁇ * ⁇ * 1 to hash the binary string to the element Q ID of * 1 , where the order of Q ID is q.
  • a message intended for a receiver with public identifier ID may be encrypted and decrypted as follows.
  • the admissible map ê may be used by the sender to determine a secret message key. Although the sender and receiver do not share all the same information, using the fact that the map ê is bilinear, they can use different information to compute the same message key. Since each uses information that is private, the message key is a secret.
  • the element g ID r is an identity-based secret which the sender may use as a secret message key to perform identity-based encryption of a message to the receiver.
  • the sender may then send an encrypted message together with rP to the receiver.
  • This secret message key is equal to the secret message key computed by the sender because of the bilinearity of the ê map.
  • This computed element g ID r ⁇ 2 is thus an identity-based secret of the sender which the receiver may compute using the element rP and the private key sQ ID .
  • This secret may be used as a message key for cryptographic communication between the sender and receiver.
  • the PKG also knows the receiver's private key, so can also compute the secret message key and decrypt the message.
  • the sender, receiver and PKG all have sufficient information to compute the secret message key. No other entity, however, normally has knowledge of the sender's secret r or the receiver's secret sQ ID .
  • the security of this embodiment is related to the difficulty of computing the secret message key, which is based upon a combination of r, s, and Q ID using a bilinear map, without knowledge of r or knowledge of sQ ID .
  • the message key g ID r is used to determine a mask which is used to encrypt and decrypt the bits of the message using an XOR operation (denoted by ‘ ⁇ ’).
  • the one-way encryption scheme outlined above is made more secure by converting it into a chosen ciphertext secure system.
  • a general technique of Fujisaki-Okamoto is used.
  • the master key is broken into components s i distributed among several private key generators in a distributed PKG.
  • each of these private key generators in the distributed PKG computes a private key portion d i using Q and its portion s i of the master key.
  • These private key portions can be combined by the user and used as a single private key d ID to decrypt messages encrypted with Q ID .
  • an ElGamal encryption scheme is provided with built-in key escrow, i.e., where one global escrow key can decrypt ciphertexts encrypted under any public key.
  • the exemplary system described above is adapted as follows. Suppose that the receiver also has knowledge of elements P and sP. Rather than obtaining a private key from the PKG, the receiver generates a public/private key pair by selecting a random x ⁇ * q , computing xP using a group action, and publishing a public key based on the result of the computation.
  • This secret can also be determined from knowledge of the master key s.
  • 1 is a subgroup of an elliptic curve, and an admissible map ê is constructed from the Weil pairing (or Tate pairing) on the elliptic curve.
  • a subgroup is not necessarily smaller than the group, i.e., 1 may be the entire elliptic curve). More generally, 1 may be an abelian variety and ê an admissible pairing of its elements. In embodiments using a map ê: 0 ⁇ 1 ⁇ G 2 where 0 and 1 are distinct, 0 also may be a subgroup of an elliptic curve, or more generally, an abelian variety.
  • the public identifier ID is not limited to an identifier associated with an individual person, but may be an identifier associated with any type of entity including not just individuals but also organizations, governmental agencies, corporations and the like.
  • individual identities forming a group may be naturally combined to produce a joint identity for the group with a corresponding group private key.
  • the group's private key need not be issued by a PKG, but is simply the combination of the separate private keys of the entities composing the group.
  • the basic ID specifying the identity of an entity is not limited to the name, e-mail address, address, or social security number of an entity, but could also include other types of information such as domain names, URLs, 9-digit zip codes, tax identification numbers, and so on.
  • the public identifier ID will contain some character string known to the public to be uniquely associated with a particular entity or collection of entities. In general, however, the public identifier ID can be any arbitrary character string or other arbitrary information.
  • An enhanced identifier may comprise a type of identifier that contains information not necessarily limited to information specifying the identity of a particular entity.
  • an ID can contain a credential descriptor such as a license number, official title, or security clearance associated with an entity.
  • An agency can then manage the credentials by providing private keys only to entities it certifies.
  • an ID can contain a property descriptor such as a serial number, vehicle identification number, patent number, or the like.
  • An agency responsible for registering property owners and authenticating owners can manage property registration by providing private keys only to entities that it registers as true owners. More generally, an association between two or more things can be managed by including identifiers for them in an ID. The PKG then acts as the management authority for the associations between things.
  • Another type of enhanced ID is an identifier that includes a time, a time interval, or a set of time intervals.
  • a private key for such an identifier can then be constructed to automatically expire at a certain time, to automatically activate only after a certain time, or to be valid only for one or more specified time intervals. This technique can be combined with the credential and ownership management to control the time of activation and/or expiration.
  • identity-based encryption systems are not limited to any particular type of identifier.
  • identity-based should be understood in general terms as indicating that any arbitrary character string or other arbitrary information may be used as a basis.
  • an IBE system allows the delegation of decryption capabilities.
  • An entity can set up its own IBE system with its own secret master key, and assume the role of PKG for this IBE system. Because the entity has the master key, it can issue keys to delegate decryption capabilities to others. For example, if the entity is a corporation, the employees can obtain private keys from the corporate PKG. Individuals can be issued private keys matching their names, titles, duties, projects, cases, or any other task-related identifier. In another example, an individual can issue to a laptop private keys that are valid only for the duration of a business trip. If the laptop is lost or stolen, only the keys for that time period are compromised. The master key, which remained at home, is uncompromised.
  • the medium of communication need not be limited to e-mail or the Internet, but could include any communication medium such as printed publications, digital storage media, radio broadcasting, wireless communications, and so on.
  • An exemplary embodiment of an identity-based encryption system and method E uses four randomized algorithms: Setup, Extract, Encrypt, Decrypt:
  • a sender 100 uses Encrypt
  • a receiver 110 uses Decrypt
  • a PKG 120 uses Setup and Extract.
  • the sender 100 obtains an ID of the receiver (e.g., the receiver's e-mail address) and combines it with a randomly selected integer r to compute a secret message key g ID r .
  • the element rP is sent to receiver 110 who combines it with a private key d ID to determine the same message key g ID r . Because the sender and receiver share the secret message key, a message encrypted with the key by the sender can be decrypted by the receiver.
  • the sender encrypts M with the message key to produce ciphertext V which is communicated with rP to the receiver.
  • the receiver uses the secret message key to decrypt the ciphertext to recover the original message.
  • the receiver 110 In order to decrypt messages, however, the receiver 110 must first obtain the private key d ID from the PKG 120 . After the PKG authenticates the identity of the receiver, it provides the receiver with the private key corresponding to the receiver's ID. (Note that, in this embodiment, the PKG can compute any private key in the system, and can thus decrypt any message to any user in the system.)
  • Chosen ciphertext security is the standard acceptable notion of security for a public key encryption scheme.
  • An embodiment of an identity-based encryption system and method may be implemented to satisfy this strong notion of security.
  • the selected level of chosen ciphertext security may be strengthened a bit. The reason is that when an adversary attacks a public key ID in an identity-based system, the adversary might already possess the private keys of users ID 1 , . . . , ID n of her choice.
  • the system remains secure under such an attack. That is, the system remains secure even when the adversary can obtain the private key associated with any identity ID i of her choice (other than the public key ID being attacked). We refer to such queries as private key extraction queries.
  • the system of this embodiment also remains secure even though the adversary is challenged on a public key ID of her choice (as opposed to a random public key).
  • an embodiment of an identity-based encryption system or method is semantically secure against an adaptive chosen ciphertext attack (IND-ID-CCA) if no polynomially bounded adversary A has a non-negligible advantage against the Challenger in the following IND-ID-CCA game:
  • IND-CCA chosen ciphertext security
  • IND-CCA chosen ciphertext security
  • a multiuser IND-CCA may be reducible to single user IND-CCA using a standard hybrid argument. This does not hold in the identity-based settings, IND-ID-CCA, since the adversary gets to choose which public keys to corrupt during the attack.
  • one implementation of the disclosed IBE system can be modified (by removing one of the hash functions) into a system which has chosen ciphertext security when private extraction queries are disallowed.
  • the implementation is insecure when extraction queries are allowed.
  • Semantically secure identity based encryption The proof of security for an implementation of our IBE system makes use of a weaker notion of security known as semantic security (also known as semantic security against a chosen plain-text attack). Semantic security is similar to chosen ciphertext security (IND-ID-CCA) except that the adversary is more limited; it cannot issue decryption queries while attacking the challenge public key.
  • semantic security also known as semantic security against a chosen plain-text attack
  • the public key system is said to be semantically secure if no polynomial time adversary can win the game with a non-negligible advantage.
  • a semantically secure public key system is IND-CPA secure. Semantic security captures our intuition that given a ciphertext the adversary learns nothing about the corresponding plain-text.
  • One embodiment of the invention is directed to an IBE system that makes use of a map ê: 1 ⁇ 1 ⁇ 2 between groups 1 and 2 of order q for some large prime q.
  • a map ê may be called an admissible map if it satisfies the following properties:
  • DDH Decision Diffie-Hellman problem
  • BDH Bilinear Diffie-Hellman Assumption
  • BDH Parameter Generator a randomized algorithm is a BDH parameter generator if (1) takes a security parameter k ⁇ + , (2) runs in polynomial time in k, and (3) outputs a prime number q, the description of two groups 1 , 2 of order q, and the description of an admissible map ê: 1 ⁇ 1 ⁇ 2 .
  • BasicIdent The following describes a basic embodiment, called BasicIdent.
  • Setup, Extract, Encrypt, Decrypt We let k be the security parameter given to the setup algorithm. We let be some BDH parameter generator.
  • the security of the exemplary system is based on the assumption that a variant of the Computational Diffie-Hellman problem in 1 is hard.
  • the technical security details of the encryption scheme are discussed by the inventors in D. Boneh, M. Franklin, “Identity based encryption from the Weil pairing”, extended abstract in Advances in Cryptology—Crypto 2001, Lecture Notes in Computer Science, Vol. 2139, Springer-Verlag, pp. 231-229, 2001, which is incorporated herein by reference.
  • the performance of the system is comparable to the performance of ElGamal encryption in * p .
  • the security of the exemplary system is based on a variant of the computational Diffie-Hellman assumption. Based on this assumption we show that the exemplary system has chosen ciphertext security in the random oracle model.
  • threshold cryptography techniques allow the PKG to be distributed so that the master-key is never available in a single location. Unlike common threshold systems, we show that robustness for the distributed PKG embodiment is free.
  • BasicIdent is a semantically secure identity based encryption scheme (IND-ID-CPA) assuming BDH is hard in groups generated by .
  • Theorem 1 Suppose the hash functions H 1 , H 2 are random oracles. Then BasicIdent is a semantically secure identity based encryption scheme (IND-ID-CPA) assuming BDH is hard in groups generated by .
  • IND-ID-CPA semantically secure identity based encryption scheme
  • BasicPub a related Public Key Encryption scheme (not an identity based scheme), called BasicPub.
  • BasicPub is described by three algorithms: keygen, encrypt, decrypt.
  • a technique of Fujisaki and Okamoto (described in E. Fujisaki and T. Okamoto, “Secure integration of asymmetric and symmetric encryption schemes”, in Advances in Cryptology—Crypto ' 99, Lecture Notes in Computer Science, Vol. 1666, Springer-Verlag, pp. 537-554, 1999, which is incorporated herein by reference) may be appropriately adapted to convert the BasicIdent embodiment of the previous section into a chosen ciphertext secure embodiment of an IBE system (in the sense defined earlier) in the random oracle model.
  • Fujisaki-Okamoto show that if is a one-way encryption scheme then hy is a chosen ciphertext secure system (IND-CCA) in the random oracle model (assuming pk satisfies some natural constraints).
  • IND-CPA semantically secure
  • the proof of Theorem 4 is based on the following result of Fujisaki and Okamoto.
  • BasicPub hy be the result of applying the Fujisaki-Okamoto transformation to BasicPub.
  • Theorem 5 (Fujisaki-Okamoto)
  • ⁇ (k) when attacking BasicPub hy .
  • t(k) has running time t(k)
  • makes at most q D decryption queries and makes at most q H 3 , q H 4 queries to the hash functions H 3 , H 4 respectively.
  • Admissible encodings Let 1 be a group and let A ⁇ 0, 1 ⁇ * be a finite set. We say that an encoding function L: A ⁇ * 1 is admissible if it satisfies the following properties:
  • the BDH parameter generator 1 is believed to satisfy the BDH assumption asymptotically. However, there is still the question of what values of p and q can be used in practice to make the BDH problem sufficiently hard. It is desirable that we can ensure, at the very least, that the discrete log problem in 1 is sufficiently hard. As pointed out earlier, the discrete log problem in 1 is efficiently reducible to discrete log in 2 . Hence, computing discrete log in * p 2 is sufficient for computing discrete log in 1 . In practice, for proper security of discrete log in * p 2 it is desirable to use primes p that are at least 512-bits long (so that the group size is at least 1024 bits long). Consequently, in some embodiments, this BDH parameter generator is used with primes p that may be 512-bits long or more.
  • 1 , 2 be two groups generated by 1 as defined above. Recall that an IBE system discussed earlier uses a hash function H 1 : ⁇ 0, 1 ⁇ * ⁇ * 1 . It suffices to have a hash function H 1 : ⁇ 0, 1 ⁇ * ⁇ A for some set A, and an admissible encoding function L: A ⁇ * 1 . In what follows the set A will be p , and the admissible encoding function L will be called MapToPoint, which may be used in various embodiments of the present invention.
  • algorithm MapToPoint works as follows on input y 0 ⁇ p :
  • Proposition 8 MapToPoint: p ⁇ B ⁇ * 1 is an admissible encoding function.
  • a curve E/ p in this family one can take 1 to be a cyclic subgroup of E( p 6 ) (that is not contained in E( p )) and then use the trace map on the curve E as the endomorphism ⁇ used to define the pairing ê.
  • both encryption and decryption in FullIdent can be made faster in alternate embodiments by using the Tate pairing on elliptic curves rather than the Weil pairing.
  • suitable bilinear maps may be derived from abelian varieties.
  • embodiments of our IBE system are not limited to symmetric maps, but may include asymmetric maps as well.
  • embodiments generally may use maps of the form ê: 0 ⁇ 1 ⁇ 2 where 0 , 1 are groups of prime order q. When 0 and are equal we say the map is symmetric. When 0 and 1 are not equal we say the map is asymmetric.
  • the elements Q ID and P in the asymmetric case are members of 0 and 1 , respectively (or vice versa), and the target group of the hash function H 1 is selected accordingly.
  • the co-BDH assumption we use a slightly strange looking complexity assumption which we call the co-BDH assumption: given random P, aP, bP ⁇ 1 and Q, aQ, cQ ⁇ 0 no polynomial time algorithm can compute ê(P, Q) abc with non-negligible probability. If one is uses this assumption then for embodiments using a curve E/ p from Miyaji et al.
  • the master-key stored at the PKG be protected.
  • One way of protecting this key is by distributing it among different sites using techniques of threshold cryptography. Embodiments of our IBE system support this in a very efficient and robust way.
  • a distributed PKG embodiment can be implemented in a t-out-of-n fashion by giving each of the n PKGs one share s i of a Shamir secret sharing of s mod q.
  • Rabin “Secure Distributed Key Generation for Discrete-Log Based Cryptosystems”, Advances in Cryptology—Eurocrypt ' 99, Lecture Notes in Computer Science, Vol. 1592, Springer-Verlag, pp. 295-310, 1999).
  • the PKGs can execute a cooperative protocol that allows them to jointly generate their respective shares of the master key without the master key ever existing in any one place.
  • a distributed master-key embodiment also enables threshold decryption on a per-message basis, without any need to derive the corresponding decryption key.
  • threshold decryption of BasicIdent ciphertext (U, V) is straightforward if each PKG responds with ê(s i Q ID , U).
  • FIG. 5 is a block diagram illustrating a distributed PKG system, according to an embodiment of the invention.
  • FIG. 5 includes a sender system 501 , receiver system 502 and three PKGs (PKG A 503 , PKG B 504 and PKG C 505 ).
  • each of three PKGs contains a different share of a master key, and any two of the three are able to derive the master key.
  • PKG A 503 , PKG B 504 , and PKG C 505 include, respectively, master key share s 1 , 511 , master key share 52 , 512 , and master key share s 3 , 513 .
  • any two out of these three PKGs could combine their shares to determine the master key, although in this embodiment each PKG secretly holds its master key share.
  • Sender system 501 sends a message to receiver 502 .
  • the message 514 may be encrypted using a public key based on an identifier ID of the receiver.
  • the receiver system queries two of the three PKGs using, for example, the receiver's identity or public key.
  • receiver system 502 makes queries 506 and 507 to PKG A 503 and PKG B 504 , respectively, in order to obtain two shares of the private key.
  • PKG A 503 and PKG B 504 return, respectively, share d 1 , 508 , and share d 2 , 509 , of private key d, 510 .
  • Receiver system 502 is then able to assemble the corresponding private key d ID , which corresponds to the public key with which the message 514 was encrypted. More generally, the receiver could have selected to query any two of the three PKGs. For example, receiver system 502 alternatively could have queried PKGs B and C and combined private key shares d 2 and d 3 to produce the private key 510 . These techniques easily generalize to provide similar embodiments using t-out-of n sharing.
  • Sender system 501 , receiver system 502 as well as PKGs 503 , 504 and 505 may be each implemented as computer systems which include elements such as processors and computer-readable media such as memory and other storage devices. Communication between the respective elements may take place using data packets sent over data networks, or any of various other forms of electronic and data transmission and communication. The communication may transpire over various architectures of communication, such as a computer network, such as the Internet, with various wired, wireless and other communications media.
  • the point P is then chosen to be a point of order q.
  • Each public key ID is converted to a group point by hashing ID to a point Q on the curve and then multiplying the point by a.
  • the system is secure if the BDH assumption holds in the group generated by P.
  • the advantage of this embodiment is that the Weil computation is done on points of small order, and hence is much faster.
  • the private key for the signature scheme is the master key for the IBE scheme.
  • the public key for the signature scheme is the set of global system parameters for the IBE scheme.
  • the IBE system is IND-ID-CCA, then the signature scheme is existentially unforgeable against a chosen message attack. Note that, unlike most signature schemes, this signature verification embodiment is randomized.
  • the ElGamal escrow system works as follows.
  • the Setup is similar to that for BasicIdent.
  • each user selects a secret random number and uses it to generate a public/private key pair.
  • a sender and receiver can then use Encrypt and Decrypt to communicate an encrypted message.
  • the message is secure except for an escrow who can use a master key s to decrypt the message.
  • FIG. 6 is a block diagram illustrating elements in a cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • the system includes a sender system 601 with encryption logic 610 , receiver system 602 with decryption logic 611 , escrow agent system 604 and broadcasting system 605 .
  • Broadcast system 605 sends system parameters to participants such as escrow agent system 604 , receiver system 602 and sender system 601 .
  • the private key x and the public key P pub form a complementary key pair.
  • sender system 601 encrypts a message M with encryption logic 610 .
  • Sender system 601 sends a resulting encrypted message 603 to receiver 602 .
  • Receiver system 602 decrypts the message with decryption logic 611 using the private key x, 607 .
  • broadcast system 605 and escrow agent 604 may be a single entity.
  • the escrow agent key s may be shared in a manner such as in the distributed PKG embodiments described earlier.
  • an exemplary embodiment of the technique involves the following procedures:
  • Another embodiment uses a similar hardness assumption, with an ElGamal encryption system with non-global escrow.
  • each user constructs a public key with two corresponding private keys, and gives one of the private keys to the trusted third party.
  • the trusted third party maintains a database of all private keys given to it by the various users. Although both private keys can be used to decrypt, only the user's private key can be used simultaneously as the signing key for a discrete logarithm based signature scheme.
  • three entities A, B, and C can communicate securely as a group by privately selecting random integers a, b, c and publishing public keys aP, bP, cP.
  • One of them, such as A could encrypt a message using the message key ê(bP, cP) r and transmit it with rP.
  • B could decrypt the message by calculating ê(cP, rP) b and C could decrypt it by calculating ê(bP, rP) c .
  • B could send a message to A and C, or C could send a message to A and B.
  • two of the three entities could publish a joint public key abP.
  • C could encrypt a message using the message key ê(abP, cP) r and transmit it with rP.
  • neither A nor B alone could decrypt the message, but both A and B together could compute ê(cP, rP) ab and jointly decrypt the message.
  • This technique generalizes to any number of entities. For example, C could join A and B by using abP to compute and publish the three-way joint public key abcP. Then anyone could encrypt a message using the message key ê(abcP, xP) r and transmit it with rP. Then only A and B and C together could compute ê(xP, rP) abc and jointly decrypt the message.
  • Embodiments of the invention enable n entities to have shares of a private key d ID corresponding to a given public key ID, so that messages encrypted using ID can only be decrypted if t of the n entities collaborate.
  • the private key d ID is never reconstructed in a single location.
  • Embodiments of our IBE system may support this as follows.
  • d ID sQ ID where s ⁇ * q is the master-key.
  • s 1 , . . . s n ⁇ * q be a t-out-of-n Shamir secret sharing of the master-key s.
  • d i s i Q ID .
  • the sender may encrypt using a public key derived from a piece of information containing a time element, such as a year, date or other time, to help provide key expiration or other forms of temporal key management.
  • key expiration can be done by having Alice encrypt e-mail sent to Bob using the public key: “bob@company.com ⁇ current-year”. In doing so Bob can use his private key during the current year only. Once a year Bob needs to obtain a new private key from the PKG. Hence, we get the effect of annual private key expiration. Note that unlike the existing public key infrastructure, Alice does not need to obtain a new certificate from Bob every time Bob refreshes his private key.
  • embodiments of identity based encryption can provide a very efficient mechanism for implementing ephemeral public keys. Also note that this embodiment can be used to enable Alice to send messages into the future: Bob will only be able to decrypt the e-mail on the date specified by Alice.
  • An embodiment of the invention enables the management of user credentials using an IBE system.
  • FIG. 10 is a block diagram illustrating a system for managing credentials in an identity based encryption system according to an embodiment of the invention.
  • the system includes sender system 1001 , receiver system 1002 and PKG 1003 .
  • Each such system may be implemented as a computer system such as a client or server connected to a computer network.
  • sender 1001 , receiver 1002 and PKG 1003 may each contain processors, such as processor 1014 , processor 1013 and processor 1012 .
  • these systems may include computer-readable storage media, such as computer memory, and may additionally include interfaces to a computer network, including technology allowing for communication with a wired, wireless or other network.
  • Sender system 1001 may include a software plug-in 1017 .
  • Such a plug-in may comprise a software module which performs cryptographic functions.
  • the plug-in includes, according to an embodiment of the invention, items such as cryptographic logic 1004 .
  • Plug-in 1017 may be distributed to various computers such as sender system 1001 and receiver system 1002 through a network in order to roll out functionality associated with identity-based encryption and other communication functionality.
  • Parameters 1015 from a system such as PKG 1003 are also distributed over a computer network or other communications medium to senders and receivers, such as sender system 1001 and receiver system 1002 , who may then use them in conjunction with plug-in 1017 when encrypting or decrypting messages.
  • plug-in 1017 is distributed together with parameters 1014 .
  • parameters 1015 may be distributed separately.
  • Sender system 1001 encrypts a message M using encryption logic 1004 in plug-in 1017 .
  • Encryption logic 1004 encrypts the message using encryption key 1011 , which is based on selected credential 1005 and an identification 1016 of the intended receiver of the message. In some embodiments, the key may be based on other information as well.
  • the sender system 1001 sends the receiver system 1002 information 1006 , e.g., in the form of a data packet transmitted over a network or other communication medium.
  • the information 1006 sent to receiver system 1002 contains the encrypted message and may also contain information 1007 regarding the credential 1005 used as part of the basis for the encryption key.
  • receiver system 1002 sends a request 1009 to PKG 1003 .
  • the request 1009 may include the receiver's identity 1016 and may also include information related to the selected credential 1005 .
  • PKG 1003 verifies the credential of receiver 1002 using credential check logic 1008 . Such logic may be implemented in software, hardware or a combination thereof. If the credential is verified as belonging to the receiver, then PKG 1003 provides a response 1010 to receiver 1002 , which includes a private decryption key 1018 corresponding to the encryption key 1011 . Using the private decryption key, the receiver then may decrypt the encrypted message contained in information 1006 to recover the original message M.
  • embodiments such as this one allow a sender to encrypt a message intended for a receiver, where the decryption of the message by the receiver is contingent upon the validity of the receiver's credential.
  • Another application for embodiments of IBE systems is delegation of decryption capabilities.
  • Bob runs the setup algorithm to generate his own IBE system parameters params and his own master-key.
  • params as Bob's public key.
  • Bob obtains a certificate from a CA for his public key params.
  • Alice wishes to send mail to Bob she first obtains Bob's public key params from Bob's public key certificate.
  • Bob is the only one who knows his master-key and hence there is no key-escrow with this setup.
  • FIG. 12 is a block diagram illustrating an encryption system with return receipt according to an embodiment of the invention.
  • a sender can receive an confirmation that the recipient has received an encrypted message. More generally, upon receipt of a request for a decryption key from a receiver, the PKG takes an action separate from providing a decryption key to the receiver. Such an action comprises providing an acknowledgement to the sender that indicates that the message was received, according to one embodiment.
  • FIG. 12 An embodiment of a system having return receipt capability is illustrated in FIG. 12 .
  • the system includes sender system 1201 , recipient system 1202 and PKG system 1203 .
  • the sender system 1201 , receiver system 1202 and PKG system 1203 may be implemented as computer systems coupled to a computer network.
  • PKG 1203 , sender system 1201 and receiver system 1202 may include processor 1212 , processor 1213 and processor and 1214 , respectively.
  • These computer systems may include elements such as computer readable storage media, computer memory and other storage devices. Additionally, these systems may include interfaces to a computer network, including technology allowing for communication from a wired, wireless or other network. Further, according an embodiment of the invention, communication between the respective elements may take place using data packets sent over a computer network, or using any of various other forms of electronic and data transmission and communication.
  • the sender 1201 encrypts a message M and sends the resulting ciphertext to receiver 1202 in a data package 1204 that also may include return receipt request information 1209 .
  • the return receipt request information may contain, for example, a return address and a message identifier corresponding to the particular message 1204 .
  • the message M is encrypted by the sender using encryption logic 1211 and an encryption key 1215 .
  • Encryption key 1215 may be based on a receiver ID (such as an e-mail address) 1216 and the return receipt request information 1209 . Because the receiver ID and return receipt request information 1209 are used by the sender to determine the encryption key 1215 , the receiver 1202 needs a corresponding decryption key that can be used to decrypt the message.
  • recipient system 1202 in response to receiving message 1204 , sends PKG 1203 a request 1206 , which includes the return receipt request information 1209 and the receiver's ID, 1216 .
  • PKG 1203 sends to receiver 1202 the private decryption key 1205 , which receiver then uses with decryption logic 1217 to decrypt the ciphertext of message 1204 and recover the original message M.
  • PKG 1203 also sends a return receipt 1207 to sender 1201 .
  • PKG 1203 may alternatively store the receipt on storage media as part of a log rather than send a return receipt.
  • Return receipt 1207 may include information such as the message identifier.
  • sender 1201 receives proof that recipient 1202 has received the message 1204 .
  • the system may be initialized by placing plug-in software in various systems, such as sender system 1201 and receiver system 1202 .
  • plug-in software may include system parameters, some of which may be derived from a system master key.
  • Such parameters stored in local devices such as sender 1201 and receiver 1202 are then used to generate encryption keys, perform encryption, perform decryption, and other functions, as appropriate.

Abstract

A method and system for encrypting a first piece of information M to be sent by a sender [100] to a receiver [110] allows both sender and receiver to compute a secret message key using identity-based information and a bilinear map. In a one embodiment, the sender [100] computes an identity-based encryption key from an identifier ID associated with the receiver [110]. The identifier ID may include various types of information such as the receiver's e-mail address, a receiver credential, a message identifier, or a date. The sender uses a bilinear map and the encryption key to compute a secret message key gID r, which is then used to encrypt a message M, producing ciphertext V to be sent from the sender [100] to the receiver [110] together with an element rP. An identity-based decryption key dID is computed by a private key generator [120] based on the ID associated with the receiver and a secret master key s. After obtaining the private decryption key from the key generator [120], the receiver [110] uses it together with the element rP and the bilinear map to compute the secret message key gID r, which is then used to decrypt V and recover the original message M. According to one embodiment, the bilinear map is based on a Weil pairing or a Tate pairing defined on a subgroup of an elliptic curve. Also described are several applications of the techniques, including key revocation, credential management, and return receipt notification.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of copending U.S. patent application Ser. No. 10/218,691 filed Aug. 13, 2002, which claims the benefit of U.S. provisional application No. 60/311,946, filed Aug. 13, 2001, both of which are incorporated herein by reference.
  • STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
  • The present invention was made with the support of DARPA contract F30602-99-1-0530. The U.S. Government has certain rights in the invention.
  • BACKGROUND OF THE INVENTION
  • The field of the present invention relates generally to cryptographic systems.
  • Public-key cryptographic systems allow two people to exchange private and authenticated messages without requiring that they first have a secure communication channel for sharing private keys. One of the most widely used public-key cryptosystem is the RSA cryptosystem disclosed in U.S. Pat. No. 4,405,829. The RSA cryptosystem is currently deployed in many commercial systems. It is used by web servers and browsers to secure web traffic, it is used to ensure privacy and authenticity of e-mail, it is used to secure remote login sessions, and it is at the heart of electronic credit-card payment systems. In short, RSA is frequently used in applications where security of digital data is a concern.
  • According to public-key cryptosystems such as the RSA cryptosystem, each person has a unique pair of keys: a private key that is a secret and a public key that is widely known. This pair of keys has two important properties: (1) the private key cannot be deduced from knowledge of the public key alone, and (2) the two keys are complementary, i.e., a message encrypted with one key of the pair can be decrypted only with the complementary key. In these systems, both the public key and the private key in a pair are generated together as the output of a key generation algorithm that takes as input a random seed. Consequently, in these cryptosystems, people cannot choose a desired public or private key, but must simply use the keys that are generated for them by a key generation algorithm. This has the disadvantage that others cannot encrypt messages to a person until that person generates and publishes a public key. Another problem with this type of cryptosystem is that an impostor can publish a public key and claim that it belongs to someone else. To address this issue, a trusted certificate authority (CA) is used to authenticate individuals and certify to others that the individual's public key is authentic. Unfortunately, this adds complexity to the cryptosystem since a sender must obtain a certificate for every receiver, and must obtain a new certificate every time an existing certificate expires. It also requires receivers to create public keys, publish them, register certificates with the CA, and renew such certificates when they expire.
  • In 1984 Shamir envisioned a new type of public key encryption scheme (described in A. Shamir, “Identity-based cryptosystems and signature schemes”, in Advances in Cryptology—Crypto '84, Lecture Notes in Computer Science, Vol. 196, Springer-Verlag, pp. 47-53, 1984). According to Shamir's scheme, a person's public key consists of a public identifier, which may be the person's name and network address, or combination of name and e-mail address, social security number, street address, telephone number, or office address. Because the public key is the person's pre-existing public identifier (ID) rather than a key produced from a random seed, this kind of public key cryptosystem is called an identity-based encryption (IBE) scheme. Shamir, however, did not provide a concrete, practical IBE cryptosystem. In fact, Shamir argued that existing cryptosystems (such as RSA) could not be adapted to realize a secure IBE cryptosystem.
  • In the years since Shamir proposed his IBE scheme there have been several attempts to realize an identity-based cryptosystem. Some proposals require that users not collude. Other proposals require the private key generator (PKG) to spend an impractically long time for each private key generation request. Some proposals require tamper resistant hardware.
  • In short, there remains a need for improved cryptographic methods and systems.
  • SUMMARY OF THE INVENTION
  • According to one embodiment of the invention, a method of encrypting a first piece of information to be sent by a sender to a receiver uses an encryption key generated from a second piece of information. A bilinear map and the encryption key are used to encrypt at least a portion of the first piece of information to be sent from the sender to the receiver. The bilinear map may be symmetric or asymmetric. The bilinear map may be based on a Weil pairing or a Tate pairing defined on an algebraic group derived from an elliptic curve. More generally, the bilinear map may be based on a pairing defined on algebraic varieties.
  • According to one embodiment of the invention, encrypting the portion of the first piece of information can be completed prior to generating a decryption key corresponding to the encryption key.
  • According to another embodiment of the invention, the second piece of information is known to the receiver prior to the generation of a decryption key corresponding to the encryption key. The second piece of information may comprise a character string such as an e-mail address, name or other identifier associated with the receiver, according to different embodiments of the invention. The second piece of information may also include, according to various embodiments, an attribute associated with the receiver or information corresponding to a time or times, such as a date or series of dates defining one or more time intervals. A decryption key may be provided based on a time that a request for the decryption key is received relative to the information corresponding to a time. According to other embodiments of the invention, the second piece of information may include a message identifier, a credential identifier or a message subject identifier.
  • According to another embodiment of the invention, a message key is generated from the encryption key using a bilinear map, and a cryptographic hash function is applied to the message key.
  • According to another embodiment of the invention, encrypting the portion of the first piece of information includes generating a mask from the second piece of information using a bilinear map. The mask is applied to the portion of the second piece of information.
  • An embodiment of the invention is directed to a method of decrypting ciphertext which has been encrypted by a sender using an identity-based encryption key associated with a receiver. A decryption key derived from the encryption key is obtained. At least a portion of the ciphertext is decrypted using a bilinear map and the decryption key. The bilinear map may be symmetric or asymmetric. The bilinear map may be based on a Weil pairing or a Tate pairing defined on an algebraic group derived from an elliptic curve.
  • According to another embodiment of the invention, the ciphertext is obtained prior to creating the decryption key. According to another embodiment of the invention, the first piece of information is known to the receiver prior to obtaining the ciphertext and prior to obtaining the decryption key. The decryption key may be obtained by sending a request to a private key generator, including information sent together with the ciphertext.
  • An embodiment of the invention is directed to a method of generating a decryption key corresponding to an encryption key. An algebraic group, a group action, and a master key are provided. The encryption key is generated based on a first piece of information. The decryption key is generated based on the group action, the master key and the encryption key. According to one embodiment of the invention, the group action is capable of being calculated in polynomial time. According to another aspect of the invention, generation of the decryption key in the absence of the master key would require greater than polynomial time.
  • Another embodiment of the invention is directed to a method of providing system parameters for a cryptographic system. Algebraic groups
    Figure US20090034714A9-20090205-P00001
    1 and
    Figure US20090034714A9-20090205-P00001
    2 having an order q are provided, together with associated group actions. In addition, a bilinear map is provided that maps pairs of points in
    Figure US20090034714A9-20090205-P00001
    1 to points in
    Figure US20090034714A9-20090205-P00001
    2. In another embodiment, a system parameter representing a member P of G1, and a system parameter representing a member Ppub of G1 are provided, where Ppub is based on the group action of a master key s applied to P. According to other embodiments of the invention, a system parameter representing a set of one or more hash functions H1, H2, H3, or H4 are provided. According to another embodiment of the invention, a system parameter representing a size n of a message space is provided.
  • According to another embodiment of the invention, the bilinear map may be asymmetric or symmetric. In another embodiment the bilinear map is based on a Weil pairing or a Tate pairing defined on a portion of an elliptic curve.
  • According to another embodiment of the invention, the algebraic group G1 is defined by an elliptic curve defined over a field of order p and the order q is less than the order p. According to another aspect of the invention, the length of p is at least 1024 bits and the length of q is no greater than 160 bits.
  • Another embodiment of the invention is directed to a method for managing cryptographic communication including generating shares of a master key. The shares are stored in separate systems. A request from a receiver to obtain a private key is responded to in the separate systems by generating from the respective shares of the master key, corresponding respective shares of the private key. The receiver constructs the private key from the shares of the private key, where the private key corresponds to identifying information of the receiver.
  • Another embodiment of the invention is directed to a method for communicating between a sender and a receiver. A message to be sent from the sender to the receiver is encrypted, and the message is sent from the sender to the receiver. A request for a decryption key is received from the receiver of the message. After receiving the request for the decryption key, information indicating that the receiver has received the message is generated, and the decryption key is provided to the receiver. According to an embodiment of the invention, a return address of the sender is included in the message, and an acknowledgment that the message has been received is sent to the return address. According to another aspect of the invention, an identification of the message is included in an acknowledgment and the acknowledgment is sent to the sender. According to another aspect of the invention, the encryption key is derived based on a return address of the sender.
  • Another embodiment of the invention is directed to a method for communicating between a sender and a receiver having a credential. Identifying information of the receiver is obtained. A credential required for the receiver to gain a decryption key is specified, and an encryption key is derived from the identifying information of the receiver and the credential. A message to be sent from the sender to the receiver is encrypted using the encryption key and a bilinear map, and the message is sent from the sender to the receiver. A request for a decryption key is received from the receiver of the message. It is determined whether the receiver has the credential, and if the receiver has the credential, the decryption key is provided to the receiver. The receiver then may use the decryption key and the bilinear map to decrypt the message.
  • Another embodiment of the invention is directed to a method of communicating between a sender and a receiver involving storing a decryption key on a target system. Sets of decryption keys associated with times messages may be decrypted are derived, and the decryption keys are stored on the target system. An encryption key is derived from a string associated with a time a message is to be decrypted. A message is encrypted using the encryption key. The message is received on the target system, and the message is decrypted using a bilinear map and the corresponding decryption key.
  • Another embodiment of the invention is directed to a method of communicating between a sender and receiver involving entities having different responsibilities. A set of decryption keys is derived from a master key and a set of strings associated with different responsibilities. The decryption keys are provided to entities having the respective responsibilities. An encryption key is derived from a string associated with one of the different responsibilities. A message to be sent from the sender to the receiver is encrypted using the encryption key and a bilinear map. An entity having a particular responsibility receives the message and decrypts the message using the respective decryption key and the bilinear map. According to one embodiment of the invention, the string corresponding to the particular responsibility comprises a subject line of an e-mail.
  • BRIEF DESCRIPTION OF THE DRAWING FIGURES
  • FIG. 1 is a block diagram illustrating a cryptosystem according to an embodiment of the invention, showing steps taken by a sender, a receiver, and a private key generator (PKG), and information communicated between them.
  • FIG. 2 is a block diagram illustrating steps performed by a PKG when generating a private key according to an embodiment of the invention.
  • FIG. 3 is a block diagram illustrating steps performed by a sender when computing a secret message key and using it to encrypt a message intended for a receiver according to an embodiment of the invention.
  • FIG. 4 is a block diagram illustrating steps performed by a receiver when computing a secret message key and using it to decrypt ciphertext received from a sender according to an embodiment of the invention.
  • FIG. 5 is a block diagram illustrating a distributed PKG, according to an embodiment of the invention.
  • FIG. 6 is a block diagram illustrating elements in a cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • FIG. 7 is a block diagram illustrating steps performed by a sender when encrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • FIG. 8 is a block diagram illustrating steps performed by a receiver when decrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an embodiment of the invention.
  • FIG. 9 is a block diagram illustrating steps performed by an escrow when decrypting messages in an ElGamal cryptosystem with escrow decryption capability according to an alternate embodiment of the invention.
  • FIG. 10 is a block diagram illustrating a system for managing credentials in an identity based encryption system according to an embodiment of the invention.
  • FIG. 11 is a block diagram illustrating a system with key delegation according to an embodiment of the invention.
  • FIG. 12 is a block diagram illustrating an encryption system with return receipt according to an embodiment of the invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • The following description provides details of several exemplary embodiments of the cryptographic techniques of the present invention, as well as a technical discussion of the security of the system.
  • Overview
  • As is normally the case with modern cryptosystems, the techniques of the present invention are generally implemented on computers connected by a communication medium. Although typically the computers are connected by the Internet or another computer network, any communication medium may be used.
  • One embodiment of the invention comprises an identity-based encryption system that uses a secret message key derived from identity-based information. The message key may be used by a sender to encrypt a message, and by a receiver to decrypt the message. The secret message key is computed by the sender from an identity-based public key of the receiver. The same message key may be computed by the receiver from the receiver's private key, which is derived from the receiver's identity-based public key. Both sender and receiver compute the same secret key using a bilinear map. For example, in one embodiment, an asymmetric or symmetric bilinear map ê:
    Figure US20090034714A9-20090205-P00001
    0×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 is used where
    Figure US20090034714A9-20090205-P00001
    0,
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 are (not necessarily distinct) algebraic groups. In the case where
    Figure US20090034714A9-20090205-P00001
    0 is equal to
    Figure US20090034714A9-20090205-P00001
    1, we say the bilinear map is symmetric and often denote it as ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2. A bilinear map ê that is non-degenerate and efficiently computable will be referred to as an admissible map. It is preferable in some embodiments of the invention that the bilinear map be admissible.
  • The convention throughout this description will be to denote the group operations of
    Figure US20090034714A9-20090205-P00001
    0 and
    Figure US20090034714A9-20090205-P00001
    1 by addition, and the group operation of
    Figure US20090034714A9-20090205-P00001
    2 by multiplication. For a group
    Figure US20090034714A9-20090205-P00001
    of prime order we use
    Figure US20090034714A9-20090205-P00001
    * to denote the set
    Figure US20090034714A9-20090205-P00001
    *=
    Figure US20090034714A9-20090205-P00001
    \{O} where O is the identity element in the group
    Figure US20090034714A9-20090205-P00001
    . The set of binary strings of arbitrary length is denoted by {0, 1}*. We use
    Figure US20090034714A9-20090205-P00002
    q to denote the group {0, . . . , q−1} under addition modulo q, and we use
    Figure US20090034714A9-20090205-P00002
    + to denote the set of positive integers. We note that there is a natural group action of
    Figure US20090034714A9-20090205-P00002
    q on
    Figure US20090034714A9-20090205-P00001
    given by repeated addition, and we denote the result of the action of an element αε
    Figure US20090034714A9-20090205-P00002
    q on an element Pε
    Figure US20090034714A9-20090205-P00001
    by aP.
  • According to another embodiment of the invention, a certain variant (involving the map ê) of the computational Diffie-Hellman problem is hard. In one implementation the map ê is admissible and the orders of
    Figure US20090034714A9-20090205-P00001
    0,
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 have a very large prime factor q. The orders of
    Figure US20090034714A9-20090205-P00001
    0,
    Figure US20090034714A9-20090205-P00001
    1 and
    Figure US20090034714A9-20090205-P00001
    2 may be equal to each other. Without loss of generality, the following description assumes for simplicity that the orders of
    Figure US20090034714A9-20090205-P00001
    0,
    Figure US20090034714A9-20090205-P00001
    1, and
    Figure US20090034714A9-20090205-P00001
    2 are all of prime order q.
  • In an exemplary embodiment, an admissible map ê:
    Figure US20090034714A9-20090205-P00001
    0×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 is used to realize an identity-based cryptosystem, as follows. To encrypt a message, a sender uses a public key QIDε
    Figure US20090034714A9-20090205-P00001
    1 associated with a public identifier ID for the intended receiver. To decrypt the encrypted message, the receiver uses a complementary private key dIDε
    Figure US20090034714A9-20090205-P00001
    1. The private key is computed from the public key QID, a secret master key sε
    Figure US20090034714A9-20090205-P00002
    *q, and a group action of
    Figure US20090034714A9-20090205-P00002
    *q on
    Figure US20090034714A9-20090205-P00001
    1. In one embodiment, for example, dID=sQID. Since the secret master key s is known only by a trusted PKG, users normally cannot themselves compute private keys. To obtain a private key, an individual may obtain it from the PKG, preferably after being authenticated. At any time, however, anyone can compute the public key QID associated with any public identifier ID even before the corresponding private key has been determined. For example, in one embodiment the public key QID may be obtained by (1) using a conventional character encoding scheme to map the public identifier ID to a corresponding binary string in {0, 1}*, and (2) using a hash function H1: {0, 1}*→
    Figure US20090034714A9-20090205-P00001
    *1 to hash the binary string to the element QID of
    Figure US20090034714A9-20090205-P00001
    *1, where the order of QID is q.
  • In this embodiment, a message intended for a receiver with public identifier ID may be encrypted and decrypted as follows. The admissible map ê may be used by the sender to determine a secret message key. Although the sender and receiver do not share all the same information, using the fact that the map ê is bilinear, they can use different information to compute the same message key. Since each uses information that is private, the message key is a secret.
  • To illustrate how this approach may be implemented, suppose that the sender has knowledge of elements P and sP in
    Figure US20090034714A9-20090205-P00001
    1. In one embodiment, for example, elements P and Ppub=sP in
    Figure US20090034714A9-20090205-P00001
    1 are published system parameters. Now further suppose the sender privately selects a random rε
    Figure US20090034714A9-20090205-P00002
    *q, and uses the receiver's identity-based public key QID to compute gID r=ê(rQID, sP). The element gID r is an identity-based secret which the sender may use as a secret message key to perform identity-based encryption of a message to the receiver. The sender may then send an encrypted message together with rP to the receiver. The receiver then receives rP and uses it together with the private key sQID to compute the secret message key gID r=ê(sQID, rP). This secret message key is equal to the secret message key computed by the sender because of the bilinearity of the ê map. This computed element gID rε
    Figure US20090034714A9-20090205-P00001
    2 is thus an identity-based secret of the sender which the receiver may compute using the element rP and the private key sQID. This secret may be used as a message key for cryptographic communication between the sender and receiver.
  • Note that the PKG also knows the receiver's private key, so can also compute the secret message key and decrypt the message. The sender, receiver and PKG all have sufficient information to compute the secret message key. No other entity, however, normally has knowledge of the sender's secret r or the receiver's secret sQID. The security of this embodiment is related to the difficulty of computing the secret message key, which is based upon a combination of r, s, and QID using a bilinear map, without knowledge of r or knowledge of sQID.
  • In one embodiment, the message key gID r is used to determine a mask which is used to encrypt and decrypt the bits of the message using an XOR operation (denoted by ‘⊕’). Specifically, the ciphertext V of a message M is produced by computing V=M⊕H2(gID r), where H2:
    Figure US20090034714A9-20090205-P00001
    2→{0, 1}n is a hash function, and n is the bit length of the message. Conversely, the message M is recovered from the ciphertext V by computing M=V⊕H2(gID r).
  • In another embodiment, the one-way encryption scheme outlined above is made more secure by converting it into a chosen ciphertext secure system. In one embodiment of the invention, for example, a general technique of Fujisaki-Okamoto is used.
  • In another embodiment, the master key is broken into components si distributed among several private key generators in a distributed PKG. For a given user with a public key QID based on an identifier ID, each of these private key generators in the distributed PKG computes a private key portion di using Q and its portion si of the master key. These private key portions can be combined by the user and used as a single private key dID to decrypt messages encrypted with QID.
  • In another embodiment, an ElGamal encryption scheme is provided with built-in key escrow, i.e., where one global escrow key can decrypt ciphertexts encrypted under any public key. In this embodiment, the exemplary system described above is adapted as follows. Suppose that the receiver also has knowledge of elements P and sP. Rather than obtaining a private key from the PKG, the receiver generates a public/private key pair by selecting a random xε
    Figure US20090034714A9-20090205-P00002
    *q, computing xP using a group action, and publishing a public key based on the result of the computation. In one embodiment, the public key is xP and the complementary private key is d=x(sP). (Thus, xP plays the role of QID, and d=x(sP)=s(xP) plays the role of dID=sQID.) To encrypt a message to the receiver, the sender as before selects a random r and sends rP to the receiver. Then the receiver knows the pair (rP, x(sP)), where x(sP)=d is a secret, while the sender knows the pair (sP, r(xP)), where r(xP) is a secret. Thus, the sender and receiver both can compute g=e(rP, x(sP))=e(sP, r(xP)), where the second equality follows from the bilinearity of ê. This secret, however, can also be determined from knowledge of the master key s. Using the element rP from the sender, the receiver's public key xP, and the master key s, the message key can be computed by evaluating g=ê(rP, s(xP)). It should be noted that this embodiment makes use of a symmetric bilinear map ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2.
  • In several embodiments of the invention,
    Figure US20090034714A9-20090205-P00001
    1 is a subgroup of an elliptic curve, and an admissible map ê is constructed from the Weil pairing (or Tate pairing) on the elliptic curve. (Recall that, by definition, a subgroup is not necessarily smaller than the group, i.e.,
    Figure US20090034714A9-20090205-P00001
    1 may be the entire elliptic curve). More generally,
    Figure US20090034714A9-20090205-P00001
    1 may be an abelian variety and ê an admissible pairing of its elements. In embodiments using a map ê:
    Figure US20090034714A9-20090205-P00001
    0×
    Figure US20090034714A9-20090205-P00001
    1→G2 where
    Figure US20090034714A9-20090205-P00001
    0 and
    Figure US20090034714A9-20090205-P00001
    1 are distinct,
    Figure US20090034714A9-20090205-P00001
    0 also may be a subgroup of an elliptic curve, or more generally, an abelian variety.
  • In other embodiments, various novel applications of identity-based encryption are provided. New and useful applications of IBE systems are possible by using other types of public identifiers, or enhanced public identifiers. For example, the public identifier ID is not limited to an identifier associated with an individual person, but may be an identifier associated with any type of entity including not just individuals but also organizations, governmental agencies, corporations and the like. It should also be noted that individual identities forming a group may be naturally combined to produce a joint identity for the group with a corresponding group private key. The group's private key need not be issued by a PKG, but is simply the combination of the separate private keys of the entities composing the group. It should be noted that the basic ID specifying the identity of an entity is not limited to the name, e-mail address, address, or social security number of an entity, but could also include other types of information such as domain names, URLs, 9-digit zip codes, tax identification numbers, and so on. In many applications, the public identifier ID will contain some character string known to the public to be uniquely associated with a particular entity or collection of entities. In general, however, the public identifier ID can be any arbitrary character string or other arbitrary information.
  • Various useful applications of IBE make use of enhanced public identifiers. An enhanced identifier may comprise a type of identifier that contains information not necessarily limited to information specifying the identity of a particular entity. For example, an ID can contain a credential descriptor such as a license number, official title, or security clearance associated with an entity. An agency can then manage the credentials by providing private keys only to entities it certifies. In one exemplary embodiment, an ID can contain a property descriptor such as a serial number, vehicle identification number, patent number, or the like. An agency responsible for registering property owners and authenticating owners can manage property registration by providing private keys only to entities that it registers as true owners. More generally, an association between two or more things can be managed by including identifiers for them in an ID. The PKG then acts as the management authority for the associations between things.
  • Another type of enhanced ID is an identifier that includes a time, a time interval, or a set of time intervals. A private key for such an identifier can then be constructed to automatically expire at a certain time, to automatically activate only after a certain time, or to be valid only for one or more specified time intervals. This technique can be combined with the credential and ownership management to control the time of activation and/or expiration.
  • From the above examples, it is evident that an identity-based encryption systems according to the present invention are not limited to any particular type of identifier. Thus, the term ‘identity-based’ should be understood in general terms as indicating that any arbitrary character string or other arbitrary information may be used as a basis.
  • According to another embodiment, an IBE system allows the delegation of decryption capabilities. An entity can set up its own IBE system with its own secret master key, and assume the role of PKG for this IBE system. Because the entity has the master key, it can issue keys to delegate decryption capabilities to others. For example, if the entity is a corporation, the employees can obtain private keys from the corporate PKG. Individuals can be issued private keys matching their names, titles, duties, projects, cases, or any other task-related identifier. In another example, an individual can issue to a laptop private keys that are valid only for the duration of a business trip. If the laptop is lost or stolen, only the keys for that time period are compromised. The master key, which remained at home, is uncompromised.
  • It should also be pointed out that the medium of communication need not be limited to e-mail or the Internet, but could include any communication medium such as printed publications, digital storage media, radio broadcasting, wireless communications, and so on.
  • Definitions
  • Identity-Based Encryption. An exemplary embodiment of an identity-based encryption system and method E uses four randomized algorithms: Setup, Extract, Encrypt, Decrypt:
    • Setup: Given a security parameter k, return params (system parameters) and master-key. The system parameters include a description of a finite message space
      Figure US20090034714A9-20090205-P00901
      , and a description of a finite ciphertext space
      Figure US20090034714A9-20090205-P00902
      . Normally, the system parameters will be publicly known, while the master-key will be known only to a Private Key Generator (PKG).
    • Extract: takes as input params, master-key, and an arbitrary IDε{0, 1}*, and returns a private key d. Here ID is an arbitrary string that will be used as a public key, and d is the corresponding private decryption key. The Extract algorithm extracts a private key from the given public key. Because the extraction requires the master-key, it is normally performed by the PKG.
    • Encrypt: takes as input params, ID, and Mε
      Figure US20090034714A9-20090205-P00901
      . It returns a ciphertext Cε
      Figure US20090034714A9-20090205-P00902
      .
    • Decrypt: takes as input params, Cε
      Figure US20090034714A9-20090205-P00902
      , and a private key d. It return Mε
      Figure US20090034714A9-20090205-P00901
      .
      According to an embodiment of the invention, these algorithms satisfy the standard consistency constraint that ensures decryption will faithfully recover any encrypted message. More specifically, when d is the private key generated by algorithm Extract when it is given ID as the public key, then
      Mε
      Figure US20090034714A9-20090205-P00901
      : Decrypt(params, C, d)=M where C=Encrypt(params, ID, M).
  • In an identity-based cryptosystem according to an embodiment of the invention, the above algorithms are used together as illustrated in FIG. 1. A sender 100 uses Encrypt, a receiver 110 uses Decrypt, and a PKG 120 uses Setup and Extract. To send a message M to receiver 110, the sender 100 obtains an ID of the receiver (e.g., the receiver's e-mail address) and combines it with a randomly selected integer r to compute a secret message key gID r. The element rP is sent to receiver 110 who combines it with a private key dID to determine the same message key gID r. Because the sender and receiver share the secret message key, a message encrypted with the key by the sender can be decrypted by the receiver. In particular, the sender encrypts M with the message key to produce ciphertext V which is communicated with rP to the receiver. The receiver then uses the secret message key to decrypt the ciphertext to recover the original message. In order to decrypt messages, however, the receiver 110 must first obtain the private key dID from the PKG 120. After the PKG authenticates the identity of the receiver, it provides the receiver with the private key corresponding to the receiver's ID. (Note that, in this embodiment, the PKG can compute any private key in the system, and can thus decrypt any message to any user in the system.)
  • Chosen ciphertext security. Chosen ciphertext security (IND-CCA) is the standard acceptable notion of security for a public key encryption scheme. An embodiment of an identity-based encryption system and method may be implemented to satisfy this strong notion of security. Additionally, the selected level of chosen ciphertext security may be strengthened a bit. The reason is that when an adversary attacks a public key ID in an identity-based system, the adversary might already possess the private keys of users ID1, . . . , IDn of her choice. In an embodiment of the invention, the system remains secure under such an attack. That is, the system remains secure even when the adversary can obtain the private key associated with any identity IDi of her choice (other than the public key ID being attacked). We refer to such queries as private key extraction queries. The system of this embodiment also remains secure even though the adversary is challenged on a public key ID of her choice (as opposed to a random public key).
  • We say that an embodiment of an identity-based encryption system or method
    Figure US20090034714A9-20090205-P00908
    is semantically secure against an adaptive chosen ciphertext attack (IND-ID-CCA) if no polynomially bounded adversary A has a non-negligible advantage against the Challenger in the following IND-ID-CCA game:
      • Setup: The challenger takes a security parameter k and runs the Setup algorithm. It gives the adversary the resulting system parameters params. It keeps the master-key to itself.
      • Phase 1: The adversary issues queries q1, . . . , qm where query qi is one of:
        • Extraction query <IDi>. The challenger responds by running algorithm Extract to generate the private key di corresponding to the public key <IDi>. It sends di to the adversary.
        • Decryption query <IDi, Ci>. The challenger responds by running algorithm Extract to generate the private key di corresponding to IDi. It then runs algorithm Decrypt to decrypt the ciphertext Ci using the private key di. It sends the resulting plain-text to the adversary.
      •  These queries may be asked adaptively, that is, each query qi may depend on the replies to q1, . . . , qi−1.
      • Challenge: Once the adversary decides that Phase 1 is over it outputs two equal length plain-texts M0, M1ε
        Figure US20090034714A9-20090205-P00908
        and an identity ID on which it wishes to be challenged. The only constraint is that ID did not appear in any private key extraction query in Phase 1.
        • The challenger picks a random bit bε{0, 1} and sets C=Encrypt(params, ID, Mb). It sends C as the challenge to the adversary.
      • Phase 2: The adversary issues more queries qm+1, . . . , qn where query qi is one of:
        • Extraction query <IDi> where IDi≠ID. Challenger responds as in Phase 1.
        • Decryption query <IDi, Ci>≠<ID, C>. Challenger responds as in Phase 1.
        • These queries may be asked adaptively as in Phase 1.
      • Guess: Finally, the adversary outputs a guess b′ε{0, 1}. The adversary wins the game if b=b′.
      • We refer to such an adversary
        Figure US20090034714A9-20090205-P00903
        as an IND-ID-CCA adversary. We define adversary
        Figure US20090034714A9-20090205-P00903
        's advantage in attacking the scheme
        Figure US20090034714A9-20090205-P00908
        as the following function of the security parameter k (k is given as input to the challenger): Adv ɛ , 𝒜 ( k ) = Pr [ b = b ] - 1 2 .
      • The probability is over the random bits used by the challenger and the adversary.
        Using the IND-ID-CCA game we can define chosen ciphertext security for IBE schemes. As usual, we say that a function g:
        Figure US20090034714A9-20090205-P00005
        Figure US20090034714A9-20090205-P00005
        is negligible if g(k) is smaller than 1/ƒ(k) for any polynomial ƒ.
        Definition 1 We say that an IBE system
        Figure US20090034714A9-20090205-P00908
        is semantically secure against an adaptive chosen ciphertext attack if for any polynomial time IND-ID-CCA adversary
        Figure US20090034714A9-20090205-P00903
        the function Adv,(k) is negligible. As shorthand, we say that
        Figure US20090034714A9-20090205-P00908
        is IND-ID-CCA secure.
  • Note that the standard definition of chosen ciphertext security (IND-CCA) is the same as above except that there are no private key extraction queries and the adversary is challenged on a random public key (rather than a public key of her choice). Private key extraction queries are related to the definition of chosen ciphertext security in the multiuser settings. After all, our definition involves multiple public keys belonging to multiple users. A multiuser IND-CCA may be reducible to single user IND-CCA using a standard hybrid argument. This does not hold in the identity-based settings, IND-ID-CCA, since the adversary gets to choose which public keys to corrupt during the attack. To emphasize the importance of private key extraction queries we note that one implementation of the disclosed IBE system can be modified (by removing one of the hash functions) into a system which has chosen ciphertext security when private extraction queries are disallowed. However, the implementation is insecure when extraction queries are allowed.
  • Semantically secure identity based encryption. The proof of security for an implementation of our IBE system makes use of a weaker notion of security known as semantic security (also known as semantic security against a chosen plain-text attack). Semantic security is similar to chosen ciphertext security (IND-ID-CCA) except that the adversary is more limited; it cannot issue decryption queries while attacking the challenge public key. For a standard public key system (not an identity based system) semantic security is defined using the following game: (1) the adversary is given a random public key generated by the challenger, (2) the adversary outputs two equal length messages M0 and M1 and receives the encryption of Mb from the challenger where b is chosen at random in {0, 1}, (3) the adversary outputs b′ and wins the game if b=b′. The public key system is said to be semantically secure if no polynomial time adversary can win the game with a non-negligible advantage. As shorthand we say that a semantically secure public key system is IND-CPA secure. Semantic security captures our intuition that given a ciphertext the adversary learns nothing about the corresponding plain-text.
  • To define semantic security for identity based systems (denoted IND-ID-CPA) we strengthen the standard definition by allowing the adversary to issue chosen private key extraction queries. Similarly, the adversary is challenged on a public key ID of her choice. We define semantic security for identity based encryption schemes using an IND-ID-CPA game. The game is identical to the IND-ID-CCA game defined above except that the adversary cannot make any decryption queries. The adversary can only make private key extraction queries. We say that an identity-based encryption scheme
    Figure US20090034714A9-20090205-P00908
    is semantically secure (IND-ID-CPA) if no polynomially bounded adversary
    Figure US20090034714A9-20090205-P00903
    has a non-negligible advantage against the Challenger in the following IND-ID-CPA game:
      • Setup: The challenger takes a security parameter k and runs the Setup algorithm. It gives the adversary the resulting system parameters params. It keeps the master-key to itself.
      • Phase 1: The adversary issues private key extraction queries ID1, . . . , IDm. The challenger responds by running algorithm Extract to generate the private key di corresponding to the public key IDi. It sends di to the adversary. These queries may be asked adaptively.
      • Challenge: Once the adversary decides that Phase 1 is over it outputs two equal length plain-texts M0, M1ε
        Figure US20090034714A9-20090205-P00901
        and a public key ID on which it wishes to be challenged. The only constraint is that ID did not appear in any private key extraction query in Phase 1. The challenger picks a random bit bε{0, 1} and sets C=Encrypt(params, ID, Mb). It sends C as the challenge to the adversary.
      • Phase 2: The adversary issues more extraction queries IDm+1, . . . , IDn. The only constraint is that IDi≠ID. The challenger responds as in Phase 1.
      • Guess: Finally, the adversary outputs a guess b′ε{0, 1}. The adversary wins the game if b=b′.
      • We refer to such an adversary
        Figure US20090034714A9-20090205-P00903
        as an IND-ID-CPA adversary. As we did above, the advantage of an IND-ID-CPA adversary
        Figure US20090034714A9-20090205-P00903
        against the scheme
        Figure US20090034714A9-20090205-P00908
        is the following function of the security parameter k: Adv ɛ , 𝒜 ( k ) = Pr [ b = b ] - 1 2 .
      • The probability is over the random bits used by the challenger and the adversary.
        Definition 2 We say that the IBE system
        Figure US20090034714A9-20090205-P00908
        is semantically secure if for any polynomial time IND-ID-CPA adversary
        Figure US20090034714A9-20090205-P00903
        the function Adv,(k) is negligible. As shorthand, we say that
        Figure US20090034714A9-20090205-P00908
        is IND-ID-CPA secure.
        One way identity-based encryption. One can define an even weaker notion of security called one-way encryption (OWE). Roughly speaking, a public key encryption scheme is a one-way encryption if given the encryption of a random plain-text the adversary cannot produce the plain-text in its entirety. One-way encryption is a weak notion of security since there is nothing preventing the adversary from, say, learning half the bits of the plaintext. Hence, one-way encryption schemes do not generally provide secure encryption. In the random oracle model one-way encryption schemes can be used for encrypting session-keys (the session-key is taken to be the hash of the plain-text). We note that one can extend the notion of one-way encryption to identity based systems by adding private key extraction queries to the definition. We do not give the full definition here since we use semantic security as the weakest notion of security.
        Bilinear Maps and the Bilinear Diffie-Hellman Assumption
  • One embodiment of the invention is directed to an IBE system that makes use of a map ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 between groups
    Figure US20090034714A9-20090205-P00001
    1 and
    Figure US20090034714A9-20090205-P00001
    2 of order q for some large prime q. A map ê may be called an admissible map if it satisfies the following properties:
    • 1. Bilinear: The map ê:
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1
      Figure US20090034714A9-20090205-P00001
      2 satisfies ê(aP, bQ)=ê(P, Q)ab for all (P, Q)ε
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1 and all a, bε
      Figure US20090034714A9-20090205-P00002
      .
    • 2. Non-degenerate: The map does not send all pairs in
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1 to the identity in
      Figure US20090034714A9-20090205-P00001
      2. Observe that since
      Figure US20090034714A9-20090205-P00001
      1,
      Figure US20090034714A9-20090205-P00001
      1,
      Figure US20090034714A9-20090205-P00001
      2 are groups of prime order this implies that if
      Figure US20090034714A9-20090205-P00001
      1=
      Figure US20090034714A9-20090205-P00001
      1 and P is a generator of
      Figure US20090034714A9-20090205-P00001
      1=
      Figure US20090034714A9-20090205-P00001
      1 then ê(P, P) is a generator of
      Figure US20090034714A9-20090205-P00001
      2.
    • 3. Computable: There is an efficient algorithm to compute ê(P, Q) for any (P, Q)ε
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1.
      Although many of the embodiments are described with reference to a map ê:
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1
      Figure US20090034714A9-20090205-P00001
      2, this is only a specific case of bilinear maps used in embodiments of the invention. More generally, maps ê:
      Figure US20090034714A9-20090205-P00001
      0×
      Figure US20090034714A9-20090205-P00001
      1
      Figure US20090034714A9-20090205-P00001
      2 may be used, where
      Figure US20090034714A9-20090205-P00001
      0 and
      Figure US20090034714A9-20090205-P00001
      1 may be distinct. For simplicity of description, however, the description of many of the embodiments focuses primarily on the case where
      Figure US20090034714A9-20090205-P00001
      1 and
      Figure US20090034714A9-20090205-P00001
      1 are the same, and both groups are then denoted
      Figure US20090034714A9-20090205-P00001
      1. Below we present a detailed exemplary embodiment using groups
      Figure US20090034714A9-20090205-P00001
      1,
      Figure US20090034714A9-20090205-P00001
      2 and an admissible map between them. In this exemplary embodiment, the group
      Figure US20090034714A9-20090205-P00001
      1 is a subgroup of the additive group of points of an elliptic curve E/
      Figure US20090034714A9-20090205-P00003
      p, and the group
      Figure US20090034714A9-20090205-P00001
      2 is a subgroup of the multiplicative group of a finite field
      Figure US20090034714A9-20090205-P00003
      *p 2 . As we will see below in the detailed example of an IBE system, the Weil pairing (which is not itself an admissible map) can be used to construct an admissible map between these two groups.
  • The existence of the admissible map ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 as above has two direct implications to these groups.
    • The MOV reduction: The discrete log problem in
      Figure US20090034714A9-20090205-P00001
      1 is no harder than the discrete log problem in
      Figure US20090034714A9-20090205-P00001
      2. To see this, let P, Qε
      Figure US20090034714A9-20090205-P00001
      1 be an instance of the discrete log problem in
      Figure US20090034714A9-20090205-P00001
      1 where both P, Q have order q. We wish to find an aε
      Figure US20090034714A9-20090205-P00002
      q such that Q=aP. Let g=ê(P, P) and h=ê(Q, P). Then, by bilinearity of ê we know that h=ga. By non-degeneracy of ê both g, h have order q in
      Figure US20090034714A9-20090205-P00001
      2. Hence, we reduced the discrete log problem in
      Figure US20090034714A9-20090205-P00001
      1 to a discrete log problem in
      Figure US20090034714A9-20090205-P00001
      2. It follows that for discrete log to be hard in
      Figure US20090034714A9-20090205-P00001
      1 we must choose our security parameter so that discrete log is hard in
      Figure US20090034714A9-20090205-P00001
      2.
    • Decision Diffie-Hellman is Easy: The Decision Diffie-Hellman problem (DDH) in
      Figure US20090034714A9-20090205-P00001
      1 is the problem of distinguishing between the distributions <P, aP, bP, abP> and <P, aP, bP, cP> where a, b, c are random in
      Figure US20090034714A9-20090205-P00002
      q and P is random in
      Figure US20090034714A9-20090205-P00001
      1. To see that DDH in
      Figure US20090034714A9-20090205-P00001
      1 is easy, observe that given P, aP, bP, cPε
      Figure US20090034714A9-20090205-P00001
      *1 we have
      c=ab mod q ê(P, cP)=ê(aP, bP).
    •  The Computational Diffie-Hellman problem (CDH) in
      Figure US20090034714A9-20090205-P00001
      1 can still be hard (CDH in
      Figure US20090034714A9-20090205-P00001
      1 is to find abP given random <P, aP, bP>). Exemplary embodiments may use mappings ê:
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1
      Figure US20090034714A9-20090205-P00001
      2 where CDH in
      Figure US20090034714A9-20090205-P00001
      1 is believed to be hard even though DDH in
      Figure US20090034714A9-20090205-P00001
      1 is easy.
      The Bilinear Diffie-Hellman Assumption (BDH)
  • Since the Decision Diffie-Hellman problem (DDH) in
    Figure US20090034714A9-20090205-P00001
    1 is easy, embodiments of the invention do not use DDH to build cryptosystems in the group
    Figure US20090034714A9-20090205-P00001
    1. Instead, the security in embodiments of our IBE system is based on a novel variant of the Computational Diffie-Hellman assumption called the Bilinear Diffie-Hellman Assumption (BDH).
  • Bilinear Diffie-Hellman Problem. Let
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 be two groups of prime order q. Let ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 be an admissible map and let P be a generator of
    Figure US20090034714A9-20090205-P00001
    1. The BDH problem in (
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2, ê> is as follows: Given <P, aP, bP, cP> for some a, b, cε
    Figure US20090034714A9-20090205-P00002
    *q compute W=ê(P, p)abcε
    Figure US20090034714A9-20090205-P00001
    2. An algorithm A has advantage ε in solving BDH in <
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2, ê if
    Pr[
    Figure US20090034714A9-20090205-P00903
    (P,aP,bP,cP)=ê(P,P)abc]≧ε
    where the probability is over the random choice of a, b, c in
    Figure US20090034714A9-20090205-P00002
    *q, the random choice of Pε
    Figure US20090034714A9-20090205-P00001
    *1, and the random bits of
    Figure US20090034714A9-20090205-P00903
    .
    BDH Parameter Generator. We say that a randomized algorithm
    Figure US20090034714A9-20090205-P00904
    is a BDH parameter generator if (1)
    Figure US20090034714A9-20090205-P00904
    takes a security parameter kε
    Figure US20090034714A9-20090205-P00002
    +, (2)
    Figure US20090034714A9-20090205-P00904
    runs in polynomial time in k, and (3)
    Figure US20090034714A9-20090205-P00904
    outputs a prime number q, the description of two groups
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 of order q, and the description of an admissible map ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2. We denote the output of G by
    Figure US20090034714A9-20090205-P00904
    (1k)=<q,
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2, ê>. The security parameter k is used to determine the size of q; for example, one could take q to be a random k-bit prime. For i=1, 2 we assume that the description of the group
    Figure US20090034714A9-20090205-P00001
    i contains polynomial time (in k) algorithms for computing the group action in
    Figure US20090034714A9-20090205-P00001
    i and contains a generator of
    Figure US20090034714A9-20090205-P00001
    i. The generator of
    Figure US20090034714A9-20090205-P00001
    i enables us to generate uniformly random elements in
    Figure US20090034714A9-20090205-P00001
    i. Similarly, we assume that the description of ê contains a polynomial time algorithm for computing ê. We give an example of a BDH parameter generator below in the detailed example of an IBE system using the Weil pairing.
    Bilinear Diffie-Hellman Assumption. Let
    Figure US20090034714A9-20090205-P00904
    be a BDH parameter generator. We say that an algorithm
    Figure US20090034714A9-20090205-P00903
    has advantage ε(k) in solving the BDH problem for
    Figure US20090034714A9-20090205-P00904
    if for sufficiently large k: Adv 𝒢 , 𝒜 ( k ) = Pr [ 𝒜 ( q , 𝔾 1 , 𝔾 2 , e ^ , P , aP , bP , cP ) = e ^ ( P , P ) abc | q , 𝔾 1 , 𝔾 2 , e ^ 𝒢 ( 1 k ) , P 𝔾 1 * , a , b , c q * ] > ε ( k )
    We say that
    Figure US20090034714A9-20090205-P00904
    satisfies the BDH assumption if for any randomized polynomial time (in k) algorithm
    Figure US20090034714A9-20090205-P00903
    and for any polynomial fε
    Figure US20090034714A9-20090205-P00002
    [x] algorithm
    Figure US20090034714A9-20090205-P00903
    solves the BDH problem with advantage at most 1/ƒ(k). When
    Figure US20090034714A9-20090205-P00904
    satisfies the BDH assumption we say that BDH is hard in groups generated by
    Figure US20090034714A9-20090205-P00904
    .
  • In the description below of a detailed example of an IBE system we give some examples of BDH parameter generators that are believed to satisfy the BDH assumption.
  • Hardness of BDH. It is interesting to study the relationship of the BDH problem to other hard problems used in cryptography. Currently, all we can say is that the BDH problem in <
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2, ê> is no harder than the CDH problem in
    Figure US20090034714A9-20090205-P00001
    1 or
    Figure US20090034714A9-20090205-P00001
    2. In other words, an algorithm for CDH in
    Figure US20090034714A9-20090205-P00001
    1 or
    Figure US20090034714A9-20090205-P00001
    2 is sufficient for solving BDH in (
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2, ê). The converse is currently an open problem: is an algorithm for BDH sufficient for solving CDH in
    Figure US20090034714A9-20090205-P00001
    1 or in
    Figure US20090034714A9-20090205-P00001
    2?
  • We note that in a detailed example of an IBE system below, the isomorphisms from
    Figure US20090034714A9-20090205-P00001
    1 to
    Figure US20090034714A9-20090205-P00001
    2 induced by the admissible map are believed to be one-way functions. More specifically, for a point Qε
    Figure US20090034714A9-20090205-P00001
    *1 define the isomorphism ƒQ: 1
    Figure US20090034714A9-20090205-P00001
    2 by ƒQ(P)=ê(P, Q). If any one of these isomorphisms turns out to be invertible, then BDH is easy in (
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2, ê>. Fortunately, an efficient algorithm for inverting ƒQ would imply an efficient algorithm for deciding DDH in the group
    Figure US20090034714A9-20090205-P00001
    2. In the exemplary embodiments DDH is believed to be hard in the group
    Figure US20090034714A9-20090205-P00001
    2. Hence, the isomorphisms ƒQ:
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 induced by the admissible map are believed to be one-way functions.
  • Exemplary Identity-Based Encryption Scheme
  • We describe the following exemplary embodiments in stages. First we describe a basic identity-based encryption system and method which is not secure against an adaptive chosen ciphertext attack. Another embodiment described below extends the basic scheme to get security against an adaptive chosen ciphertext attack (IND-ID-CCA) in the random oracle model. We later relax some of the requirements on the hash functions to provide alternative embodiments. These embodiments are described with reference to a generic BDH parameter generator
    Figure US20090034714A9-20090205-P00904
    satisfying the BDH assumption. Later we describe a detailed example of an IBE system using the Weil pairing.
  • BasicIdent
  • The following describes a basic embodiment, called BasicIdent. We present the embodiment by describing the four algorithms: Setup, Extract, Encrypt, Decrypt. We let k be the security parameter given to the setup algorithm. We let
    Figure US20090034714A9-20090205-P00904
    be some BDH parameter generator.
    • Setup: Given a security parameter kε
      Figure US20090034714A9-20090205-P00002
      +, the algorithm in the basic embodiment works as follows:
      • Step 1: Run
        Figure US20090034714A9-20090205-P00904
        on input k to generate a prime q, two groups
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2 of order q, and an admissible map ê:
        Figure US20090034714A9-20090205-P00001
        1×
        Figure US20090034714A9-20090205-P00001
        1
        Figure US20090034714A9-20090205-P00001
        2. Choose an arbitrary generator Pε
        Figure US20090034714A9-20090205-P00001
        1.
      • Step 2: Pick a random sε
        Figure US20090034714A9-20090205-P00002
        *q and set Ppub=sP.
      • Step 3: Choose a cryptographic hash function H1: {0, 1}*→
        Figure US20090034714A9-20090205-P00001
        *1. Choose a cryptographic hash function H2:
        Figure US20090034714A9-20090205-P00001
        2→{0, 1}n for some n. The security analysis will view H1, H2 as random oracles.
      • The message space is
        Figure US20090034714A9-20090205-P00901
        ={0, 1}n. The ciphertext space is
        Figure US20090034714A9-20090205-P00902
        =
        Figure US20090034714A9-20090205-P00001
        *1×{0, 1}n. The system parameters are params=<q,
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2, ê, n, P, Ppub, H1, H2>. The master-key is sε
        Figure US20090034714A9-20090205-P00002
        *q. Embodiments of the IBE system may be used to encrypt a symmetric key, in which case one may take n to be, for example, 128 or 256. For k one may use, for example, 512 or 1024 or 2048.
    • Extract: For a given string IDε{0, 1}* the algorithm in the basic embodiment does: (1) computes QID=H1(ID)ε
      Figure US20090034714A9-20090205-P00001
      *1, and (2) sets the private key dID to be dID=sQID where s is the master key.
      • Extract may be performed by a PKG in various embodiments as illustrated in FIG. 2. The PKG obtains the master key in block 200, obtains the public identifier ID in block 210, computes the public key from the ID in block 220, then computes the private key from the master key and the public key in block 230. In block 240 the private key is then sent to an entity associated with the public identifier ID, normally after the entity's identity has been authenticated.
    • Encrypt: To encrypt Mε
      Figure US20090034714A9-20090205-P00901
      under the public key ID do the following: (1) compute QID=H1(ID)ε
      Figure US20090034714A9-20090205-P00001
      *1, (2) choose a random rε
      Figure US20090034714A9-20090205-P00002
      *q, and (3) set the ciphertext to be
      C=<rP,M⊕H 2(g ID r)> where g ID (Q ID ,P pub
      Figure US20090034714A9-20090205-P00001
      *2.
      • In the basic embodiment, the sender of a message may perform Encrypt as illustrated in FIG. 3. In block 300 the system parameters are obtained (from an external resource such as a PKG, or from a local storage medium if they were obtained previously). A receiver's ID is determined in block 310, and the corresponding public key is computed from the ID in block 320. Then the secret message key is computed in block 330, and the message key is used to encrypt the message in block 340.
    • Decrypt: Let C=<U, V>εC be a ciphertext encrypted using the public key ID. To decrypt C using the private key dIDε
      Figure US20090034714A9-20090205-P00001
      *1 compute:
      V⊕H 2(ê(d ID ,U))=M.
      • In the basic embodiment, the receiver may perform Decrypt as illustrated in FIG. 4. In block 400, the system parameters are obtained (from an external resource such as a PKG, or from a local storage medium if they were obtained previously). The ciphertext V and an element rP are obtained from the sender in block 410. The element rP may be considered a portion of the total ciphertext obtained from the sender. In block 420 the receiver obtains the private key dID corresponding to the public identifier ID used to encrypt the message. The private key is normally obtained from an external resource such as a PKG, or from a local storage medium if it was obtained previously. The secret message key is then computed in block 430, and used to decrypt the message in block 440.
        This completes the description of BasicIdent for the basic embodiment. We first verify consistency. When everything is computed as above we have:
        1. During encryption M is bitwise exclusive-ored with the hash of: gID r.
        2. During decryption V is bitwise exclusive-ored with the hash of: ê(dID, U).
        These masks used during encryption and decryption are the same since:
        ê(d ID ,U)=ê(sQ ID ,rP)=ê(Q ID ,p)st (Q ID ,P pub)r =g ID r
        Thus, applying decryption after encryption produces the original message M as required. Performance considerations of BasicIdent are discussed later.
    • Security. Next, we study the security of this basic embodiment.
  • The security of the exemplary system is based on the assumption that a variant of the Computational Diffie-Hellman problem in
    Figure US20090034714A9-20090205-P00001
    1 is hard. The technical security details of the encryption scheme are discussed by the inventors in D. Boneh, M. Franklin, “Identity based encryption from the Weil pairing”, extended abstract in Advances in Cryptology—Crypto 2001, Lecture Notes in Computer Science, Vol. 2139, Springer-Verlag, pp. 231-229, 2001, which is incorporated herein by reference.
  • In an exemplary embodiment, the performance of the system is comparable to the performance of ElGamal encryption in
    Figure US20090034714A9-20090205-P00003
    *p. The security of the exemplary system is based on a variant of the computational Diffie-Hellman assumption. Based on this assumption we show that the exemplary system has chosen ciphertext security in the random oracle model. In accordance with a distributed PKG embodiment, threshold cryptography techniques allow the PKG to be distributed so that the master-key is never available in a single location. Unlike common threshold systems, we show that robustness for the distributed PKG embodiment is free.
  • To argue about the security of the exemplary system, we define chosen ciphertext security for identity-based encryption. Our model gives the adversary more power than the standard model for chosen ciphertext security. First, we allow the attacker to attack an arbitrary public key ID of her choice. Second, while mounting a chosen ciphertext attack on ID we allow the attacker to obtain from the PKG the private key for any public key of her choice, other than the private key for ID. This models an attacker who obtains a number of private keys corresponding to some identities of her choice and then tries to attack some other public key ID of her choice. Even with the help of such queries, it is desirable that the attacker still have negligible advantage in defeating the semantic security of the system.
  • The following theorem shows that BasicIdent is a semantically secure identity based encryption scheme (IND-ID-CPA) assuming BDH is hard in groups generated by
    Figure US20090034714A9-20090205-P00904
    .
    Theorem 1 Suppose the hash functions H1, H2 are random oracles. Then BasicIdent is a semantically secure identity based encryption scheme (IND-ID-CPA) assuming BDH is hard in groups generated by
    Figure US20090034714A9-20090205-P00904
    . Concretely, suppose there is an IND-ID-CPA adversary
    Figure US20090034714A9-20090205-P00903
    that has advantage ε(k) against the scheme BasicIdent. Suppose
    Figure US20090034714A9-20090205-P00903
    makes at most qE>0 private key extraction queries and qH 2 >0 hash queries to H2. Then there is an algorithm
    Figure US20090034714A9-20090205-P00903
    that solves BDH in groups generated by
    Figure US20090034714A9-20090205-P00904
    with advantage at least: Adv 𝒢 , ( k ) 2 ε ( k ) e ( 1 + q E ) · q H 2
    Here e≈2.71 is the base of the natural logarithm. The running time of
    Figure US20090034714A9-20090205-P00906
    is O(time(
    Figure US20090034714A9-20090205-P00903
    )).
  • To prove the theorem we first define a related Public Key Encryption scheme (not an identity based scheme), called BasicPub. BasicPub is described by three algorithms: keygen, encrypt, decrypt.
    • keygen: Given a security parameter kε
      Figure US20090034714A9-20090205-P00002
      +, the algorithm works as follows:
      • Step 1: Run
        Figure US20090034714A9-20090205-P00904
        on input k to generate two prime order groups
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2 and an admissible map ê:
        Figure US20090034714A9-20090205-P00001
        1×
        Figure US20090034714A9-20090205-P00001
        1
        Figure US20090034714A9-20090205-P00001
        2. Let q be the order of
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2. Choose an arbitrary generator Pε
        Figure US20090034714A9-20090205-P00001
        1.
      • Step 2: Pick a random sε
        Figure US20090034714A9-20090205-P00002
        *q and set Ppub=sP. Pick a random QIDε
        Figure US20090034714A9-20090205-P00001
        *1.
      • Step 3: Choose a cryptographic hash function H2:
        Figure US20090034714A9-20090205-P00001
        2{0, 1}n for some n.
      • Step 4: The public key is <q,
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2, ê, n, P, Ppub, QID, H2>. The private key is dID=sQIDε
        Figure US20090034714A9-20090205-P00001
        *1.
    • encrypt: To encrypt Mε{0, 1}n choose a random rε
      Figure US20090034714A9-20090205-P00002
      *q and set the ciphertext to be:
      C=<rP,M⊕H 2(g r)> where g=ê(Q ID ,P pub
      Figure US20090034714A9-20090205-P00001
      *2
    • decrypt: Let C=<U, V> be a ciphertext created using the public key <q,
      Figure US20090034714A9-20090205-P00001
      1,
      Figure US20090034714A9-20090205-P00001
      2, ê, n, P, Ppub, QID, H2>. To decrypt C using the private key dIDε
      Figure US20090034714A9-20090205-P00001
      *1 compute:
      V⊕H 2(ê(d ID ,U))=M
      This completes the description of BasicPub. We now prove Theorem 1 in two steps. We first show that an IND-ID-CPA attack on BasicIdent can be converted to a IND-CPA attack on BasicPub. This step shows that private key extraction queries do not help the adversary. We then show that BasicPub is IND-CPA secure if the BDH assumption holds. The proofs are omitted.
      Lemma 2 Let H1 be a random oracle from {0, 1}* to
      Figure US20090034714A9-20090205-P00001
      *1. Let
      Figure US20090034714A9-20090205-P00903
      be an IND-ID-CPA adversary that has advantage ε(k) against BasicIdent. Suppose
      Figure US20090034714A9-20090205-P00903
      makes at most qE>0 private key extraction queries. Then there is a IND-CPA adversary
      Figure US20090034714A9-20090205-P00906
      that has advantage at least ε(k)/e(1+qE) against BasicPub. Its running time is O(time(
      Figure US20090034714A9-20090205-P00903
      )).
      Lemma 3 Let H2 be a random oracle from
      Figure US20090034714A9-20090205-P00001
      2 to {0, 1}n. Let
      Figure US20090034714A9-20090205-P00903
      be an IND-CPA adversary that has advantage ε(k) against BasicPub. Suppose
      Figure US20090034714A9-20090205-P00903
      makes a total of qH 2 >0 queries to H2. Then there is an algorithm
      Figure US20090034714A9-20090205-P00906
      that solves the BDH problem for
      Figure US20090034714A9-20090205-P00904
      with advantage at least 2ε(k)/qH 2 and a running time O(time(
      Figure US20090034714A9-20090205-P00903
      )).
      Proof of Theorem 1. The theorem follows directly from Lemma 2 and Lemma 3. Composing both reductions shows that an IND-ID-CPA adversary on BasicIdent with advantage ε(k) gives a BDH algorithm for G with advantage at least 2ε(k)/e(1+qE)qH 2 , as required.
      Identity-Based Encryption with Chosen Ciphertext Security
  • According to one embodiment of the invention, a technique of Fujisaki and Okamoto (described in E. Fujisaki and T. Okamoto, “Secure integration of asymmetric and symmetric encryption schemes”, in Advances in Cryptology—Crypto '99, Lecture Notes in Computer Science, Vol. 1666, Springer-Verlag, pp. 537-554, 1999, which is incorporated herein by reference) may be appropriately adapted to convert the BasicIdent embodiment of the previous section into a chosen ciphertext secure embodiment of an IBE system (in the sense defined earlier) in the random oracle model. Let
    Figure US20090034714A9-20090205-P00908
    be a probabilistic public key encryption scheme. We denote by
    Figure US20090034714A9-20090205-P00908
    pk(M; r) the encryption of M using the random bits r under the public key pk. Fujisaki-Okamoto define the hybrid scheme
    Figure US20090034714A9-20090205-P00908
    hy as:
    Figure US20090034714A9-20090205-P00908
    pk hy(M)=<
    Figure US20090034714A9-20090205-P00908
    pk(σ;H 3(σ,M)),H 4(σ)⊕M>
    Here σ is generated at random and H3, H4 are cryptographic hash functions. Fujisaki-Okamoto show that if
    Figure US20090034714A9-20090205-P00908
    is a one-way encryption scheme then
    Figure US20090034714A9-20090205-P00908
    hy is a chosen ciphertext secure system (IND-CCA) in the random oracle model (assuming
    Figure US20090034714A9-20090205-P00908
    pk satisfies some natural constraints). We note that semantic security implies one-way encryption and hence the Fujisaki-Okamoto result also applies if
    Figure US20090034714A9-20090205-P00908
    is semantically secure (IND-CPA).
  • We apply the Fujisaki-Okamoto transformation to BasicIdent and show that the resulting embodiment of an IBE system is IND-ID-CCA secure. We obtain the following IBE embodiment which we call FullIdent. Recall that n is the length of the message to be encrypted.
    • Setup: As in the BasicIdent scheme. In addition, we pick a hash function H3: {0, 1}n×{0, 1}n
      Figure US20090034714A9-20090205-P00002
      *q, and a hash function H4: {0, 1}n→{0, 1}n.
    • Extract: As in the BasicIdent scheme.
    • Encrypt: To encrypt Mε{, 1}n under the public key ID do the following: (1) compute QID=H1(ID)ε
      Figure US20090034714A9-20090205-P00001
      *1, (2) choose a random σε{0, 1}n, (3) set r=H3(σ, M), and (4) set the ciphertext to be
      C=<rP,σ⊕H 2(g ID r), M⊕(H4(σ)> where g ID (Q ID ,P pub
      Figure US20090034714A9-20090205-P00001
      2
    • Decrypt: Let C=<U, V, W> be a ciphertext encrypted using the public key ID. If U≠
      Figure US20090034714A9-20090205-P00001
      *1 reject the ciphertext. To decrypt C using the private key dIDε
      Figure US20090034714A9-20090205-P00001
      *1 do:
      • 1. Compute V⊕H2(ê(dID, U))=σ.
      • 2. Compute W⊕H4(σ)=M.
      • 3. Set r=H3(σ, M). Test that U=rP. If not, reject the ciphertext.
      • 4. Output M as the decryption of C.
        This completes the description of FullIdent. Its implementation follows the same basic pattern as BasicIdent shown in FIGS. 2, 3, 4. Note that M is encrypted as W=M⊕H4(σ). This can be replaced by W=EH 4 (σ)(M) where E is a semantically secure symmetric encryption scheme.
    • Security. The following theorem shows that FullIdent is a chosen ciphertext secure IBE (i.e. IND-ID-CCA), assuming BDH is hard in groups generated by
      Figure US20090034714A9-20090205-P00904
      .
      Theorem 4 Let the hash functions H1, H2, H3, H4 be random oracles. Then FullIdent is a chosen ciphertext secure IBE (IND-ID-CCA) assuming BDH is hard in groups generated by
      Figure US20090034714A9-20090205-P00904
      .
      Concretely, suppose there is an IND-ID-CCA adversary
      Figure US20090034714A9-20090205-P00903
      that has advantage ε(k) against the scheme FullIdent and
      Figure US20090034714A9-20090205-P00903
      runs in time at most t(k). Suppose
      Figure US20090034714A9-20090205-P00903
      makes at most qE extraction queries, at most qD decryption queries, and at most qH 2 , qH 3 , qH 4 queries to the hash functions H2, H3, H4 respectively. Then there is a BDH algorithm
      Figure US20090034714A9-20090205-P00906
      for
      Figure US20090034714A9-20090205-P00904
      with running time t1(k) where: Adv 𝒢 , ( k ) 2 FO adv ( ε ( k ) e ( 1 + q E + q D ) , q H 4 , q H 3 , q D ) / q H 2 t 1 ( k ) FO time ( t ( k ) , q H 4 , q H 3 )
      where the functions FOtime and FOadv are defined in Theorem 5.
  • The proof of Theorem 4 is based on the following result of Fujisaki and Okamoto. Let BasicPubhy be the result of applying the Fujisaki-Okamoto transformation to BasicPub.
    Theorem 5 (Fujisaki-Okamoto) Suppose
    Figure US20090034714A9-20090205-P00903
    is an IND-CCA adversary that achieves advantage ε(k) when attacking BasicPubhy. Suppose
    Figure US20090034714A9-20090205-P00903
    has running time t(k), makes at most qD decryption queries, and makes at most qH 3 , qH 4 queries to the hash functions H3, H4 respectively. Then there is an IND-CPA adversary
    Figure US20090034714A9-20090205-P00906
    against BasicPub with running time t1(k) and advantage ε1(k) where ε 1 ( k ) FO adv ( ε ( k ) , q H 4 , q H 3 , q D ) = 1 2 ( q H 4 + q H 3 ) [ ( ε ( k ) + 1 ) ( 1 - 2 / q ) q D - 1 ] t 1 ( k ) FO time ( t ( k ) , q H 4 , q H 3 ) = t ( k ) + O ( ( q H 4 + q H 3 ) · n ) ,
    Here q is the size of the groups
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 and n is the length of σ.
  • In fact, Fujisaki-Okamoto prove a stronger result: Under the hypothesis of Theorem 5, BasicPubhy would not even be a one-way encryption scheme. For our purposes the result in Theorem 5 is sufficient. To prove Theorem 4 we also need the following lemma to translate between an IND-ID-CCA chosen ciphertext attack on FullIdent and an IND-CCA chosen ciphertext attack on BasicPubhy.
    Lemma 6 Let A be an IND-ID-CCA adversary that has advantage ε(k) against FullIdent. Suppose
    Figure US20090034714A9-20090205-P00903
    makes at most qE>0 private key extraction queries and at most qD decryption queries. Then there is an IND-CCA adversary
    Figure US20090034714A9-20090205-P00906
    that has advantage at least ε ( k ) e ( 1 + q E + q D )
    against BasicPubhy. Its running time is O(time(
    Figure US20090034714A9-20090205-P00903
    )).
    Proof of Theorem 4. By Lemma 6 an IND-ID-CCA adversary on FullIdent implies an IND-CCA adversary on BasicPubhy. By Theorem 5 an IND-CCA adversary on BasicPubhy implies an IND-CPA adversary on BasicPub. By Lemma 3 an IND-CPA adversary on BasicPub implies an algorithm for BDH. Composing all these reductions gives the required bounds. □
  • Relaxing the Hashing Requirements
  • Recall that an IBE system of Section uses a hash function H1: {0, 1}*→
    Figure US20090034714A9-20090205-P00001
    *1. The detailed example of an IBE system presented in the next section uses
    Figure US20090034714A9-20090205-P00001
    1 as a subgroup of the group of points on an elliptic curve. In practice, it sometimes can be difficult to build hash functions that hash directly onto such groups. In an exemplary embodiment, we therefore show how to relax the requirement of hashing directly onto
    Figure US20090034714A9-20090205-P00001
    *1. Rather than hash onto
    Figure US20090034714A9-20090205-P00001
    *1 we hash onto some set A{0, 1}* and then use a deterministic encoding function to map A onto
    Figure US20090034714A9-20090205-P00001
    *1.
  • Admissible encodings: Let
    Figure US20090034714A9-20090205-P00001
    1 be a group and let Aε{0, 1}* be a finite set. We say that an encoding function L: A→
    Figure US20090034714A9-20090205-P00001
    *1 is admissible if it satisfies the following properties:
    • 1. Computable: There is an efficient deterministic algorithm to compute L(z) for any xεA.
    • 2. l-to-1: For any yε
      Figure US20090034714A9-20090205-P00001
      *1 the preimage of y under L has size exactly l. In other words, |L−1(y)|=l for all yε
      Figure US20090034714A9-20090205-P00001
      *1. Note that this implies that |A|=l·|
      Figure US20090034714A9-20090205-P00001
      *1|.
    • 3. Samplable: There is an efficient randomized algorithm
      Figure US20090034714A9-20090205-P00907
      s such that
      Figure US20090034714A9-20090205-P00907
      s(y) induces a uniform distribution on L−1(y) for any yε
      Figure US20090034714A9-20090205-P00001
      *1. In other words,
      Figure US20090034714A9-20090205-P00907
      s(y) is a uniform random element in L−1(y).
      We modify FullIdent to obtain an IND-ID-CCA secure embodiment of an IBE system where H1 is replaced by a hash function into some set A. Since the change is relatively minor we refer to this new scheme as FullIdent:
    • Setup: As in the FullIdent embodiment. The only difference is that H1 is replaced by a hash function H′1: {0, 1}*→A. The system parameters also include a description of an admissible encoding function L: A→
      Figure US20090034714A9-20090205-P00001
      *1.
    • Extract, Encrypt: As in the FullIdent embodiment. The only difference is that in Step 1 these algorithms compute QID=L(H′1(ID))ε
      Figure US20090034714A9-20090205-P00001
      *1.
    • Decrypt: As in the FullIdent embodiment.
      This completes the description of FullIdent′. The following theorem shows that FullIdent′ is a chosen ciphertext secure IBE (i.e. IND-ID-CCA), assuming FullIdent is.
      Theorem 7 Let
      Figure US20090034714A9-20090205-P00903
      be an IND-ID-CCA adversary on FullIdent′ that achieves advantage ε(k). Suppose
      Figure US20090034714A9-20090205-P00903
      makes at most qH 1 queries to the hash function H′1. Then there is an IND-ID-CCA adversary
      Figure US20090034714A9-20090205-P00906
      on FullIdent that achieves the same advantage ε(k) and time(
      Figure US20090034714A9-20090205-P00906
      )=time(
      Figure US20090034714A9-20090205-P00903
      )+qH 1 ·time(Ls)
      Proof Sketch Algorithm
      Figure US20090034714A9-20090205-P00906
      attacks FullIdent by running algorithm
      Figure US20090034714A9-20090205-P00903
      . It relays all decryption queries, extraction queries, and hash queries from
      Figure US20090034714A9-20090205-P00903
      directly to the challenger and relays the challenger's response back to
      Figure US20090034714A9-20090205-P00903
      . It only behaves differently when
      Figure US20090034714A9-20090205-P00903
      issues a hash query to H′1. Recall that
      Figure US20090034714A9-20090205-P00906
      only has access to a hash function H1: {0, 1}*→
      Figure US20090034714A9-20090205-P00001
      *1. To respond to H′1 queries algorithm
      Figure US20090034714A9-20090205-P00906
      maintains a list of tuples <IDj, yj> as explained below. We refer to this list as the (H′1)list. The list is initially empty. When
      Figure US20090034714A9-20090205-P00903
      queries the oracle H′1 at a point IDi algorithm
      Figure US20090034714A9-20090205-P00906
      responds as follows:
    • 1. If the query IDi already appears on the (H′1)list in a tuple <IDi, yi> then respond with H′1(IDi)=yiεA.
    • 2. Otherwise,
      Figure US20090034714A9-20090205-P00906
      issues a query for H1(IDi). Say, H1(IDi)=αε
      Figure US20090034714A9-20090205-P00001
      *1.
    • 3.
      Figure US20090034714A9-20090205-P00906
      runs the sampling algorithm
      Figure US20090034714A9-20090205-P00907
      s(α) to generate a random element yεL−1(α).
    • 4.
      Figure US20090034714A9-20090205-P00906
      adds the tuple <IDi, y> to the (H′1)list and responds to
      Figure US20090034714A9-20090205-P00903
      with H′1(IDi)=yεA. Note that y is uniformly distributed in A as required since α is uniformly distributed in
      Figure US20090034714A9-20090205-P00001
      *1 and L is an l-to-1 map.
      Algorithm
      Figure US20090034714A9-20090205-P00906
      's responses to all of
      Figure US20090034714A9-20090205-P00903
      's queries, including H′1 queries, are identical to
      Figure US20090034714A9-20090205-P00903
      's view in the real attack. Hence,
      Figure US20090034714A9-20090205-P00906
      will have the same advantage ε(k) in winning the game with the challenger.
      A Detailed Example of an IBE System Using the Weil Pairing
  • In this section we use FullIdent′ to describe a detailed example of an embodiment of an IBE system. This embodiment is based on the Weil pairing. Although in practice the Tate pairing has computational advantages and may be used instead of the Weil pairing in various embodiments, the implementation using the Weil pairing will be described first because it is simpler. Later, the Tate pairing will be discussed.
  • Properties of the Weil Pairing
  • Let p>3 be a prime satisfying p=2 mod 3 and let q be some prime factor of p+1. Let E be the elliptic curve defined by the equation y2=x3+1 over
    Figure US20090034714A9-20090205-P00003
    p. We state a few elementary facts about this curve E. From here on we let E(
    Figure US20090034714A9-20090205-P00003
    p r ) denote the group of points on E defined over
    Figure US20090034714A9-20090205-P00003
    p r .
    • Fact 1: Since x3+1 is a permutation on
      Figure US20090034714A9-20090205-P00003
      p it follows that the group E(
      Figure US20090034714A9-20090205-P00003
      p) contains p+1 points. We let O denote the point at infinity. Let PεE(
      Figure US20090034714A9-20090205-P00003
      p) be a point of order q and let
      Figure US20090034714A9-20090205-P00001
      1 be the subgroup of points generated by P.
    • Fact 2: For any y0ε
      Figure US20090034714A9-20090205-P00003
      p there is a unique point (x0, y0) on E(
      Figure US20090034714A9-20090205-P00003
      p), namely x0=(y0 2−1)1/3ε
      Figure US20090034714A9-20090205-P00003
      p. Hence, if (x, y) is a random non-zero point on E(
      Figure US20090034714A9-20090205-P00003
      p) then y is uniform in
      Figure US20090034714A9-20090205-P00003
      p. We use this property to build a simple admissible encoding function.
    • Fact 3: Let 1≠ζε
      Figure US20090034714A9-20090205-P00003
      p 2 be a solution of x3−1=0 mod p. Then the map φ(x, y)=(ζx, y) is an automorphism of the group of points on the curve E. Note that for any point Q=(x, y)εE(
      Figure US20090034714A9-20090205-P00003
      p) we have that φ(Q)εE(
      Figure US20090034714A9-20090205-P00003
      p 2 ), but φ(Q)εE(
      Figure US20090034714A9-20090205-P00003
      p). Hence, QεE(
      Figure US20090034714A9-20090205-P00003
      p) is linearly independent of φ(Q)εE
      Figure US20090034714A9-20090205-P00003
      p 2 ).
    • Fact 4: Since the points Pε
      Figure US20090034714A9-20090205-P00001
      1 and φ(P) are linearly independent they generate a group isomorphic to
      Figure US20090034714A9-20090205-P00002
      q×
      Figure US20090034714A9-20090205-P00002
      q. We denote this group of points by E[q].
      Let
      Figure US20090034714A9-20090205-P00001
      2 be the subgroup of
      Figure US20090034714A9-20090205-P00003
      *p 2 of order q. The Weil pairing on the curve E(
      Figure US20090034714A9-20090205-P00003
      p 2 ) is a mapping e: E[q]×E[q]→
      Figure US20090034714A9-20090205-P00001
      2. (This map is defined and discussed in the section below entitled Description of the Weil Pairing.) For any Q, RεE(
      Figure US20090034714A9-20090205-P00003
      p) the Weil pairing satisfies e(Q, R)=1. In other words, the Weil pairing is degenerate on E(
      Figure US20090034714A9-20090205-P00003
      p), and hence degenerate on the group
      Figure US20090034714A9-20090205-P00001
      1. To get a non-degenerate map we define the modified Weil pairing ê:
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1
      Figure US20090034714A9-20090205-P00001
      2 as follows:
      ê(P,Q)=e(P,φ(Q))
      The modified Weil pairing satisfies the following properties:
    • 1. Bilinear: For all P, Qε
      Figure US20090034714A9-20090205-P00001
      1 and for all a, bε
      Figure US20090034714A9-20090205-P00002
      we have ê(aP, bQ)=ê(P, Q)ab.
    • 2. Non-degenerate: If P is a generator of
      Figure US20090034714A9-20090205-P00001
      1 then ê(P, P)ε
      Figure US20090034714A9-20090205-P00003
      *p 2 is a generator of
      Figure US20090034714A9-20090205-P00001
      2.
    • 3. Computable: Given P, Qε
      Figure US20090034714A9-20090205-P00001
      1 there is an efficient algorithm to compute ê(P, Q)ε
      Figure US20090034714A9-20090205-P00001
      2. (This algorithm is described in the section below entitled Description of the Weil Pairing.) Its running time is comparable to exponentiation in
      Figure US20090034714A9-20090205-P00003
      p.
      Although the Computational Diffie-Hellman problem (CDH) appears to be hard in the group
      Figure US20090034714A9-20090205-P00001
      1, the Decision Diffie-Hellman problem (DDH) is easy in
      Figure US20090034714A9-20090205-P00001
      1.
      BDH Parameter Generator
      Figure US20090034714A9-20090205-P00904
      1: Given a security parameter 2<kε
      Figure US20090034714A9-20090205-P00002
      the BDH parameter generator picks a random k-bit prime q and finds the smallest prime p such that (1) p=2 mod 3, (2) q divides p+1, and (3) q2 does not divide p+1. We write p=lq+1. The group
      Figure US20090034714A9-20090205-P00001
      1 is the subgroup of order q of the group of points on the curve y2=x3+1 over
      Figure US20090034714A9-20090205-P00002
      p. The group
      Figure US20090034714A9-20090205-P00001
      2 is the subgroup of order q of
      Figure US20090034714A9-20090205-P00003
      *p 2 . The bilinear map ê:
      Figure US20090034714A9-20090205-P00001
      1×
      Figure US20090034714A9-20090205-P00001
      1
      Figure US20090034714A9-20090205-P00001
      2 is the modified Weil pairing defined above.
  • The BDH parameter generator
    Figure US20090034714A9-20090205-P00904
    1 is believed to satisfy the BDH assumption asymptotically. However, there is still the question of what values of p and q can be used in practice to make the BDH problem sufficiently hard. It is desirable that we can ensure, at the very least, that the discrete log problem in
    Figure US20090034714A9-20090205-P00001
    1 is sufficiently hard. As pointed out earlier, the discrete log problem in
    Figure US20090034714A9-20090205-P00001
    1 is efficiently reducible to discrete log in
    Figure US20090034714A9-20090205-P00001
    2. Hence, computing discrete log in
    Figure US20090034714A9-20090205-P00003
    *p 2 is sufficient for computing discrete log in
    Figure US20090034714A9-20090205-P00001
    1. In practice, for proper security of discrete log in
    Figure US20090034714A9-20090205-P00003
    *p 2 it is desirable to use primes p that are at least 512-bits long (so that the group size is at least 1024 bits long). Consequently, in some embodiments, this BDH parameter generator is used with primes p that may be 512-bits long or more.
  • An Admissible Encoding Function: MapToPoint
  • Let
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 be two groups generated by
    Figure US20090034714A9-20090205-P00904
    1 as defined above. Recall that an IBE system discussed earlier uses a hash function H1: {0, 1}*→
    Figure US20090034714A9-20090205-P00001
    *1. It suffices to have a hash function H1: {0, 1}*→A for some set A, and an admissible encoding function L: A→
    Figure US20090034714A9-20090205-P00001
    *1. In what follows the set A will be
    Figure US20090034714A9-20090205-P00003
    p, and the admissible encoding function L will be called MapToPoint, which may be used in various embodiments of the present invention.
  • In this example, let p be a prime satisfying p=2 mod 3 and p=lq−1 for some prime q>3. In this exemplary embodiment, q does not divide l (i.e. q2 does not divide p+1). Let E be the elliptic curve y2=x3+1 over
    Figure US20090034714A9-20090205-P00003
    p. Let
    Figure US20090034714A9-20090205-P00001
    1 be the subgroup of points on E of order q. In addition, a hash function H1: {0, 1}*→
    Figure US20090034714A9-20090205-P00003
    p is provided.
  • In this exemplary embodiment, algorithm MapToPoint works as follows on input y0ε
    Figure US20090034714A9-20090205-P00003
    p:
  • 1. Compute x0=(y0 2−1)1/3=(y0 2−1)(2p−1)/3ε
    Figure US20090034714A9-20090205-P00003
    p.
  • 2. Let Q=(x0, y0)εE(
    Figure US20090034714A9-20090205-P00003
    p) and set QID=lQε
    Figure US20090034714A9-20090205-P00001
    1.
  • 3. Output MapToPoint (y0)=QID.
  • This completes the description of MapToPoint.
  • We note that there are l−1 values of y0ε
    Figure US20090034714A9-20090205-P00003
    p for which lQ=l(x0, y0)=O (these are the non-O points of order dividing l). Let B⊂
    Figure US20090034714A9-20090205-P00003
    p be the set of these y0. When H1(ID) is one of these l−1 values QID is the identity element of
    Figure US20090034714A9-20090205-P00001
    1. It is extremely unlikely for H1(ID) to hit one of these points—the probability is 1/{dot over (q)}<½k. Hence, for simplicity we say that H1(ID) only outputs elements in
    Figure US20090034714A9-20090205-P00003
    p\B, i.e. H1: {0, 1}*→
    Figure US20090034714A9-20090205-P00003
    p\B. In other embodiments, algorithm MapToPoint can be easily extended to handle the values y0εB by hashing ID multiple times using different hash functions.
  • Proposition 8 MapToPoint:
    Figure US20090034714A9-20090205-P00003
    p\B→
    Figure US20090034714A9-20090205-P00001
    *1 is an admissible encoding function.
  • Proof The map is clearly computable and is a l-to-1 mapping. It remains to show that L is samplable. Let P be a generator of E(
    Figure US20090034714A9-20090205-P00003
    p). Given a Qε
    Figure US20090034714A9-20090205-P00001
    *1 the sampling algorithm
    Figure US20090034714A9-20090205-P00907
    s does the following: (1) pick a random bε{0, . . . , l−1}, (2) compute Q′=l−1·Q+bqP=(x, y), and (3) output
    Figure US20090034714A9-20090205-P00907
    s(Q)=yε
    Figure US20090034714A9-20090205-P00003
    p. Here l−1 is the inverse of l in
    Figure US20090034714A9-20090205-P00002
    *q. This algorithm outputs a random element from the l elements in MapToPoint−1(Q) as required. □
  • A Detailed Example of an IBE System
  • Using the BDH parameter generator
    Figure US20090034714A9-20090205-P00904
    1 and the admissible encoding function MapToPoint we obtain the following detailed example of an embodiment of an IBE system.
    • Setup: Given a security parameter kε
      Figure US20090034714A9-20090205-P00002
      +, the algorithm works as follows:
      • Step 1: Run
        Figure US20090034714A9-20090205-P00904
        1 on input k to generate a k-bit prime q and a prime p=2 mod 3 such that q divides p+1. Let E be the elliptic curve defined by y2=x3+1 over
        Figure US20090034714A9-20090205-P00003
        p. Choose an arbitrary PεE(
        Figure US20090034714A9-20090205-P00003
        p) of order q.
      • Step 2: Pick a random sε
        Figure US20090034714A9-20090205-P00002
        *q and set Ppub=sP.
      • Step 3: Pick four hash functions: H1: {0, 1}*→
        Figure US20090034714A9-20090205-P00003
        p; H2:
        Figure US20090034714A9-20090205-P00003
        p 2 →{0, 1}n for some n H3: {0, 1}n×{0, 1}n
        Figure US20090034714A9-20090205-P00002
        *q, and a hash function H4: {0, 1}n→{0, 1}n.
      • The message space is
        Figure US20090034714A9-20090205-P00901
        ={0, 1}n. The ciphertext space is
        Figure US20090034714A9-20090205-P00902
        =E(
        Figure US20090034714A9-20090205-P00003
        p)×{0, 1}n. The system parameters are params=<p, q, n, P, Ppub, H1, . . . , H4>. The master-key is sε
        Figure US20090034714A9-20090205-P00002
        *q.
    • Extract: For a given string IDε{0, 1}* the algorithm builds a private key d as follows:
      • Step 1: Compute MapToPoint(H1(ID))=QIDεE(
        Figure US20090034714A9-20090205-P00003
        p) of order q.
      • Step 2: Set the private key dID to be dID=sQID where s is the master key.
    • Encrypt: To encrypt Mε{0, 1}n under the public key ID do the following:
      • Step 1: Compute MapToPoint(H1(ID))=QIDεE(
        Figure US20090034714A9-20090205-P00003
        p) of order q.
      • Step 2: Choose a random σε{0, 1}n.
      • Step 3: Set r=H3(σ, M).
      • Step 4: Set the ciphertext to be
        C=<rP,σ⊕H 2(g ID r),M⊕H 4(σ)> where g ID (Q ID ,P pub
        Figure US20090034714A9-20090205-P00003
        p 2
    • Decrypt: Let C=<U, V, W>ε
      Figure US20090034714A9-20090205-P00902
      be a ciphertext encrypted using the public key ID. If UεE(
      Figure US20090034714A9-20090205-P00003
      p) is not a point of order q reject the ciphertext. To decrypt C using the private key dID do:
      Step 1. Compute V⊕H2(ê(dID, U))=σ.
      Step 2. Compute W⊕(H4(σ)=M.
      Step 3. Set r=H3(σ, M). Test that U=rP. If not, reject the ciphertext.
      Step 4. Output M as the decryption of C.
      Performance. In this embodiment, algorithms Setup and Extract are very simple. At the heart of both algorithms is a standard multiplication on the curve E(
      Figure US20090034714A9-20090205-P00003
      p). Algorithm Encrypt requires that the encryptor compute the Weil pairing of QID and Ppub. Note that this computation is independent of the message, and hence can be done once and for all. Once gID is computed the performance of this embodiment is almost identical to standard ElGamal encryption. We also note that the ciphertext length of the exemplary embodiment of BasicIdent is the same as in regular ElGamal encryption in
      Figure US20090034714A9-20090205-P00003
      p. Decryption is a simple Weil pairing computation.
      Security. The security of the detailed exemplary embodiment just described follows directly from Theorem 4 and Theorem 7.
      Corollary 9 The detailed exemplary embodiment described above is a chosen ciphertext secure IBE system (i.e. IND-ID-CCA in the random oracle model) assuming the BDH parameter generator
      Figure US20090034714A9-20090205-P00904
      1 satisfies the BDH assumption.
      Extensions and Observations
      Tate Pairing and Other Curves.
  • Embodiments of our IBE system work with efficiently computable bilinear maps ê:
    Figure US20090034714A9-20090205-P00001
    1×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 between two groups
    Figure US20090034714A9-20090205-P00001
    1,
    Figure US20090034714A9-20090205-P00001
    2 where the BDH assumption holds. Many different elliptic curves may give rise to such maps. For example, one could use the curve y2=x3+x over
    Figure US20090034714A9-20090205-P00003
    p with p=3 mod 4 and its endomorphism φ: (x, y)→(−x, iy) where i2=−1.
  • In an alternative embodiment, one may use a family of nonsupersingular elliptic curves over
    Figure US20090034714A9-20090205-P00003
    p discussed by Miyaji et al. (A. Miyaji, M. Nakabayashi, S. Takano, “New explicit condition of elliptic curve trace for FR-reduction”, IEICE Trans. Fundamentals, Vol. E84 A, No. 5, May 2001). For example, to use a curve E/
    Figure US20090034714A9-20090205-P00003
    p in this family one can take
    Figure US20090034714A9-20090205-P00001
    1 to be a cyclic subgroup of E(
    Figure US20090034714A9-20090205-P00003
    p 6 ) (that is not contained in E(
    Figure US20090034714A9-20090205-P00003
    p)) and then use the trace map on the curve E as the endomorphism φ used to define the pairing ê. We also note that both encryption and decryption in FullIdent can be made faster in alternate embodiments by using the Tate pairing on elliptic curves rather than the Weil pairing. In other embodiments, suitable bilinear maps may be derived from abelian varieties.
  • Asymmetric Pairings
  • As mentioned earlier, embodiments of our IBE system are not limited to symmetric maps, but may include asymmetric maps as well. In other words, embodiments generally may use maps of the form ê:
    Figure US20090034714A9-20090205-P00001
    0×
    Figure US20090034714A9-20090205-P00001
    1
    Figure US20090034714A9-20090205-P00001
    2 where
    Figure US20090034714A9-20090205-P00001
    0,
    Figure US20090034714A9-20090205-P00001
    1 are groups of prime order q. When
    Figure US20090034714A9-20090205-P00001
    0 and
    Figure US20090034714A9-20090205-P00001
    are equal we say the map is symmetric. When
    Figure US20090034714A9-20090205-P00001
    0 and
    Figure US20090034714A9-20090205-P00001
    1 are not equal we say the map is asymmetric.
  • The elements QID and P in the asymmetric case are members of
    Figure US20090034714A9-20090205-P00001
    0 and
    Figure US20090034714A9-20090205-P00001
    1, respectively (or vice versa), and the target group of the hash function H1 is selected accordingly. However, to make the proof of security go through (Lemma 2 in particular) we use a slightly strange looking complexity assumption which we call the co-BDH assumption: given random P, aP, bPε
    Figure US20090034714A9-20090205-P00001
    1 and Q, aQ, cQε
    Figure US20090034714A9-20090205-P00001
    0 no polynomial time algorithm can compute ê(P, Q)abc with non-negligible probability. If one is uses this assumption then for embodiments using a curve E/
    Figure US20090034714A9-20090205-P00003
    p from Miyaji et al. (as just described above) one can take
    Figure US20090034714A9-20090205-P00001
    1 to be a cyclic subgroup of E(
    Figure US20090034714A9-20090205-P00003
    p) of order q and
    Figure US20090034714A9-20090205-P00001
    0 to be a different cyclic subgroup of E(
    Figure US20090034714A9-20090205-P00003
    p 6 ) of order q. This will result in a more efficient system than the method described in the preceding paragraph for using these curves.
  • Distributed PKG
  • In exemplary embodiments of an IBE system it is desirable that the master-key stored at the PKG be protected. One way of protecting this key is by distributing it among different sites using techniques of threshold cryptography. Embodiments of our IBE system support this in a very efficient and robust way. Recall that in some embodiments discussed above, the master-key may be some sε
    Figure US20090034714A9-20090205-P00002
    *q and the PKG uses the group action to compute a private key from s and QID, where QID is derived from the user's public key ID. For example, dID=sQID. A distributed PKG embodiment can be implemented in a t-out-of-n fashion by giving each of the n PKGs one share si of a Shamir secret sharing of s mod q. Each of the n PKGs can use its share si of the master key to generate a corresponding share di of a private key dID by calculating di=siQID. The user can then construct the entire private key dID by requesting from t of the n PKGs its share di of the private key, then combining the shares by calculating d ID = i λ i d i ,
    where the λi's are the appropriate Lagrange interpolation coefficients.
  • Furthermore, it is easy to make this embodiment robust against dishonest PKGs using the fact that DDH is easy in
    Figure US20090034714A9-20090205-P00001
    1. During setup each of the n PKGs publishes Pi=siP. During a key generation request the user can verify that the response from the i'th PKG is valid by testing that:
    ê(d i ,P)=ê(Q ID ,P i)
    Thus, a misbehaving PKG will be immediately caught. There is no need for zero-knowledge proofs as in regular robust threshold schemes. The PKG's master-key can be generated in a distributed fashion using the techniques of R. Gennaro et al. (R. Gennaro, S. Jarecki, H. Krawczyk, T. Rabin, “Secure Distributed Key Generation for Discrete-Log Based Cryptosystems”, Advances in Cryptology—Eurocrypt '99, Lecture Notes in Computer Science, Vol. 1592, Springer-Verlag, pp. 295-310, 1999). Using this technique, the PKGs can execute a cooperative protocol that allows them to jointly generate their respective shares of the master key without the master key ever existing in any one place.
  • Note that a distributed master-key embodiment also enables threshold decryption on a per-message basis, without any need to derive the corresponding decryption key. For example, threshold decryption of BasicIdent ciphertext (U, V) is straightforward if each PKG responds with ê(siQID, U).
  • FIG. 5 is a block diagram illustrating a distributed PKG system, according to an embodiment of the invention. FIG. 5 includes a sender system 501, receiver system 502 and three PKGs (PKG A 503, PKG B 504 and PKG C 505). In one embodiment illustrating a 2-out-of-3 sharing, each of three PKGs contains a different share of a master key, and any two of the three are able to derive the master key. As shown in the figure, PKG A 503, PKG B 504, and PKG C 505 include, respectively, master key share s1, 511, master key share 52, 512, and master key share s3, 513. In 2-out-of-3 sharing, any two out of these three PKGs could combine their shares to determine the master key, although in this embodiment each PKG secretly holds its master key share.
  • Sender system 501 sends a message to receiver 502. The message 514 may be encrypted using a public key based on an identifier ID of the receiver. In order to obtain the corresponding private key, the receiver system queries two of the three PKGs using, for example, the receiver's identity or public key. As shown in the figure, receiver system 502 makes queries 506 and 507 to PKG A 503 and PKG B 504, respectively, in order to obtain two shares of the private key. In response to the queries, PKG A 503 and PKG B 504 return, respectively, share d1, 508, and share d2, 509, of private key d, 510. Receiver system 502 is then able to assemble the corresponding private key dID, which corresponds to the public key with which the message 514 was encrypted. More generally, the receiver could have selected to query any two of the three PKGs. For example, receiver system 502 alternatively could have queried PKGs B and C and combined private key shares d2 and d3 to produce the private key 510. These techniques easily generalize to provide similar embodiments using t-out-of n sharing.
  • Sender system 501, receiver system 502 as well as PKGs 503, 504 and 505 may be each implemented as computer systems which include elements such as processors and computer-readable media such as memory and other storage devices. Communication between the respective elements may take place using data packets sent over data networks, or any of various other forms of electronic and data transmission and communication. The communication may transpire over various architectures of communication, such as a computer network, such as the Internet, with various wired, wireless and other communications media.
  • Working in Subgroups
  • In an alternative embodiment of the detailed IBE system described above, performance may be improved by working in a comparatively small subgroup of the curve. For example, choose a 1024-bit prime p=2 mod 3 with p=aq−1 for some 160-bit prime q. The point P is then chosen to be a point of order q. Each public key ID is converted to a group point by hashing ID to a point Q on the curve and then multiplying the point by a. The system is secure if the BDH assumption holds in the group generated by P. The advantage of this embodiment is that the Weil computation is done on points of small order, and hence is much faster.
  • IBE Implies Signatures
  • Various IBE techniques described above can be used to provide public key signature systems and methods. The intuition is as follows. The private key for the signature scheme is the master key for the IBE scheme. The public key for the signature scheme is the set of global system parameters for the IBE scheme. The signature on a message M is the IBE decryption key for ID=M. To verify a signature, choose a random message M′, encrypt M′ using the public key ID=M, and then attempt to decrypt using the given signature on M as the decryption key. If the IBE system is IND-ID-CCA, then the signature scheme is existentially unforgeable against a chosen message attack. Note that, unlike most signature schemes, this signature verification embodiment is randomized. This shows that the IBE techniques described herein may encompass both public key encryption and digital signatures. Signature schemes derived from these approaches can be used to provide interesting properties, as described by Boneh et al. (D. Boneh, B. Lynn, H. Shacham, “Short signatures from the Weil pairing”, in Advances in Cryptology—AsiaCrypt 2001, Lecture Notes in Computer Science, Vol. 2248, Springer-Verlag, pp. 514-532, 2001, which is incorporated herein by reference).
  • Escrow ElGamal Encryption
  • In this section we show that various IBE techniques described above can be used to provide an ElGamal encryption system embodiment having global escrow capability. In this embodiment, a single escrow key enables the decryption of ciphertexts encrypted under any public key.
  • In one exemplary embodiment, the ElGamal escrow system works as follows. The Setup is similar to that for BasicIdent. Unlike the identity-based BasicIdent, each user selects a secret random number and uses it to generate a public/private key pair. A sender and receiver can then use Encrypt and Decrypt to communicate an encrypted message. The message is secure except for an escrow who can use a master key s to decrypt the message.
  • FIG. 6 is a block diagram illustrating elements in a cryptosystem with escrow decryption capability according to an embodiment of the invention. The system includes a sender system 601 with encryption logic 610, receiver system 602 with decryption logic 611, escrow agent system 604 and broadcasting system 605. Broadcast system 605 sends system parameters to participants such as escrow agent system 604, receiver system 602 and sender system 601. The receiver system 602 selects a private key x, 607, and uses it to generate a public key Ppub=xP, 606, which is then published. The private key x and the public key Ppub form a complementary key pair. Using the public key Ppub=xP, 606, sender system 601 encrypts a message M with encryption logic 610. Sender system 601 sends a resulting encrypted message 603 to receiver 602. Receiver system 602 decrypts the message with decryption logic 611 using the private key x, 607. Escrow agent system 604 may intercept message 603 and, using the escrow agent key s, 609, public key Ppub=xP, 606, and decrypt message 603 with decryption logic 612. In an alternate embodiment, broadcast system 605 and escrow agent 604 may be a single entity. In yet another embodiment, the escrow agent key s may be shared in a manner such as in the distributed PKG embodiments described earlier.
  • In more detail, an exemplary embodiment of the technique involves the following procedures:
    • Setup: Let
      Figure US20090034714A9-20090205-P00904
      be some BDH parameter generator. Given a security parameter kε
      Figure US20090034714A9-20090205-P00002
      +, the algorithm works as follows:
      • Step 1: Run
        Figure US20090034714A9-20090205-P00904
        on input k to generate a prime q, two groups
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2 of order q, and an admissible map ê:
        Figure US20090034714A9-20090205-P00001
        1×
        Figure US20090034714A9-20090205-P00001
        1
        Figure US20090034714A9-20090205-P00001
        2. Let P be some generator of
        Figure US20090034714A9-20090205-P00001
        1.
      • Step 2: Pick a random sε
        Figure US20090034714A9-20090205-P00002
        *q and set Q=sP.
      • Step 3: Choose a cryptographic hash function H:
        Figure US20090034714A9-20090205-P00001
        2→{0, 1}n.
      • The message space is
        Figure US20090034714A9-20090205-P00901
        ={0, 1}n. The ciphertext space is
        Figure US20090034714A9-20090205-P00902
        =
        Figure US20090034714A9-20090205-P00001
        1×{0, 1}n. The system parameters are params=<q,
        Figure US20090034714A9-20090205-P00001
        1,
        Figure US20090034714A9-20090205-P00001
        2, ê, n, P, Q, H>. The escrow key is sε
        Figure US20090034714A9-20090205-P00002
        *q.
    • keygen: A user generates a public/private key pair for herself by picking a random xε
      Figure US20090034714A9-20090205-P00002
      *q and computing Ppub=xPε
      Figure US20090034714A9-20090205-P00001
      1. Her private key is x (or xQ), her public key is Ppub.
    • Encrypt: To encrypt Mε{0, 1}n under the public key Ppub do the following: (1) pick a random rε
      Figure US20090034714A9-20090205-P00002
      *q, and (2) set the ciphertext to be:
      C=<rP,M⊕H(g r)> where g=ê(P pub ,Q
      Figure US20090034714A9-20090205-P00001
      2.
      • This encryption technique is also illustrated in FIG. 7, where the sender obtains the system parameters and elements P and Q=sP in block 700, and obtains the recipient's public key Ppub=xP in block 710. The sender then selects a random r and computes a message key in block 720. The message key is then used to encrypt a message in block 730. The sender then transmits an encapsulated key rP and encrypted message V to the receiver.
    • Decrypt: Let C=<U, V> be a ciphertext encrypted using Ppub. Then Uε
      Figure US20090034714A9-20090205-P00001
      l. To decrypt C using the private key x do:
      V⊕H(ê(U,xQ))=M.
      • As illustrated in FIG. 8, the receiver obtains the system parameters and elements P and Q=sP in block 800, then obtains the encrypted message V and encapsulated key rP from the sender in block 810. The receiver then computes the message key in block 820, and uses it to decrypt the message in block 830.
      • To see that the message keys computed by the sender and receiver are the same, note that the sender knows the secret r as well as the public Q=sP and Ppub=xP, and uses these to compute a key from ê(sP, xP)r. The receiver, on the other hand, knows the secret x as well as the public Q=sP and rP, and uses these to compute a message key from ê(rP, x(sP)). The bilinearity of ê implies that ê(sP, xP)r=ê(rP, x(sP)), so the sender and receiver compute the same message key.
    • Escrow-decrypt: The purpose of this embodiment is to permit escrow decryption of otherwise secure communications. To decrypt C=<U, V> using the escrow key s, compute:
      V⊕H(ê(U,sP pub))=M.
      • As shown in FIG. 9, the escrow obtains the system parameters and element P in block 900, then in block 910 obtains the recipient's public key xP, and obtains the encrypted message V and encapsulated key rP from the sender. The escrow then computes the message key in block 920, and uses it to decrypt the message in block 930. The escrow can compute the message key from the knowledge of s, rP, and xP.
        A standard argument shows that assuming that BDH is hard for groups generated by
        Figure US20090034714A9-20090205-P00904
        the system of this embodiment has semantic security in the random oracle model (recall that since DDH is easy we cannot prove semantic security based on DDH). Yet, the escrow agent can decrypt any ciphertext encrypted using any user's public key. The decryption capability of the escrow agent can be distributed using the PKG distribution techniques described earlier.
  • Another embodiment uses a similar hardness assumption, with an ElGamal encryption system with non-global escrow. In this embodiment, each user constructs a public key with two corresponding private keys, and gives one of the private keys to the trusted third party. The trusted third party maintains a database of all private keys given to it by the various users. Although both private keys can be used to decrypt, only the user's private key can be used simultaneously as the signing key for a discrete logarithm based signature scheme.
  • Various other cryptographic systems can be devised based on the principles illustrated in the above embodiments. For example, three entities A, B, and C can communicate securely as a group by privately selecting random integers a, b, c and publishing public keys aP, bP, cP. One of them, such as A, could encrypt a message using the message key ê(bP, cP)r and transmit it with rP. Then B could decrypt the message by calculating ê(cP, rP)b and C could decrypt it by calculating ê(bP, rP)c. Similarly, B could send a message to A and C, or C could send a message to A and B.
  • In another possible embodiment, two of the three entities, say A and B, could publish a joint public key abP. Then C could encrypt a message using the message key ê(abP, cP)r and transmit it with rP. Then neither A nor B alone could decrypt the message, but both A and B together could compute ê(cP, rP)ab and jointly decrypt the message. This technique generalizes to any number of entities. For example, C could join A and B by using abP to compute and publish the three-way joint public key abcP. Then anyone could encrypt a message using the message key ê(abcP, xP)r and transmit it with rP. Then only A and B and C together could compute ê(xP, rP)abc and jointly decrypt the message.
  • Threshold Decryption.
  • Embodiments of the invention enable n entities to have shares of a private key dID corresponding to a given public key ID, so that messages encrypted using ID can only be decrypted if t of the n entities collaborate. The private key dID is never reconstructed in a single location. Embodiments of our IBE system may support this as follows.
  • Recall that in other embodiments the private key dID=sQID where sε
    Figure US20090034714A9-20090205-P00002
    *q is the master-key. Instead, let s1, . . . snε
    Figure US20090034714A9-20090205-P00002
    *q be a t-out-of-n Shamir secret sharing of the master-key s. Each of the n users is given di=siQID. To decrypt a ciphertext <U, V> encrypted using the key ID each user locally computes gi=ê(U, di) and sends giε
    Figure US20090034714A9-20090205-P00001
    2 to the user managing the decryption process. That user then combines the decryption shares by computing gID= i g i λ i
    where λi are the appropriate Lagrange interpolation coefficients used in Shamir secret sharing. The message is then obtained by computing H2(gID)⊕V=M.
  • Those skilled in the art of cryptography will be able to devise many other schemes that employ the basic principles of the present invention.
  • Applications of Identity-Based Encryption
  • One application for embodiments of identity-based encryption is to help the deployment of a public key infrastructure. In this section, we show several embodiments of this and other applications.
  • Revocation of Public Keys
  • In this embodiment, the sender may encrypt using a public key derived from a piece of information containing a time element, such as a year, date or other time, to help provide key expiration or other forms of temporal key management. For example, in one embodiment, key expiration can be done by having Alice encrypt e-mail sent to Bob using the public key: “bob@company.com ∥ current-year”. In doing so Bob can use his private key during the current year only. Once a year Bob needs to obtain a new private key from the PKG. Hence, we get the effect of annual private key expiration. Note that unlike the existing public key infrastructure, Alice does not need to obtain a new certificate from Bob every time Bob refreshes his private key.
  • One may make this approach more granular in other embodiments by encrypting e-mail for Bob using “bob@company.com ∥ current-date”, or using another time stamp. This forces Bob to obtain a new private key every day. This embodiment may be used in a corporate context where the PKG is maintained by the corporation. With this approach key revocation is very simple: when Bob leaves the company and his key needs to be revoked, the corporate PKG is instructed to stop issuing private keys for Bob's e-mail address. As a result, Bob can no longer read his email. The interesting property is that Alice does not need to communicate with any third party certificate directory to obtain Bob's daily public key. Hence, embodiments of identity based encryption can provide a very efficient mechanism for implementing ephemeral public keys. Also note that this embodiment can be used to enable Alice to send messages into the future: Bob will only be able to decrypt the e-mail on the date specified by Alice.
  • Managing User Credentials
  • An embodiment of the invention enables the management of user credentials using an IBE system. The message is encrypted with a string containing a credential identifier. For example, suppose Alice encrypts mail to Bob using the public key: “bob@company.com ∥ current-year ∥ clearance=secret”. Then Bob will only be able to read the email if on the specified date he has secret clearance. Consequently, it is very easy to grant and revoke user credentials using the PKG.
  • FIG. 10 is a block diagram illustrating a system for managing credentials in an identity based encryption system according to an embodiment of the invention. The system includes sender system 1001, receiver system 1002 and PKG 1003. Each such system may be implemented as a computer system such as a client or server connected to a computer network. Accordingly, sender 1001, receiver 1002 and PKG 1003 may each contain processors, such as processor 1014, processor 1013 and processor 1012. Additionally, these systems may include computer-readable storage media, such as computer memory, and may additionally include interfaces to a computer network, including technology allowing for communication with a wired, wireless or other network. Sender system 1001 may include a software plug-in 1017. Such a plug-in may comprise a software module which performs cryptographic functions. The plug-in includes, according to an embodiment of the invention, items such as cryptographic logic 1004. Plug-in 1017 may be distributed to various computers such as sender system 1001 and receiver system 1002 through a network in order to roll out functionality associated with identity-based encryption and other communication functionality. Parameters 1015 from a system such as PKG 1003 are also distributed over a computer network or other communications medium to senders and receivers, such as sender system 1001 and receiver system 1002, who may then use them in conjunction with plug-in 1017 when encrypting or decrypting messages. In one embodiment, plug-in 1017 is distributed together with parameters 1014. In an alternate embodiment, parameters 1015 may be distributed separately.
  • Sender system 1001 encrypts a message M using encryption logic 1004 in plug-in 1017. Encryption logic 1004 encrypts the message using encryption key 1011, which is based on selected credential 1005 and an identification 1016 of the intended receiver of the message. In some embodiments, the key may be based on other information as well. The sender system 1001 sends the receiver system 1002 information 1006, e.g., in the form of a data packet transmitted over a network or other communication medium. The information 1006 sent to receiver system 1002 contains the encrypted message and may also contain information 1007 regarding the credential 1005 used as part of the basis for the encryption key.
  • Either before or after receiving information 1006, receiver system 1002 sends a request 1009 to PKG 1003. In one embodiment, the request 1009 may include the receiver's identity 1016 and may also include information related to the selected credential 1005. In response, PKG 1003 verifies the credential of receiver 1002 using credential check logic 1008. Such logic may be implemented in software, hardware or a combination thereof. If the credential is verified as belonging to the receiver, then PKG 1003 provides a response 1010 to receiver 1002, which includes a private decryption key 1018 corresponding to the encryption key 1011. Using the private decryption key, the receiver then may decrypt the encrypted message contained in information 1006 to recover the original message M. Thus, by including a credential as part of an encryption key, embodiments such as this one allow a sender to encrypt a message intended for a receiver, where the decryption of the message by the receiver is contingent upon the validity of the receiver's credential.
  • Delegation of Decryption Keys
  • Another application for embodiments of IBE systems is delegation of decryption capabilities. We give two exemplary embodiments, described with reference to a user Bob who plays the role of the PKG. Bob runs the setup algorithm to generate his own IBE system parameters params and his own master-key. Here we view params as Bob's public key. Bob obtains a certificate from a CA for his public key params. When Alice wishes to send mail to Bob she first obtains Bob's public key params from Bob's public key certificate. Note that Bob is the only one who knows his master-key and hence there is no key-escrow with this setup.
    • 1. Delegation to a laptop. Suppose Alice encrypts mail to Bob using the current date as the IBE encryption key (she uses Bob's params as the IBE system parameters). Since Bob has the master-key he can extract the private key corresponding to this IBE encryption key and then decrypt the message. Now, suppose Bob goes on a trip for seven days. Normally, Bob would put his private key on his laptop. If the laptop is stolen the private key is compromised. When using the IBE system Bob could simply install on his laptop the seven private keys corresponding to the seven days of the trip. If the laptop is stolen, only the private keys for those seven days are compromised. The master-key is unharmed. FIG. 11 is a block diagram illustrating a system with key delegation according to an embodiment of the invention. The system includes user system 1101 and target system 1102. The target system may comprise a computer such as a laptop computer. User system 1101 includes a master key 1103, which is used to generate decryption keys 1104. The decryption keys 1104 are downloaded to the target system 1102. Using the techniques of key revocation described above, these decryption keys may be valid only for a limited time, thus providing additional security in the event that target system 1101 is compromised. User system 1101 and target system 1102 may include elements of computer systems such as memory 1106 and 1107 as well as processor 1105 and 1108. User system 1101 includes key generator logic 1109, which uses master key 1103 and system parameters 1110 to generate private decryption keys 1104 based on information derived from a user ID 1113 and one or more dates 1114 or other time stamps. Target system 1102 includes decryption logic 1111, which uses the private decryption keys 1104 obtained from user system 1101 and system parameters 1110 to decrypt an incoming encrypted message 1112. If message 1112 is encrypted using public keys based on ID 1113 and one of the dates 1114, then private decryption keys may be used to decrypt it. Thus the decryption capabilities of target system 1102 may be limited to messages associated with selected dates 1114. In an alternate embodiment, the target system may be a data storage medium or portable data storage device which can be connected as desired to other computer systems, thereby enabling use of the decryption keys on those systems.
    • 2. Delegation of duties. Suppose Alice encrypts mail to Bob using the subject line as the IBE encryption key. Bob can decrypt mail using his master-key. Now, suppose Bob has several assistants each responsible for a different task (e.g. one is ‘purchasing’, another is ‘human-resources’, etc.). In this embodiment, Bob may give one private key to each of his assistants corresponding to the assistant's responsibility. Each assistant can then decrypt messages whose subject line falls within its responsibilities, but it cannot decrypt messages intended for other assistants. Note that Alice only obtains a single public key from Bob (params), and she uses that public key to send mail with any subject line of her choice. The mail can only be read by the assistant responsible for that subject.
      • More generally, embodiments of IBE can simplify various systems that manage a large number of public keys. Rather than storing a big database of public keys the system can either derive these public keys from user names, or simply use the integers 1, . . . , n as distinct public keys. For example, in a corporation, each employee might have a unique employee number, and that number may serve also as the employee's public key.
        Return Receipt
  • FIG. 12 is a block diagram illustrating an encryption system with return receipt according to an embodiment of the invention. According to one embodiment of the invention, a sender can receive an confirmation that the recipient has received an encrypted message. More generally, upon receipt of a request for a decryption key from a receiver, the PKG takes an action separate from providing a decryption key to the receiver. Such an action comprises providing an acknowledgement to the sender that indicates that the message was received, according to one embodiment.
  • An embodiment of a system having return receipt capability is illustrated in FIG. 12. The system includes sender system 1201, recipient system 1202 and PKG system 1203. The sender system 1201, receiver system 1202 and PKG system 1203 may be implemented as computer systems coupled to a computer network. For example, PKG 1203, sender system 1201 and receiver system 1202 may include processor 1212, processor 1213 and processor and 1214, respectively. These computer systems may include elements such as computer readable storage media, computer memory and other storage devices. Additionally, these systems may include interfaces to a computer network, including technology allowing for communication from a wired, wireless or other network. Further, according an embodiment of the invention, communication between the respective elements may take place using data packets sent over a computer network, or using any of various other forms of electronic and data transmission and communication.
  • The sender 1201 encrypts a message M and sends the resulting ciphertext to receiver 1202 in a data package 1204 that also may include return receipt request information 1209. The return receipt request information may contain, for example, a return address and a message identifier corresponding to the particular message 1204. The message M is encrypted by the sender using encryption logic 1211 and an encryption key 1215. Encryption key 1215 may be based on a receiver ID (such as an e-mail address) 1216 and the return receipt request information 1209. Because the receiver ID and return receipt request information 1209 are used by the sender to determine the encryption key 1215, the receiver 1202 needs a corresponding decryption key that can be used to decrypt the message. Accordingly, recipient system 1202, in response to receiving message 1204, sends PKG 1203 a request 1206, which includes the return receipt request information 1209 and the receiver's ID, 1216. In response, PKG 1203 sends to receiver 1202 the private decryption key 1205, which receiver then uses with decryption logic 1217 to decrypt the ciphertext of message 1204 and recover the original message M. In addition to sending receiver 1202 the decryption key 1205, PKG 1203 also sends a return receipt 1207 to sender 1201. PKG 1203 may alternatively store the receipt on storage media as part of a log rather than send a return receipt. Return receipt 1207 may include information such as the message identifier. Thus, sender 1201 receives proof that recipient 1202 has received the message 1204. The system may be initialized by placing plug-in software in various systems, such as sender system 1201 and receiver system 1202. Such plug-in software may include system parameters, some of which may be derived from a system master key. Such parameters, stored in local devices such as sender 1201 and receiver 1202 are then used to generate encryption keys, perform encryption, perform decryption, and other functions, as appropriate.
  • Description of the Weil Pairing
  • In this section we describe the Weil pairing on elliptic curves and then show how to efficiently compute it using an algorithm. To be concrete we present an example using supersingular elliptic curves defined over a prime field
    Figure US20090034714A9-20090205-P00003
    p with p>3 (the curve y2=x3+1 over
    Figure US20090034714A9-20090205-P00003
    p with p=2 mod 3 is an example of such a curve). The following discussion easily generalizes to computing the Weil pairing over other elliptic curves.
  • Elliptic Curves and the Weil Pairing
  • We state a few elementary facts about supersingular elliptic curves defined over a prime field
    Figure US20090034714A9-20090205-P00003
    p with p>3:
    • Fact 1: A supersingular curve E/
      Figure US20090034714A9-20090205-P00003
      p (with p>3) contains p+1 points in
      Figure US20090034714A9-20090205-P00003
      p. We let O denote the point at infinity. The group of points over
      Figure US20090034714A9-20090205-P00003
      p forms a cyclic group of order p+1. For simplicity, let P be a generator of this group and set n=p+1.
    • Fact 2: The group of points E(
      Figure US20090034714A9-20090205-P00003
      p 2 ) contains a point Q of order n which is linearly independent of the points in E(
      Figure US20090034714A9-20090205-P00003
      p). Hence, E(
      Figure US20090034714A9-20090205-P00003
      p 2 ) contains a subgroup which is isomorphic to the group
      Figure US20090034714A9-20090205-P00002
      n 2. The group is generated by PεE(
      Figure US20090034714A9-20090205-P00003
      p) and QεE(
      Figure US20090034714A9-20090205-P00003
      p 2 ). We denote this group by E[p+1]=E[n].
      We will be working with the Weil pairing e which maps pairs of points in E[n] into
      Figure US20090034714A9-20090205-P00003
      *p 2 , i.e. e: E[n]×E[n]→
      Figure US20090034714A9-20090205-P00003
      *p 2 . To describe the pairing, we review the following concepts:
    • Divisors A divisor is a formal sum of points on the curve E(
      Figure US20090034714A9-20090205-P00003
      p 2 ). We write divisors as 𝒜 = P a p ( P )
    •  where aPε
      Figure US20090034714A9-20090205-P00002
      and PεE(
      Figure US20090034714A9-20090205-P00003
      p 2 ). For example,
      Figure US20090034714A9-20090205-P00903
      =3(P1)−2(P2)−(P3) is a divisor. We will only consider divisors f ( x , y ) 𝔽 p 2 ( x , y ) .
    •  where P a p = 0.
    • Functions Roughly speaking, a function ƒ on the curve E(
      Figure US20090034714A9-20090205-P00003
      p 2 ) can be viewed as a rational function ƒ(x, y)ε
      Figure US20090034714A9-20090205-P00003
      p 2 (x, y). For any point P=(x, y)εE(
      Figure US20090034714A9-20090205-P00003
      p 2 ) we define ƒ(P)=ƒ(x, y).
    • Divisors of functions Let ƒ be a function on the curve E(
      Figure US20090034714A9-20090205-P00003
      p 2 ). We define its divisor, denoted by (ƒ), as ( f ) = P ord P ( f ) · P .
    •  P. Here ordP(ƒ) is the order of the zero that ƒ has at the point P. For example, let ax+by+c=0 be the line passing through the points P1, P2εE(
      Figure US20090034714A9-20090205-P00003
      p 2 ) with P1 ≠±P2. This line intersects the curve at third point P3εE(
      Figure US20090034714A9-20090205-P00003
      p 2 ). Then the function ƒ(x, y)=ax+by+c has three zeroes P1, P2, P3 and a pole of order 3 at infinity. The divisor of ƒ is (ƒ)=(P1)+(P2)+(P3)−3(O).
    • Principal divisors Let
      Figure US20090034714A9-20090205-P00903
      be a divisor. If there exists a function ƒ such that (ƒ)=
      Figure US20090034714A9-20090205-P00903
      then we say that
      Figure US20090034714A9-20090205-P00903
      is a principal divisor. We know that a divisor 𝒜 = P a p ( P )
    •  is principal if and only if P a p = 0
    •  and P a P P = O .
    •  Note that the second summation is using the group action on the curve. Furthermore, given a principal divisor
      Figure US20090034714A9-20090205-P00903
      there exists a unique function ƒ (up to constant multiples) such that (A)=(ƒ).
    • Equivalence of divisors We say that two divisors
      Figure US20090034714A9-20090205-P00903
      ,
      Figure US20090034714A9-20090205-P00906
      are equivalent if their difference
      Figure US20090034714A9-20090205-P00903
      Figure US20090034714A9-20090205-P00906
      is a principal divisor. We know that any divisor 𝒜 = P a p ( P )
    •  (with ( with P a P = 0 )
    •  is equivalent to a divisor of the form
      Figure US20090034714A9-20090205-P00903
      ′=(Q)−(O) for some QεE. Observe that Q = P a P P .
    • Notation Given a function ƒ and a divisor 𝒜 = P a P ( P )
    •  we define ƒ(
      Figure US20090034714A9-20090205-P00903
      ) as ƒ(
      Figure US20090034714A9-20090205-P00903
      )=ΠPƒ(P)aP. Note that since P a P = 0
    •  we have that ƒ(
      Figure US20090034714A9-20090205-P00903
      ) remains unchanged if instead of ƒ we use cƒ for any cε
      Figure US20090034714A9-20090205-P00003
      p 2 .
      We are now ready to describe the Weil pairing of two points P, QεE[n]. Let
      Figure US20090034714A9-20090205-P00903
      P be some divisor equivalent to the divisor (P)−(O). We know that n
      Figure US20090034714A9-20090205-P00903
      P is a principal divisor (it is equivalent to n(P)−n(O) which is clearly a principal divisor). Hence, there exists a function ƒP such that (ƒP)=n
      Figure US20090034714A9-20090205-P00903
      P. Define
      Figure US20090034714A9-20090205-P00903
      Q and ƒQ analogously. The Weil pairing of P and Q is given by: e ( P , Q ) = f P ( 𝒜 Q ) f Q ( 𝒜 P )
      This ratio provides the value of the Weil pairing of P and Q whenever it is well defined (i.e., whenever no division by zero has occurred). If this ratio is undefined we use different divisors
      Figure US20090034714A9-20090205-P00903
      P,
      Figure US20090034714A9-20090205-P00903
      Q to define e(P, Q). When P, QεE(
      Figure US20090034714A9-20090205-P00003
      p 2 ) we have that e(P, Q)ε
      Figure US20090034714A9-20090205-P00003
      p 2 .
  • We briefly show that the Weil pairing is well defined. That is, the value of e(P, Q) is independent of the choice of the divisor
    Figure US20090034714A9-20090205-P00903
    P as long as
    Figure US20090034714A9-20090205-P00903
    P is equivalent to (P)−(O) and
    Figure US20090034714A9-20090205-P00903
    P leads to a well defined value. The same holds for
    Figure US20090034714A9-20090205-P00903
    Q. Let {circumflex over (
    Figure US20090034714A9-20090205-P00903
    )}P be a divisor equivalent to
    Figure US20090034714A9-20090205-P00903
    P and let {circumflex over (ƒ)}P be a function so that ({circumflex over (ƒ)}P)=n{circumflex over (
    Figure US20090034714A9-20090205-P00903
    )}P. Then {circumflex over (
    Figure US20090034714A9-20090205-P00003
    )}P=
    Figure US20090034714A9-20090205-P00903
    P+(g) for some function g and {circumflex over (ƒ)}PP·gn. We have that: e ( P , Q ) = f ^ P ( 𝒜 Q ) f Q ( 𝒜 ^ P ) = f P ( 𝒜 Q ) g ( 𝒜 Q ) n f Q ( 𝒜 P ) f Q ( ( g ) ) = f P ( 𝒜 Q ) f Q ( 𝒜 P ) · g ( n 𝒜 Q ) f Q ( ( g ) ) = f P ( 𝒜 Q ) f Q ( 𝒜 P ) · g ( ( f Q ) ) f Q ( ( g ) ) = f P ( 𝒜 Q ) f Q ( 𝒜 P )
    The last equality follows from the following fact known as Weil reciprocity: for any two functions ƒ, g we have that ƒ((g))=g((ƒ)). Hence, the Weil pairing is well defined.
    Fact 10 The Weil pairing has the following properties:
      • For all PεE[n] we have: e(P, P)=1.
      • Bilinear: e(P1+P2, Q)=e(P1, Q)·e(P2, Q) and e(P, Q1+Q2)=e(P, Q1)·e(P, Q2)
      • When P, QεE[n] are collinear then e(P, Q)=1. Similarly, e(P, Q)=e(Q, p)−1.
      • n'th root: for all P, QεE[n] we have e(P, Q)n=1.
      • Non-degenerate: if P satisfies e(P, Q)=1 for all QεE[n] then P=O.
  • As discussed earlier, our detailed example of an embodiment of an IBE scheme uses the modified Weil pairing ê(P, Q)=e(P, φ(Q)), where φ is an automorphism on the group of points of E.
    Tate pairing. The Tate pairing is another bilinear pairing that has the required properties for embodiments of our system. In various embodiments, we slightly modify the original definition of the Tate pairing to fit our purpose. Define the Tate pairing of two points P, QεE[n] as T ( P , Q ) = f P ( 𝒜 Q ) 𝔽 p 2 * / n
    where ƒP and
    Figure US20090034714A9-20090205-P00903
    Q are defined as earlier. This definition gives a computable bilinear pairing T: E[n]×E[n]→
    Figure US20090034714A9-20090205-P00001
    2.
    Computing the Weil Pairing
  • Given two points P, QεE[n] we show how to compute e(P, Q)ε
    Figure US20090034714A9-20090205-P00003
    *p 2 using O(log p) arithmetic operations in
    Figure US20090034714A9-20090205-P00003
    p. We assume P # Q. We proceed as follows: pick two random points R1, R2εE[n]. Consider the divisors
    Figure US20090034714A9-20090205-P00903
    P=(P+R1)−(R1) and
    Figure US20090034714A9-20090205-P00903
    Q=(Q+R2)−(R2). These divisors are equivalent to (P)−(O) and (O)−(O) respectively. Hence, we can use
    Figure US20090034714A9-20090205-P00903
    P and
    Figure US20090034714A9-20090205-P00903
    Q to compute the Weil pairing as: e ( P , Q ) = f P ( 𝒜 Q ) f Q ( 𝒜 P ) = f P ( Q + R 2 ) f Q ( R 1 ) f P ( R 2 ) f Q ( P + R 1 )
    This expression is well defined with very high probability over the choice of R1, R2 (the probability of failure is at most O ( log p p ) ) .
    In the rare event that a division by zero occurs during the computation of e(P, Q) we simply pick new random points R1, R2 and repeat the process.
  • To evaluate e(P, Q) it suffices to show how to evaluate the function ƒP at
    Figure US20090034714A9-20090205-P00903
    Q. Evaluating ƒQ(
    Figure US20090034714A9-20090205-P00903
    P) is done analogously. We evaluate ƒP(
    Figure US20090034714A9-20090205-P00903
    Q) using repeated doubling. For a positive integer b define the divisor
    Figure US20090034714A9-20090205-P00903
    b =b(P+R 1)−b(R 1)−(bP)+(O)
    It is a principal divisor and therefore there exists a function ƒb such that (ƒb)=
    Figure US20090034714A9-20090205-P00903
    b. Observe that (ƒP)=(ƒn) and hence, ƒP(
    Figure US20090034714A9-20090205-P00903
    Q)=ƒn(
    Figure US20090034714A9-20090205-P00903
    Q). It suffices to show how to evaluate ƒn(
    Figure US20090034714A9-20090205-P00903
    Q).
    Lemma 11 There is an algorithm
    Figure US20090034714A9-20090205-P00909
    that given ƒb(
    Figure US20090034714A9-20090205-P00903
    Q), ƒc(
    Figure US20090034714A9-20090205-P00903
    Q) and bP, cP, (b+c)P for some b, c>0 outputs ƒb+c(
    Figure US20090034714A9-20090205-P00903
    Q). The algorithm only uses a (small) constant number of arithmetic operations in
    Figure US20090034714A9-20090205-P00003
    p 2 .
    Proof We first define two auxiliary linear functions g1, g2:
      • 1. Let a1x+b1y+c1=0 be the line passing through the points bP and cP (if b=c then let a1x+b1y+c1=0 be the line tangent to E at bP). Define g1(x, y)=a1x+b1y+c1.
      • 2. Let x+c2=0 be the vertical line passing through the point (b+c)P. Define g2(x, y)=x+c2
        The divisors of these functions are:
        (g 1)=(bP)+(cP)+(−(b+c)P)−3(O)
        (g 2)=((b+c)P)+(−(b+c)P)−2(O)
        By definition we have that:
        Figure US20090034714A9-20090205-P00903
        b =b(P+R 1)−b(R 1)−(bP)+(O)
        Figure US20090034714A9-20090205-P00903
        c =c(P+R 1)−c(R 1)−(cP)+(O)
        Figure US20090034714A9-20090205-P00903
        b +c=(b+c)(P+R 1)−(b+c)(R 1)−((b+c)P)+(O)
        It now follows that:
        Figure US20090034714A9-20090205-P00903
        b+c=
        Figure US20090034714A9-20090205-P00903
        b+
        Figure US20090034714A9-20090205-P00903
        c+(g1)−(g2). Hence: f b + c ( 𝒜 Q ) = f b ( 𝒜 Q ) · f c ( 𝒜 Q ) · g 1 ( 𝒜 Q ) g 2 ( 𝒜 Q ) ( 1 )
        This shows that to evaluate ƒb+c(
        Figure US20090034714A9-20090205-P00903
        Q) it suffices to evaluate gi(
        Figure US20090034714A9-20090205-P00903
        Q) for all i=1, 2 and plug the results into equation 1. Hence, given ƒb(
        Figure US20090034714A9-20090205-P00903
        Q), ƒc(
        Figure US20090034714A9-20090205-P00903
        Q) and bP, cP, (b+c)P one can compute ƒb+c(
        Figure US20090034714A9-20090205-P00903
        Q) using a constant number of arithmetic operations.
  • Denote the output of Algorithm
    Figure US20090034714A9-20090205-P00909
    of Lemma 11 by
    Figure US20090034714A9-20090205-P00909
    b(
    Figure US20090034714A9-20090205-P00903
    Q), ƒc(
    Figure US20090034714A9-20090205-P00903
    Q), bP, cP, (b+c)P)=ƒb+c(
    Figure US20090034714A9-20090205-P00903
    Q). Then one can compute ƒP(
    Figure US20090034714A9-20090205-P00903
    Q)=ƒn(
    Figure US20090034714A9-20090205-P00903
    Q) using the following standard repeated doubling procedure. Let n=bmbm-1 . . . b1b0 be the binary representation of n, i.e. n = i = 0 m b i 2 i .
    Init: Set Z=O, V=ƒ0(
    Figure US20090034714A9-20090205-P00903
    Q)=1, and k=0.
    Iterate: For i=m, m−1, . . . , 1, 0 do:
      • 1: If bi=1 then do: Set V=
        Figure US20090034714A9-20090205-P00909
        (V, ƒ1(
        Figure US20090034714A9-20090205-P00903
        Q), Z, P, Z+P), set Z=Z+P, and set k=k+1.
      • 2: If i>0 set V=
        Figure US20090034714A9-20090205-P00909
        (V, V, Z, Z, 2Z), set Z=2Z, and set k=2k.
      • 3: Observe that at the end of each iteration we have z=kP and V=ƒk(
        Figure US20090034714A9-20090205-P00903
        Q).
        Output: After the last iteration we have k=n and therefore V=ƒn(
        Figure US20090034714A9-20090205-P00903
        Q) as required.
        To evaluate the Weil pairing e(P, Q) we run the above algorithm once to compute ƒP(
        Figure US20090034714A9-20090205-P00903
        Q) and once to compute ƒQ(
        Figure US20090034714A9-20090205-P00903
        P). Note that the repeated squaring algorithm needs to evaluate ƒ1(3 Q). This is easily done since the function ƒ1(x, y) (whose divisor is (ƒ1)=(P+R1)−(R1)−(P)+(O)) can be written out explicitly as follows:
      • 1. Let a1x+b1y+c1=0 be the line passing through the points P and R1. Define the function: g1(x, y)=a1x+b1y+c1.
      • 2. Let x+c2=0 be the vertical line passing through the point P+R1. Define the function: g2(x, y)=x+c2.
      • 3. The function ƒ1(x, y) is simply ƒ1(x, y)=g2(x, y)/g1(x, y) which is easy to evaluate in
        Figure US20090034714A9-20090205-P00003
        p 2 .

Claims (20)

1. A method for using identity-based encryption (IBE) to securely convey data over a communications network from a sender to a receiver, comprising:
at the sender, forming an IBE public key using a time element;
at the sender, obtaining IBE system parameters;
at the sender, encrypting the data using the IBE public key and the IBE system parameters;
at the receiver, receiving the encrypted data from the sender;
at the receiver, obtaining an IBE private key that corresponds to the IBE public key; and
at the receiver, decrypting the encrypted data using the IBE private key.
2. The method defined in claim 1 wherein encrypting the data using the IBE public key and the IBE system parameters comprises encrypting the data using the IBE public key, the IBE system parameters, and a bilinear map.
3. The method defined in claim 1 wherein the receiver has identifying information and wherein forming the IBE public key comprises forming the IBE public key using the time element and using the identifying information of the receiver.
4. The method defined in claim 1 wherein the time element includes a date and wherein forming the IBE public key at the sender comprises using the date in forming the IBE public key.
5. The method defined in claim 1 wherein the time element includes a future date and wherein forming the IBE public key at the sender comprises using the future date in forming the IBE public key.
6. The method defined in claim 1 wherein a private key generator is connected to the communications network, the method further comprising:
at the receiver, obtaining the IBE private key from the private key generator over the communications network.
7. A method for using identity-based encryption (IBE) to securely convey data over a communications network from a sender to a receiver, wherein the receiver has a credential, comprising:
at the sender, forming an IBE public key using the credential;
at the sender, obtaining IBE system parameters;
at the sender, encrypting the data using the IBE public key and the IBE system parameters;
at the receiver, receiving the encrypted data from the sender;
at the receiver, obtaining an IBE private key that corresponds to the IBE public key; and
at the receiver, decrypting the encrypted data using the IBE private key.
8. The method defined in claim 7 wherein encrypting the data using the IBE public key and the IBE system parameters comprises encrypting the data using the IBE public key, the IBE system parameters, and a bilinear map.
9. The method defined in claim 7 wherein a private key generator is connected to the communications network, the method further comprising:
at the receiver, obtaining the IBE private key from the private key generator over the communications network.
10. The method defined in claim 7 wherein a private key generator is connected to the communications network, the method further comprising:
at the private key generator, determining whether the receiver has the credential; and
if the private key generator determines that the receiver has the credential, providing the IBE private key to the receiver from the private key generator over the communications network.
11. The method defined in claim 7 wherein the receiver has identifying information and wherein forming the IBE public key comprises forming the IBE public key using the identifying information of the receiver.
12. The method defined in claim 7 wherein the receiver has an identity and wherein a private key generator is connected to the communications network, the method further comprising:
at the private key generator, receiving a request for the IBE private key from the receiver that includes information related to the credential and that includes the identity of the receiver;
at the private key generator, verifying that the credential belongs to the receiver; and
if the credential is verified as belonging to the receiver, providing the requested IBE private key to the receiver from the private key generator.
13. The method defined in claim 7 wherein the credential includes a security clearance and wherein forming the IBE public key comprises forming the IBE public key using the security clearance.
14. The method defined in claim 7 wherein the receiver has identifying information, wherein forming the IBE public key comprises forming the IBE public key using the identifying information of the receiver, and wherein encrypting the data using the IBE public key and the IBE system parameters comprises encrypting the data using the IBE public key, the IBE system parameters, and a bilinear map.
15. The method defined in claim 7 wherein the receiver has identifying information, wherein forming the IBE public key comprises forming the IBE public key using the identifying information of the receiver and a time element, and wherein encrypting the data using the IBE public key and the IBE system parameters comprises encrypting the data using the IBE public key, the IBE system parameters, and a bilinear map.
16. An identity-based cryptographic method comprising:
at a first party, forming an identity-based public key using a time element;
at the first party, performing cryptographic operations using the identity-based public key;
at a second party, obtaining an identity-based private key corresponding to the identity-based public key; and
at the second party, performing cryptographic operations using the identity-based private key.
17. The identity-based cryptographic method defined in claim 16 wherein performing the cryptographic operations using the identity-based public key comprises performing the cryptographic operations using the identity-based public key and a bilinear map.
18. An identity-based cryptographic method comprising:
at a first party, forming an identity-based public key using a credential of a second party;
at the first party, performing cryptographic operations using the identity-based public key;
at a second party, obtaining an identity-based private key corresponding to the identity-based public key; and
at the second party, performing cryptographic operations using the identity-based private key.
19. The identity-based cryptographic method defined in claim 18 wherein performing the cryptographic operations using the identity-based public key comprises performing the cryptographic operations using the identity-based public key and a bilinear map.
20. The identity-based cryptographic method defined in claim 18 further comprising:
at the second party, obtaining the identity-based private key from a private key generator over a communications network.
US11/431,410 2001-08-13 2006-05-09 Systems and methods for identity-based encryption and related cryptographic techniques Expired - Lifetime US7634087B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US11/431,410 US7634087B2 (en) 2001-08-13 2006-05-09 Systems and methods for identity-based encryption and related cryptographic techniques
US12/589,880 US8130964B2 (en) 2001-08-13 2009-10-28 Systems and methods for identity-based encryption and related cryptographic techniques
US13/369,165 US9356779B2 (en) 2001-08-13 2012-02-08 Systems and methods for identity-based encryption and related cryptographic techniques

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US31194601P 2001-08-13 2001-08-13
US10/218,697 US7113594B2 (en) 2001-08-13 2002-08-13 Systems and methods for identity-based encryption and related cryptographic techniques
US11/431,410 US7634087B2 (en) 2001-08-13 2006-05-09 Systems and methods for identity-based encryption and related cryptographic techniques

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US10218691 Continuation 2002-08-13
US10/218,697 Continuation US7113594B2 (en) 2001-08-13 2002-08-13 Systems and methods for identity-based encryption and related cryptographic techniques

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/589,880 Continuation US8130964B2 (en) 2001-08-13 2009-10-28 Systems and methods for identity-based encryption and related cryptographic techniques

Publications (3)

Publication Number Publication Date
US20070041583A1 US20070041583A1 (en) 2007-02-22
US20090034714A9 true US20090034714A9 (en) 2009-02-05
US7634087B2 US7634087B2 (en) 2009-12-15

Family

ID=23209176

Family Applications (4)

Application Number Title Priority Date Filing Date
US10/218,697 Active 2024-12-23 US7113594B2 (en) 2001-08-13 2002-08-13 Systems and methods for identity-based encryption and related cryptographic techniques
US11/431,410 Expired - Lifetime US7634087B2 (en) 2001-08-13 2006-05-09 Systems and methods for identity-based encryption and related cryptographic techniques
US12/589,880 Expired - Lifetime US8130964B2 (en) 2001-08-13 2009-10-28 Systems and methods for identity-based encryption and related cryptographic techniques
US13/369,165 Expired - Lifetime US9356779B2 (en) 2001-08-13 2012-02-08 Systems and methods for identity-based encryption and related cryptographic techniques

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/218,697 Active 2024-12-23 US7113594B2 (en) 2001-08-13 2002-08-13 Systems and methods for identity-based encryption and related cryptographic techniques

Family Applications After (2)

Application Number Title Priority Date Filing Date
US12/589,880 Expired - Lifetime US8130964B2 (en) 2001-08-13 2009-10-28 Systems and methods for identity-based encryption and related cryptographic techniques
US13/369,165 Expired - Lifetime US9356779B2 (en) 2001-08-13 2012-02-08 Systems and methods for identity-based encryption and related cryptographic techniques

Country Status (7)

Country Link
US (4) US7113594B2 (en)
EP (3) EP1425874B1 (en)
JP (4) JP2005500740A (en)
AT (1) ATE465571T1 (en)
AU (1) AU2002332671A1 (en)
DE (1) DE60236094D1 (en)
WO (1) WO2003017559A2 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080091947A1 (en) * 2006-10-17 2008-04-17 Andrew John Dancer Software registration system
US20090006851A1 (en) * 2007-06-29 2009-01-01 Microsoft Corporation Confidential mail with tracking and authentication
US20090030778A1 (en) * 2007-07-23 2009-01-29 Motivepath, Inc. System, method and apparatus for secure multiparty location based services
US20090257594A1 (en) * 2008-04-15 2009-10-15 Amjad Qureshi Secure debug interface and memory of a media security circuit and method
US20090319769A1 (en) * 2008-05-21 2009-12-24 Apple Inc. Discrete key generation method and apparatus
US20100104094A1 (en) * 2007-01-19 2010-04-29 Mitsubishi Electric Corporation Ciphertext generating apparatus, cryptographic communication system, and group parameter generating apparatus
US20100119058A1 (en) * 2008-11-11 2010-05-13 Seiichi Matsuda Information processing apparatus, information processing method, and program
US8166203B1 (en) * 2009-05-29 2012-04-24 Google Inc. Server selection based upon time and query dependent hashing
US20120233465A1 (en) * 2007-04-05 2012-09-13 International Business Machines Corporation Distribution of Credentials
US20120254616A1 (en) * 2011-04-01 2012-10-04 Certicom Corporation Identity-Based Decryption
US20130322620A1 (en) * 2012-05-31 2013-12-05 Samsung Sds Co., Ltd. Apparatus and method for generating secret key for id-based encryption system and recording medium having program recorded thereon for causing computer to execute the method
US20150120650A1 (en) * 2013-10-30 2015-04-30 Gordon E. Seay Methods and Systems for Utilizing Global Entities In Software Applications
US20160301531A1 (en) * 2015-04-09 2016-10-13 Qualcomm Incorporated Proof of work based user identification system

Families Citing this family (392)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10114157A1 (en) * 2001-03-22 2002-09-26 Deutsche Telekom Ag Computer-aided encryption key generation method provides public encryption key with common first part and second part specific to each receiver
US7564970B2 (en) * 2004-08-12 2009-07-21 Cmla, Llc Exponential data transform to enhance security
US7577250B2 (en) 2004-08-12 2009-08-18 Cmla, Llc Key derivation functions to enhance security
US8077861B2 (en) 2004-08-12 2011-12-13 Cmla, Llc Permutation data transform to enhance security
WO2003017559A2 (en) * 2001-08-13 2003-02-27 Board Of Trustees Of The Leland Stanford Junior University Systems and methods for identity-based encryption and related cryptographic techniques
JP3901484B2 (en) * 2001-10-05 2007-04-04 株式会社ジェイテクト Electric power steering device
GB0124681D0 (en) * 2001-10-15 2001-12-05 Hewlett Packard Co Method and apparatus for encrypting data
US7921284B1 (en) 2001-12-12 2011-04-05 Gary Mark Kinghorn Method and system for protecting electronic data in enterprise environment
US7930756B1 (en) 2001-12-12 2011-04-19 Crocker Steven Toye Multi-level cryptographic transformations for securing digital assets
US8006280B1 (en) 2001-12-12 2011-08-23 Hildebrand Hal S Security system for generating keys from access rules in a decentralized manner and methods therefor
US7921450B1 (en) * 2001-12-12 2011-04-05 Klimenty Vainstein Security system using indirect key generation from access rules and methods therefor
US7260555B2 (en) 2001-12-12 2007-08-21 Guardian Data Storage, Llc Method and architecture for providing pervasive security to digital assets
US10360545B2 (en) 2001-12-12 2019-07-23 Guardian Data Storage, Llc Method and apparatus for accessing secured electronic data off-line
US7921288B1 (en) 2001-12-12 2011-04-05 Hildebrand Hal S System and method for providing different levels of key security for controlling access to secured items
US7178033B1 (en) 2001-12-12 2007-02-13 Pss Systems, Inc. Method and apparatus for securing digital assets
US7565683B1 (en) 2001-12-12 2009-07-21 Weiqing Huang Method and system for implementing changes to security policies in a distributed security system
US7380120B1 (en) 2001-12-12 2008-05-27 Guardian Data Storage, Llc Secured data format for access control
US8065713B1 (en) 2001-12-12 2011-11-22 Klimenty Vainstein System and method for providing multi-location access management to secured items
US10033700B2 (en) 2001-12-12 2018-07-24 Intellectual Ventures I Llc Dynamic evaluation of access rights
US7950066B1 (en) 2001-12-21 2011-05-24 Guardian Data Storage, Llc Method and system for restricting use of a clipboard application
US8176334B2 (en) 2002-09-30 2012-05-08 Guardian Data Storage, Llc Document security system that permits external users to gain access to secured files
US7349538B2 (en) * 2002-03-21 2008-03-25 Ntt Docomo Inc. Hierarchical identity-based encryption and signature schemes
EP2375628A2 (en) * 2002-04-15 2011-10-12 NTT DoCoMo, Inc. Signature schemes using bilinear mappings
GB0208858D0 (en) * 2002-04-18 2002-05-29 Hewlett Packard Co Method and apparatus for encrypting/decrypting data
GB2390703A (en) * 2002-07-02 2004-01-14 Ascent Group Ltd Storage and authentication of data transactions
GB0215524D0 (en) * 2002-07-05 2002-08-14 Hewlett Packard Co Method and apparatus for generating a cryptographic key
US20050089173A1 (en) * 2002-07-05 2005-04-28 Harrison Keith A. Trusted authority for identifier-based cryptography
GB0215590D0 (en) * 2002-07-05 2002-08-14 Hewlett Packard Co Method and apparatus for generating a cryptographic key
GB2401763B (en) * 2002-07-05 2005-08-10 Hewlett Packard Development Co Trusted authority for identifer-based cryptography
SG145524A1 (en) * 2002-08-07 2008-09-29 Mobilastic Technologies Pte Lt Secure transfer of digital tokens
US20040044734A1 (en) * 2002-08-27 2004-03-04 Mark Beck Enhanced services electronic mail
US7657748B2 (en) * 2002-08-28 2010-02-02 Ntt Docomo, Inc. Certificate-based encryption and public key infrastructure
KR100489327B1 (en) * 2002-09-18 2005-05-12 학교법인 한국정보통신학원 Identification scheme based on the bilinear diffie-hellman problem
US7486795B2 (en) * 2002-09-20 2009-02-03 University Of Maryland Method and apparatus for key management in distributed sensor networks
US7412059B1 (en) 2002-11-27 2008-08-12 Voltage Security, Inc. Public-key encryption system
KR20030008182A (en) * 2002-12-24 2003-01-24 학교법인 한국정보통신학원 Method of id-based blind signature by using bilinear parings
KR20030008183A (en) * 2002-12-24 2003-01-24 학교법인 한국정보통신학원 Method of id-based ring signature by using bilinear parings
CN1736055B (en) * 2003-01-07 2010-10-13 高通股份有限公司 System, apparatus and method for replacing a cryptographic key
US7003117B2 (en) * 2003-02-05 2006-02-21 Voltage Security, Inc. Identity-based encryption system for secure data distribution
US7480384B2 (en) * 2003-02-10 2009-01-20 International Business Machines Corporation Method for distributing and authenticating public keys using random numbers and Diffie-Hellman public keys
US8108678B1 (en) * 2003-02-10 2012-01-31 Voltage Security, Inc. Identity-based signcryption system
US7783044B2 (en) * 2003-02-20 2010-08-24 Proofpoint, Inc. System for on-line and off-line decryption
GB2398713B (en) * 2003-02-22 2005-11-30 Hewlett Packard Development Co Limiting service provision to group members
US7571321B2 (en) * 2003-03-14 2009-08-04 Voltage Security, Inc. Identity-based-encryption messaging system
KR100507809B1 (en) * 2003-03-19 2005-08-17 학교법인 한국정보통신학원 Anonymous fingerprinting scheme based on the bilinear pairings diffie-hellman problem
US7921292B1 (en) 2003-04-04 2011-04-05 Voltage Security, Inc. Secure messaging systems
GB2400699B (en) * 2003-04-17 2006-07-05 Hewlett Packard Development Co Security data provision method and apparatus and data recovery method and system
GB0309161D0 (en) * 2003-04-23 2003-05-28 Hewlett Packard Development Co Cryptographic method and apparatus
GB2401006A (en) * 2003-04-23 2004-10-27 Hewlett Packard Development Co Cryptographic method and apparatus
DE602004001273T2 (en) * 2003-04-23 2007-05-31 Hewlett-Packard Development Co., L.P., Houston Method and device for identification-based encryption
GB0309182D0 (en) 2003-04-23 2003-05-28 Hewlett Packard Development Co Security method and apparatus using biometric data
JP2006524352A (en) * 2003-04-23 2006-10-26 ヒューレット−パッカード デベロップメント カンパニー エル.ピー. Identity-based encryption method and apparatus based on biometrics
US7380138B2 (en) 2003-04-23 2008-05-27 Hewlett-Packard Development Company, L.P. Cryptographic method and apparatus
GB2401013B (en) * 2003-04-23 2005-09-28 Hewlett Packard Development Co Cryptographic method and apparatus
AU2004201807A1 (en) * 2003-05-09 2004-11-25 Nor Azman Bin Abu Method and apparatus for the generation of public key based on a user-defined ID in a cryptosystem
US8707034B1 (en) 2003-05-30 2014-04-22 Intellectual Ventures I Llc Method and system for using remote headers to secure electronic files
GB0313663D0 (en) * 2003-06-13 2003-07-16 Hewlett Packard Development Co Mediated rsa cryptographic method and system
GB0313666D0 (en) 2003-06-13 2003-07-16 Hewlett Packard Development Co RSA cryptographic method and system
US7580521B1 (en) * 2003-06-25 2009-08-25 Voltage Security, Inc. Identity-based-encryption system with hidden public key attributes
US7017181B2 (en) * 2003-06-25 2006-03-21 Voltage Security, Inc. Identity-based-encryption messaging system with public parameter host servers
DE10330089B4 (en) * 2003-07-03 2014-02-27 Bt Ignite Gmbh & Co. Method and apparatus for transmitting decryption codes for freely transmitted, encrypted program content to uniquely identifiable recipients
KR20030062401A (en) * 2003-07-04 2003-07-25 학교법인 한국정보통신학원 Apparatus and method for generating and verifying id-based blind signature by using bilinear parings
US7769167B2 (en) * 2003-07-25 2010-08-03 Microsoft Corporation Weil and Tate pairing techniques using parabolas
US7298839B2 (en) * 2003-07-25 2007-11-20 Microsoft Corporation Squared Weil and Tate pairing techniques for use with elliptic curves
US7440569B2 (en) * 2003-07-28 2008-10-21 Microsoft Corporation Tate pairing techniques for use with hyperelliptic curves
US7266847B2 (en) * 2003-09-25 2007-09-04 Voltage Security, Inc. Secure message system with remote decryption service
EP1519530A1 (en) * 2003-09-29 2005-03-30 STMicroelectronics S.r.l. Method for establishing an encrypted communication by means of keys
US8127366B2 (en) 2003-09-30 2012-02-28 Guardian Data Storage, Llc Method and apparatus for transitioning between states of security policies used to secure electronic documents
US7703140B2 (en) 2003-09-30 2010-04-20 Guardian Data Storage, Llc Method and system for securing digital assets using process-driven security policies
US7979911B2 (en) * 2003-10-08 2011-07-12 Microsoft Corporation First computer process and second computer process proxy-executing code from third computer process on behalf of first process
US7788496B2 (en) * 2003-10-08 2010-08-31 Microsoft Corporation First computer process and second computer process proxy-executing code on behalf thereof
US8103592B2 (en) * 2003-10-08 2012-01-24 Microsoft Corporation First computer process and second computer process proxy-executing code on behalf of first process
US7596704B2 (en) * 2003-10-10 2009-09-29 Jing-Jang Hwang Partition and recovery of a verifiable digital secret
US7487537B2 (en) * 2003-10-14 2009-02-03 International Business Machines Corporation Method and apparatus for pervasive authentication domains
US7103911B2 (en) * 2003-10-17 2006-09-05 Voltage Security, Inc. Identity-based-encryption system with district policy information
EP1687931B1 (en) 2003-10-28 2021-12-29 BlackBerry Limited Method and apparatus for verifiable generation of public keys
US20050135610A1 (en) * 2003-11-01 2005-06-23 Liqun Chen Identifier-based signcryption
GB0325527D0 (en) * 2003-11-01 2003-12-03 Hewlett Packard Development Co Identifier-based signcryption
US7499544B2 (en) 2003-11-03 2009-03-03 Microsoft Corporation Use of isogenies for design of cryptosystems
US7523314B2 (en) 2003-12-22 2009-04-21 Voltage Security, Inc. Identity-based-encryption message management system
US20050187863A1 (en) * 2004-02-20 2005-08-25 Whinery Christopher S. Method and system for protecting real estate from fraudulent transactions
WO2005096545A1 (en) * 2004-03-30 2005-10-13 Dublin City University Verification of identity based signatures
US7646872B2 (en) 2004-04-02 2010-01-12 Research In Motion Limited Systems and methods to securely generate shared keys
US8050409B2 (en) * 2004-04-02 2011-11-01 University Of Cincinnati Threshold and identity-based key management and authentication for wireless ad hoc networks
US7590236B1 (en) * 2004-06-04 2009-09-15 Voltage Security, Inc. Identity-based-encryption system
GB2415112B (en) 2004-06-11 2007-04-25 Hewlett Packard Development Co Cryptographic method and apparatus
KR100657265B1 (en) 2004-06-23 2006-12-14 삼성전자주식회사 Self-enforcing method and method for transmitting and receiving contents using the same
GB2415579B (en) 2004-06-23 2006-12-20 Hewlett Packard Development Co Cryptographic method and apparatus
US20060013397A1 (en) * 2004-07-13 2006-01-19 International Business Machines Corporation Channel adapter managed trusted queue pairs
GB2416282B (en) 2004-07-15 2007-05-16 Hewlett Packard Development Co Identifier-based signcryption with two trusted authorities
US7920050B2 (en) * 2004-07-29 2011-04-05 Emc Corporation Proxy device for enhanced privacy in an RFID system
EP1621956B1 (en) * 2004-07-30 2017-05-31 Irdeto B.V. Method of providing rights data objects
KR101328618B1 (en) 2004-08-12 2013-11-13 씨엠엘에이 엘엘씨 Permutation Data Transformation to Enhance Security
US7742596B2 (en) * 2004-08-24 2010-06-22 General Dynamics C4 Systems, Inc. Reliable elliptic curve cryptography computation
WO2006034428A2 (en) * 2004-09-20 2006-03-30 Pgp Corporation Apparatus and method for identity-based encryption within a conventional public-key infrastructure
JP4752313B2 (en) * 2004-09-30 2011-08-17 ソニー株式会社 Cryptographic processing operation method, cryptographic processing apparatus, and computer program
US20060078790A1 (en) * 2004-10-05 2006-04-13 Polyplus Battery Company Solid electrolytes based on lithium hafnium phosphate for active metal anode protection
KR100601706B1 (en) * 2004-10-15 2006-07-18 삼성전자주식회사 Method and apparatus for sharing and generating system key in DRM
US7418100B2 (en) * 2004-10-20 2008-08-26 Cisco Technology, Inc. Enciphering method
GB2419787B (en) * 2004-10-28 2007-07-04 Hewlett Packard Development Co Method and apparatus for providing short-term private keys in public-key cryptographic systems
US7660987B2 (en) * 2004-10-29 2010-02-09 Baylis Stephen W Method of establishing a secure e-mail transmission link
US7370202B2 (en) * 2004-11-02 2008-05-06 Voltage Security, Inc. Security device for cryptographic communications
FR2877453A1 (en) * 2004-11-04 2006-05-05 France Telecom SECURE DELEGATION METHOD OF CALCULATING A BILINE APPLICATION
ATE546909T1 (en) 2004-11-11 2012-03-15 Certicom Corp NEW TRAPDOOR ONE-WAY FUNCTION ON ELLIPTICAL CURVES AND ITS APPLICATION FOR ASYMMETRIC ENCRYPTION AND SHORTER SIGNATURES
EP1813051B1 (en) * 2004-11-12 2017-09-13 Dublin City University Identity based encryption
JP4546231B2 (en) * 2004-12-09 2010-09-15 株式会社日立製作所 ID-based signature and encryption system and method
GB2421097B (en) * 2004-12-10 2009-07-01 Hewlett Packard Development Co Methods, devices and computer programs for creating ciphertext, plaintext and a cryptographic key
US7639799B2 (en) * 2004-12-14 2009-12-29 Microsoft Corporation Cryptographically processing data based on a Cassels-Tate pairing
DE602005010039D1 (en) 2004-12-23 2008-11-13 Hewlett Packard Development Co Improvements in the application of bilinear mappings in cryptographic applications
JP4528114B2 (en) * 2004-12-28 2010-08-18 日本電信電話株式会社 Key generation device, encryption device, inspection device, decryption device, key generation program, encryption program, inspection program, decryption program
US8099598B1 (en) * 2005-01-03 2012-01-17 Gary Gang Liu Secure messaging system with automatic recipient enrollment
US7869593B2 (en) * 2005-01-07 2011-01-11 First Data Corporation Software for providing based on shared knowledge public keys having same private key
CN1262087C (en) * 2005-01-14 2006-06-28 南相浩 Method and apparatus for cipher key generation based on identification
US20060159269A1 (en) * 2005-01-20 2006-07-20 Matsushita Electric Industrial Co., Ltd. Cryptographic system for resource starved CE device secure upgrade and re-configuration
US8396213B2 (en) 2005-01-21 2013-03-12 Certicom Corp. Elliptic curve random number generation
US7860802B2 (en) * 2005-02-01 2010-12-28 Microsoft Corporation Flexible licensing architecture in content rights management systems
US7594261B2 (en) * 2005-02-08 2009-09-22 Microsoft Corporation Cryptographic applications of the Cartier pairing
MX2007010388A (en) 2005-02-25 2007-10-18 Qualcomm Inc Small public-key based digital signatures for authentication.
US7822200B2 (en) * 2005-03-07 2010-10-26 Microsoft Corporation Method and system for asymmetric key security
US7739500B2 (en) * 2005-03-07 2010-06-15 Microsoft Corporation Method and system for consistent recognition of ongoing digital relationships
US7680268B2 (en) 2005-03-15 2010-03-16 Microsoft Corporation Elliptic curve point octupling using single instruction multiple data processing
US7702098B2 (en) * 2005-03-15 2010-04-20 Microsoft Corporation Elliptic curve point octupling for weighted projective coordinates
US7657456B2 (en) * 2005-03-18 2010-02-02 Pitney Bowes Inc. Method and system for electronic voting using identity based encryption
US7634085B1 (en) * 2005-03-25 2009-12-15 Voltage Security, Inc. Identity-based-encryption system with partial attribute matching
US8285996B2 (en) 2005-03-30 2012-10-09 Dublin City University Verification of identity based signatures
US20060238302A1 (en) * 2005-04-21 2006-10-26 Sean Loving System and method for configuring an RFID reader
US20060238304A1 (en) * 2005-04-21 2006-10-26 Sean Loving System and method for adapting an FRID tag reader to its environment
US20060238305A1 (en) * 2005-04-21 2006-10-26 Sean Loving Configurable RFID reader
US20060253415A1 (en) * 2005-04-21 2006-11-09 Sayan Chakraborty Data-defined communication device
US7659819B2 (en) 2005-04-21 2010-02-09 Skyetek, Inc. RFID reader operating system and associated architecture
US20070046431A1 (en) * 2005-08-31 2007-03-01 Skyetek, Inc. System and method for combining RFID tag memory
US7570164B2 (en) * 2005-12-30 2009-08-04 Skyetek, Inc. System and method for implementing virtual RFID tags
US20060238303A1 (en) * 2005-04-21 2006-10-26 Sean Loving Adaptable RFID reader
US20070046467A1 (en) * 2005-08-31 2007-03-01 Sayan Chakraborty System and method for RFID reader to reader communication
US8091142B2 (en) * 2005-04-26 2012-01-03 Microsoft Corporation Supplementary trust model for software licensing/commercial digital distribution policy
KR100635280B1 (en) * 2005-04-27 2006-10-19 삼성전자주식회사 Security method using electronic signature
JP4646691B2 (en) * 2005-05-10 2011-03-09 株式会社エヌ・ティ・ティ・データ Encrypted communication system, secret key issuing device, and program
US7720221B2 (en) * 2005-05-20 2010-05-18 Certicom Corp. Privacy-enhanced e-passport authentication protocol
JP4723909B2 (en) * 2005-05-27 2011-07-13 株式会社日立製作所 Data exchange method, data exchange management device, and data exchange management program
US7649999B2 (en) * 2005-06-08 2010-01-19 Iris Anshel Method and apparatus for establishing a key agreement protocol
US8356175B2 (en) * 2005-06-29 2013-01-15 Intel Corporation Methods and apparatus to perform associated security protocol extensions
US8477940B2 (en) * 2005-07-15 2013-07-02 Tyfone, Inc. Symmetric cryptography with user authentication
US8189788B2 (en) * 2005-07-15 2012-05-29 Tyfone, Inc. Hybrid symmetric/asymmetric cryptography with user authentication
US7627760B2 (en) * 2005-07-21 2009-12-01 Microsoft Corporation Extended authenticated key exchange
JP2007036364A (en) * 2005-07-22 2007-02-08 Nec Corp Time device, encrypting device, decrypting device, and encrypting/decrypting system
US7694141B2 (en) 2005-07-26 2010-04-06 Microsoft Corporation Extended authenticated key exchange with key confirmation
US8190895B2 (en) * 2005-08-18 2012-05-29 Microsoft Corporation Authenticated key exchange with derived ephemeral keys
US7908482B2 (en) * 2005-08-18 2011-03-15 Microsoft Corporation Key confirmed authenticated key exchange with derived ephemeral keys
FR2890201A1 (en) * 2005-08-31 2007-03-02 Proton World Internatinal Nv Digital data e.g. music files, storing method for e.g. digital floppy disk, involves encrypting digital data using symmetric algorithm with encryption key independent to recorder, and transferring key onto physical medium or microcircuit
US20070206786A1 (en) * 2005-08-31 2007-09-06 Skyetek, Inc. Rfid security system
FR2892251A1 (en) * 2005-10-14 2007-04-20 Gemplus Sa CRYPTOGRAPHIC METHOD IMPLEMENTING AN IDENTITY-BASED ENCRYPTION SYSTEM
US20070104323A1 (en) * 2005-11-04 2007-05-10 Pitney Bowes Incorporated Method and system for providing privacy to sender of a mail piece
WO2007063876A1 (en) * 2005-12-01 2007-06-07 Nec Corporation Electronic bidding system and electronic bidding method
US9165411B2 (en) * 2005-12-16 2015-10-20 Pitney Bowes Inc. Method and system for embedding mailer specified mailing instructions on a mail piece to automate mail processing
US20080022160A1 (en) * 2005-12-30 2008-01-24 Skyetek, Inc. Malware scanner for rfid tags
US20070206797A1 (en) * 2006-03-01 2007-09-06 Skyetek, Inc. Seamless rfid tag security system
JP4688886B2 (en) * 2006-01-11 2011-05-25 三菱電機株式会社 Elliptic curve encryption parameter generation apparatus, elliptic curve encryption system, and elliptic curve encryption parameter generation program
US8180047B2 (en) * 2006-01-13 2012-05-15 Microsoft Corporation Trapdoor pairings
US8094810B2 (en) * 2006-02-03 2012-01-10 Massachusetts Institute Of Technology Unidirectional proxy re-encryption
US9137012B2 (en) 2006-02-03 2015-09-15 Emc Corporation Wireless authentication methods and apparatus
GB2436910B (en) * 2006-04-03 2011-02-16 Identum Ltd Electronic Data Communication System
US8311214B2 (en) * 2006-04-24 2012-11-13 Motorola Mobility Llc Method for elliptic curve public key cryptographic validation
US9002018B2 (en) * 2006-05-09 2015-04-07 Sync Up Technologies Corporation Encryption key exchange system and method
US7434726B2 (en) * 2006-05-15 2008-10-14 Pitney Bowes Inc. Method and system for postdating of financial transactions
FR2901940B1 (en) * 2006-05-31 2012-12-14 Oberthur Card Syst Sa METHOD OF GENERATING A PRIVATE KEY AND METHODS OF ENCRYPTING AND DE-CREATING A MESSAGE
EP2022207B1 (en) * 2006-05-31 2018-10-10 Orange Cryptographic method with integrated encryption and revocation, system, device and programs for implementing this method
US9769158B2 (en) * 2006-06-07 2017-09-19 Red Hat, Inc. Guided enrollment and login for token users
JP4868131B2 (en) * 2006-06-15 2012-02-01 ネッツエスアイ東洋株式会社 Electronic tally verification system
JP4556917B2 (en) * 2006-06-22 2010-10-06 日本電気株式会社 Determination system, determination method, determination apparatus, and program
US8670564B1 (en) 2006-08-14 2014-03-11 Key Holdings, LLC Data encryption system and method
EP1890493A1 (en) * 2006-08-17 2008-02-20 Nagracard S.A. Method for revocating security modules used to secure broadcast messages
JP5144991B2 (en) * 2006-08-22 2013-02-13 株式会社エヌ・ティ・ティ・データ Ciphertext decryption authority delegation system
US20080065729A1 (en) * 2006-09-08 2008-03-13 Pitney Bowes Incorporated Method and system for service provider to be compensated for delivering e-mail messages while reducing amount of unsolicited e-mail messages
US7885406B2 (en) * 2006-10-10 2011-02-08 Microsoft Corporation Computing endomorphism rings of Abelian surfaces over finite fields
US20080137859A1 (en) * 2006-12-06 2008-06-12 Ramanathan Jagadeesan Public key passing
JP2008152737A (en) * 2006-12-20 2008-07-03 Nippon Telegr & Teleph Corp <Ntt> Service provision server, authentication server, and authentication system
GB0705494D0 (en) * 2007-03-22 2007-05-02 Ibm A method and system for a subscription to a symmetric key
US7859411B2 (en) 2007-03-30 2010-12-28 Skyetek, Inc. RFID tagged item trajectory and location estimation system and method
US20080297326A1 (en) * 2007-03-30 2008-12-04 Skyetek, Inc. Low Cost RFID Tag Security And Privacy System And Method
US20080290995A1 (en) * 2007-03-30 2008-11-27 Skyetek, Inc. System and method for optimizing communication between an rfid reader and an rfid tag
US8669845B1 (en) 2007-03-30 2014-03-11 Vail Resorts, Inc. RFID skier monitoring systems and methods
CN101652956B (en) * 2007-04-05 2013-08-21 皇家飞利浦电子股份有限公司 Wireless sensor network key distribution
JP2008301391A (en) * 2007-06-04 2008-12-11 Murata Mach Ltd Broadcasting encryption system, encryption communication method, decoder and decoding program
US8676715B2 (en) 2007-06-06 2014-03-18 Pitney Bowes Inc. System and method for authenticating indicia using identity-based signature scheme
US8631419B2 (en) * 2007-06-29 2014-01-14 Microsoft Corporation System and methods for disruption detection, management, and recovery
DE102007033846A1 (en) 2007-07-18 2009-01-22 Freisleben, Bernd, Prof. Dr. Cryptographic key generating method for encrypted digital communication between communication devices, involves converting end product address of communication device into part of key, and utilizing address for key agreement
DE102007033847A1 (en) 2007-07-18 2009-01-22 Bernd Prof. Dr. Freisleben Method for cryptographic key agreement between two communication devices in Internet protocol communications networks, involves arranging one or multiple Network address translation routers between two communication devices
DE102007033845A1 (en) 2007-07-18 2009-01-22 Bernd Prof. Dr. Freisleben Public/private cryptographic key producing method for executing key agreement in digital data carrier, involves converting terminal end point address into key portion by applying inverse function of trap door one-way function for agreement
DE102007033848A1 (en) 2007-07-18 2009-01-22 Freisleben, Bernd, Prof. Dr. Method for verification of ownership of terminal address of communications device in network, involves verifying ownership of terminal address by communications device belonging to it, by private cryptographic key
KR101490687B1 (en) * 2007-08-20 2015-02-06 삼성전자주식회사 Method and apparatus for sharing secret information between devices in home network
US7890763B1 (en) * 2007-09-14 2011-02-15 The United States Of America As Represented By The Director, National Security Agency Method of identifying invalid digital signatures involving batch verification
US8700894B2 (en) * 2007-10-17 2014-04-15 Pitney Bowes Inc. Method and system for securing routing information of a communication using identity-based encryption scheme
EP2217995A4 (en) * 2007-10-26 2012-11-21 Telcordia Tech Inc Method and system for secure session establishment using identity-based encryption (vdtls)
JP5286748B2 (en) * 2007-11-09 2013-09-11 ソニー株式会社 Information processing apparatus, key setting method, and program
CN101179380A (en) * 2007-11-19 2008-05-14 上海交通大学 Bidirectional authentication method, system and network terminal
JP4907502B2 (en) * 2007-11-20 2012-03-28 日本電信電話株式会社 Action certificate issuing method, action certificate issuing device, action certificate issuing program, and action certificate issuing / verifying system
KR20090052199A (en) * 2007-11-20 2009-05-25 삼성전자주식회사 Storage device, terminal device using the storage device, and, method thereof
JP5365072B2 (en) * 2007-12-11 2013-12-11 ソニー株式会社 KEY GENERATION DEVICE, ENCRYPTION DEVICE, RECEPTION DEVICE, KEY GENERATION METHOD, ENCRYPTION METHOD, KEY PROCESSING METHOD, AND PROGRAM
US20090153290A1 (en) * 2007-12-14 2009-06-18 Farpointe Data, Inc., A California Corporation Secure interface for access control systems
KR20100133953A (en) * 2007-12-21 2010-12-22 코쿤 데이터 홀딩스 리미티드 System and method for securing data
CN101521569B (en) * 2008-02-28 2013-04-24 华为技术有限公司 Method, equipment and system for realizing service access
KR101484110B1 (en) * 2008-02-29 2015-01-28 삼성전자주식회사 Memory controller and memory device thereof
BRPI0908621A2 (en) * 2008-05-23 2016-06-14 Koninkl Philips Electronics Nv encryption method of a data item that has an identifier to identify the data item, decryption method of an encrypted data item, computer program product, computer system, digital rights management method drm
US8259949B2 (en) * 2008-05-27 2012-09-04 Intel Corporation Methods and apparatus for protecting digital content
JP5118556B2 (en) * 2008-06-04 2013-01-16 日本電信電話株式会社 Key distribution method, key distribution system, client device, key server device, and program thereof
JP5027742B2 (en) * 2008-06-19 2012-09-19 日本電信電話株式会社 Secret information transmission system, secret information transmission method, secret information management server, encryption device, secret information transmission program
US8656177B2 (en) * 2008-06-23 2014-02-18 Voltage Security, Inc. Identity-based-encryption system
US8761390B2 (en) * 2008-06-30 2014-06-24 Gm Global Technology Operations Production of cryptographic keys for an embedded processing device
US8737614B1 (en) * 2008-07-07 2014-05-27 Voltage Security, Inc. Document imaging system with identity-based encryption
CN101350060B (en) * 2008-07-23 2011-06-01 西安西电捷通无线网络通信股份有限公司 Data safety access method being suitable for electronic label
US8108777B2 (en) 2008-08-11 2012-01-31 Microsoft Corporation Sections of a presentation having user-definable properties
EP2316180A4 (en) 2008-08-11 2011-12-28 Assa Abloy Ab Secure wiegand communications
EP2157526B1 (en) * 2008-08-14 2014-04-30 Assa Abloy Ab RFID reader with embedded attack detection heuristics
US7995765B2 (en) * 2008-08-28 2011-08-09 Red Hat, Inc. Sharing a secret using hyperplanes over GF(q)
US8520854B2 (en) * 2008-08-28 2013-08-27 Red Hat, Inc. Sharing a secret using polynomials over polynomials
US7995764B2 (en) * 2008-08-28 2011-08-09 Red Hat, Inc. Sharing a secret using hyperplanes over GF(2m)
US8675877B2 (en) * 2008-08-29 2014-03-18 Red Hat, Inc. Sharing a secret via linear interpolation
US8559637B2 (en) 2008-09-10 2013-10-15 Verizon Patent And Licensing Inc. Securing information exchanged via a network
JP5491015B2 (en) * 2008-09-25 2014-05-14 Kddi株式会社 Mediation apparatus and program for setting wireless communication channel
JP5580318B2 (en) * 2008-10-14 2014-08-27 コーニンクレッカ フィリップス エヌ ヴェ Method and apparatus for kana generation and authentication
CN101420303B (en) * 2008-12-12 2011-02-02 广州杰赛科技股份有限公司 Communication method for audio data and apparatus thereof
JP5097102B2 (en) * 2008-12-25 2012-12-12 日本電信電話株式会社 Hierarchical ID-based encryption device and decryption device, method thereof, program, and recording medium
JP5134555B2 (en) * 2009-01-07 2013-01-30 日本電信電話株式会社 Key generation device, encryption device, decryption device, encryption system, key generation method, encryption method, decryption method, program, and recording medium
JP5268066B2 (en) * 2009-01-16 2013-08-21 日本電信電話株式会社 Conversion operation device, method, program, and recording medium
US8341427B2 (en) * 2009-02-16 2012-12-25 Microsoft Corporation Trusted cloud computing and services framework
US9165154B2 (en) * 2009-02-16 2015-10-20 Microsoft Technology Licensing, Llc Trusted cloud computing and services framework
US8510558B2 (en) 2009-02-17 2013-08-13 Alcatel Lucent Identity based authenticated key agreement protocol
EP2222015A1 (en) * 2009-02-19 2010-08-25 Thomson Licensing Method and device for hashing onto points of an elliptic curve
US8837718B2 (en) * 2009-03-27 2014-09-16 Microsoft Corporation User-specified sharing of data via policy and/or inference from a hierarchical cryptographic store
US9704159B2 (en) * 2009-05-15 2017-07-11 Entit Software Llc Purchase transaction system with encrypted transaction information
US8571995B2 (en) 2009-06-02 2013-10-29 Voltage Security, Inc. Purchase transaction system with encrypted payment card data
EP2456118A4 (en) * 2009-07-17 2013-05-01 Alcatel Lucent Digital rights management (drm) method and equipment in small and medium enterprise (sme) and method for providing drm service
US8850203B2 (en) 2009-08-28 2014-09-30 Alcatel Lucent Secure key management in multimedia communication system
US8301883B2 (en) * 2009-08-28 2012-10-30 Alcatel Lucent Secure key management in conferencing system
US8510835B1 (en) 2009-09-18 2013-08-13 Trend Micro Incorporated Techniques for protecting data in cloud computing environments
US8826013B1 (en) 2009-09-23 2014-09-02 Trend Micro Incorporated Protection of customer data in cloud virtual machines using a central management server
US8219792B2 (en) * 2009-10-06 2012-07-10 Dell Products L.P. System and method for safe information handling system boot
JP4802274B2 (en) * 2009-10-30 2011-10-26 インターナショナル・ビジネス・マシーンズ・コーポレーション How to send and receive messages
US8666812B1 (en) * 2009-11-10 2014-03-04 Google Inc. Distributing content based on transaction information
US8219810B2 (en) * 2009-11-13 2012-07-10 Palo Alto Research Center Incorporated Method and system for facilitating throttling of interpolation-based authentication
JP5325755B2 (en) * 2009-12-11 2013-10-23 株式会社エヌ・ティ・ティ・データ Ciphertext decryption authority delegation system, ciphertext decryption authority delegation method, ciphertext conversion apparatus, decryption authority holder apparatus, and ciphertext conversion program
EP2348449A3 (en) * 2009-12-18 2013-07-10 CompuGroup Medical AG A computer implemented method for performing cloud computing on data being stored pseudonymously in a database
EP2348452B1 (en) 2009-12-18 2014-07-02 CompuGroup Medical AG A computer implemented method for sending a message to a recipient user, receiving a message by a recipient user, a computer readable storage medium and a computer system
EP2348447B1 (en) 2009-12-18 2014-07-16 CompuGroup Medical AG A computer implemented method for generating a set of identifiers from a private key, computer implemented method and computing device
WO2011086668A1 (en) * 2010-01-13 2011-07-21 三菱電機株式会社 Secret retrieval system, public parameter generation device, encryption device, user secret key generation device, query issue device, retrieval device, computer program, secret retrieval method, public parameter generation method, encryption method, user secret key generation method, query issue method, and retrieval method
US8615668B2 (en) 2010-01-15 2013-12-24 Mitsubishi Electric Corporation Confidential search system and cryptographic processing system
US8488783B2 (en) * 2010-02-19 2013-07-16 Nokia Method and apparatus for applying recipient criteria in identity-based encryption
ES2524075T3 (en) * 2010-03-03 2014-12-04 Nagravision S.A. Method to manage revocation in a group of terminals
EP2365456B1 (en) 2010-03-11 2016-07-20 CompuGroup Medical SE Data structure, method and system for predicting medical conditions
US9025767B2 (en) * 2010-03-24 2015-05-05 Nokia Corporation Method and apparatus for querying content protected by identity-based encryption
US8553878B2 (en) * 2010-04-14 2013-10-08 Apple Inc. Data transformation system using cyclic groups
US9772834B2 (en) * 2010-04-27 2017-09-26 Red Hat, Inc. Exportable encoded identifications of networked machines
JP5424974B2 (en) * 2010-04-27 2014-02-26 三菱電機株式会社 Cryptographic processing system, key generation device, encryption device, decryption device, signature processing system, signature device, and verification device
US8423764B2 (en) 2010-06-23 2013-04-16 Motorola Solutions, Inc. Method and apparatus for key revocation in an attribute-based encryption scheme
RU2452111C1 (en) * 2010-11-17 2012-05-27 ЗАО Институт инфокоммуникационных технологий Method for threshold key generating for protection system based on identity data
US8621227B2 (en) 2010-12-28 2013-12-31 Authernative, Inc. System and method for cryptographic key exchange using matrices
US8656484B2 (en) 2010-12-28 2014-02-18 Authernative, Inc. System and method for mutually authenticated cryptographic key exchange using matrices
JP5612494B2 (en) * 2011-01-21 2014-10-22 日本電信電話株式会社 Timed cryptographic system, timed cryptographic method, apparatus, and program using function encryption
US20130042112A1 (en) * 2011-02-12 2013-02-14 CertiVox Ltd. Use of non-interactive identity based key agreement derived secret keys with authenticated encryption
US8661240B2 (en) * 2011-04-29 2014-02-25 International Business Machines Corporation Joint encryption of data
CA2819211C (en) * 2011-04-29 2020-12-08 International Business Machines Corporation Data encryption
US8644510B2 (en) * 2011-05-11 2014-02-04 Alcatel Lucent Discovery of security associations for key management relying on public keys
WO2012165889A2 (en) * 2011-05-31 2012-12-06 삼성에스디에스 주식회사 Id-based encryption and signature method and terminal
US10318932B2 (en) 2011-06-07 2019-06-11 Entit Software Llc Payment card processing system with structure preserving encryption
US8891772B2 (en) * 2011-06-17 2014-11-18 Microsoft Corporation Cloud key escrow system
US8627508B2 (en) 2011-06-17 2014-01-07 Microsoft Corporation Cloud key directory for federating data exchanges
WO2013009290A1 (en) * 2011-07-11 2013-01-17 Hewlett-Packard Development Company, Lp Policy based data management
US9166778B2 (en) * 2011-07-15 2015-10-20 Alcatel Lucent Secure group messaging
US8619986B2 (en) * 2011-07-21 2013-12-31 Patton Protection Systems LLC Systems and methods for secure communication using a communication encryption bios based upon a message specific identifier
US8892875B1 (en) 2011-07-29 2014-11-18 Trend Micro Incorporated Methods and apparatus for controlling access to encrypted computer files
JP2013042315A (en) * 2011-08-12 2013-02-28 Sony Corp Information processing device and information processing method
US8948381B2 (en) * 2011-09-09 2015-02-03 Fujitsu Limited Conditional key generation based on expiration date of data
US9203613B2 (en) 2011-09-29 2015-12-01 Amazon Technologies, Inc. Techniques for client constructed sessions
EP3493070B1 (en) * 2011-09-29 2020-07-29 Amazon Technologies, Inc. Parameter based key derivation and resource access delegation
WO2013044284A1 (en) * 2011-09-30 2013-04-04 Abeyweera Ranganath C Method, system and apparatus for a communications client program and an associated transfer server for onymous and secure communications
US9065637B2 (en) * 2012-01-25 2015-06-23 CertiVox Ltd. System and method for securing private keys issued from distributed private key generator (D-PKG) nodes
US9154302B2 (en) 2012-01-25 2015-10-06 CertiVox Ltd. System and method for secure two-factor authenticated ID-based key exchange and remote login using an insecure token and simple second-factor such as a PIN number
WO2013114125A2 (en) * 2012-02-03 2013-08-08 David Sallis A method and database system for secure storage and communication of information
US8694771B2 (en) 2012-02-10 2014-04-08 Connect In Private Panama Corp. Method and system for a certificate-less authenticated encryption scheme using identity-based encryption
PT2648170E (en) * 2012-04-06 2015-02-20 Kapsch Trafficcom Ag A method for detecting a speed violation of a vehicle
JP5985894B2 (en) * 2012-06-06 2016-09-06 株式会社東海理化電機製作所 Electronic key registration method
JP5990406B2 (en) * 2012-06-06 2016-09-14 株式会社東海理化電機製作所 Electronic key registration method
FR2992509B1 (en) * 2012-06-21 2017-05-26 Commissariat Energie Atomique DEVICE AND METHOD FOR GENERATING A SESSION KEY
US10984415B2 (en) * 2012-06-25 2021-04-20 Li Tan System and methods for using limit-use encrypted code to transfer values securely among users
US10148285B1 (en) 2012-07-25 2018-12-04 Erich Schmitt Abstraction and de-abstraction of a digital data stream
JP6057150B2 (en) * 2012-07-30 2017-01-11 雅浩 満保 Public key encryption system, receiving apparatus, public key encryption method, program, and recording medium
CN103780385B (en) * 2012-10-23 2017-02-15 航天信息股份有限公司 Blind signature method based on elliptic curve and device thereof
US10007803B2 (en) * 2012-10-26 2018-06-26 Infosys Limited Searching over encrypted keywords in a database
KR101493212B1 (en) * 2012-10-31 2015-02-23 삼성에스디에스 주식회사 Method and system for id-based encryption and decryption
US9230072B1 (en) * 2012-12-17 2016-01-05 Creative Information Technology, Inc. Dynamic identity program templates
US8763085B1 (en) 2012-12-19 2014-06-24 Trend Micro Incorporated Protection of remotely managed virtual machines
US9197422B2 (en) * 2013-01-24 2015-11-24 Raytheon Company System and method for differential encryption
US9020151B1 (en) 2013-03-04 2015-04-28 Trend Micro Incorporated Secure real-time data replication with disk encryption and key management system
GB201309702D0 (en) 2013-05-30 2013-07-17 Certivox Ltd Security
US8971540B2 (en) 2013-05-30 2015-03-03 CertiVox Ltd. Authentication
US9106644B2 (en) 2013-05-30 2015-08-11 CertiVox Ltd. Authentication
CN104219047B (en) * 2013-05-31 2017-12-15 华为技术有限公司 A kind of method and apparatus of signature verification
KR101460541B1 (en) * 2013-07-15 2014-11-11 고려대학교 산학협력단 Public encryption method based on user ID
US9275242B1 (en) 2013-10-14 2016-03-01 Trend Micro Incorporated Security system for cloud-based emails
US9197419B1 (en) 2013-10-14 2015-11-24 Trend Micro Incorporated Security system for data stored in the cloud
JP5915629B2 (en) * 2013-11-28 2016-05-11 トヨタ自動車株式会社 Communication method, data sharing system, and communication node in data sharing system
US9219722B2 (en) 2013-12-11 2015-12-22 Globalfoundries Inc. Unclonable ID based chip-to-chip communication
US9628516B2 (en) 2013-12-12 2017-04-18 Hewlett Packard Enterprise Development Lp Policy-based data management
IN2014CH00681A (en) 2014-02-13 2015-08-14 Infosys Ltd
US10795858B1 (en) 2014-02-18 2020-10-06 Erich Schmitt Universal abstraction and de-abstraction of a digital data stream
US9946858B2 (en) * 2014-05-05 2018-04-17 Analog Devices, Inc. Authentication system and device including physical unclonable function and threshold cryptography
US10432409B2 (en) 2014-05-05 2019-10-01 Analog Devices, Inc. Authentication system and device including physical unclonable function and threshold cryptography
US9672342B2 (en) 2014-05-05 2017-06-06 Analog Devices, Inc. System and device binding metadata with hardware intrinsic properties
CN105099897B (en) * 2014-05-13 2020-01-21 中兴通讯股份有限公司 Method and gateway for communication between browser and telecommunication network
US9703979B1 (en) * 2014-06-13 2017-07-11 BicDroid Inc. Methods and computer program products for encryption key generation and management
EP3155754B1 (en) 2014-06-13 2018-10-24 Bicdroid Inc. Methods, systems and computer program product for providing encryption on a plurality of devices
CN104506483A (en) * 2014-10-21 2015-04-08 中兴通讯股份有限公司 Method for encrypting and decrypting information and managing secret key as well as terminal and network server
US10333696B2 (en) 2015-01-12 2019-06-25 X-Prime, Inc. Systems and methods for implementing an efficient, scalable homomorphic transformation of encrypted data with minimal data expansion and improved processing efficiency
US10020940B2 (en) * 2015-02-23 2018-07-10 Oracle International Corporation Identity-based encryption for securing access to stored messages
SG10201504240VA (en) * 2015-05-29 2016-12-29 Huawei Internat Pte Ltd A method and system for secure sms communications
GB201509499D0 (en) * 2015-06-02 2015-07-15 Certivox Ltd Zkd
US9584493B1 (en) 2015-12-18 2017-02-28 Wickr Inc. Decentralized authoritative messaging
CN105530087B (en) * 2015-12-28 2019-05-10 北京航空航天大学 The attribute base encryption method of adaptability selection ciphertext safety
EP3855677A1 (en) 2016-02-23 2021-07-28 Nchain Holdings Limited Blockchain-implemented method for control and distribution of digital content
CN109314636B (en) 2016-02-23 2022-01-11 区块链控股有限公司 Cryptographic method and system for secure extraction of data from blockchains
AU2017222468B2 (en) 2016-02-23 2023-01-12 nChain Holdings Limited Agent-based turing complete transactions integrating feedback within a blockchain system
WO2017145002A1 (en) * 2016-02-23 2017-08-31 nChain Holdings Limited Personal device security using elliptic curve cryptography for secret sharing
MX2018010045A (en) 2016-02-23 2019-01-21 Nchain Holdings Ltd Blockchain-based exchange with tokenisation.
SG10202011640TA (en) 2016-02-23 2021-01-28 Nchain Holdings Ltd System and method for controlling asset-related actions via a blockchain
JP6799061B2 (en) 2016-02-23 2020-12-09 エヌチェーン ホールディングス リミテッドNchain Holdings Limited Secure multi-party loss resistant storage and transfer of cryptographic keys for blockchain-based systems combined with wallet management systems
CN109074579B (en) 2016-02-23 2022-10-11 区块链控股有限公司 Method and system for protecting computer software using distributed hash table and blockchain
RS64953B1 (en) 2016-04-14 2024-01-31 Rhombus Systems Group Inc System for verification of integrity of unmanned aerial vehicles
JP6844411B2 (en) * 2016-05-17 2021-03-17 富士通株式会社 Relationship encryption
US10116440B1 (en) 2016-08-09 2018-10-30 Amazon Technologies, Inc. Cryptographic key management for imported cryptographic keys
JP6719339B2 (en) * 2016-08-30 2020-07-08 三菱電機株式会社 Cryptographic system, cryptographic method, and cryptographic program
CN110050437B (en) * 2016-09-06 2020-10-23 华为技术有限公司 Apparatus and method for distributed certificate registration
US10389719B2 (en) 2016-10-28 2019-08-20 Entit Software Llc Parameter based data access on a security information sharing platform
CN106570405B (en) * 2016-11-04 2020-10-27 北京百度网讯科技有限公司 Method and device for encrypting/decrypting characters in input method
US10452877B2 (en) 2016-12-16 2019-10-22 Assa Abloy Ab Methods to combine and auto-configure wiegand and RS485
US10341098B2 (en) * 2017-01-24 2019-07-02 Nxp B.V. Method of generating cryptographic key pairs
US11356427B1 (en) 2017-02-15 2022-06-07 Wells Fargo Bank, N.A. Signcrypted envelope message
US10484379B2 (en) * 2017-03-16 2019-11-19 Motorola Solutions, Inc. System and method for providing least privilege access in a microservices architecture
EP3379766B1 (en) * 2017-03-20 2019-06-26 Huawei Technologies Co., Ltd. A wireless communication device for communication in a wireless communication network
US11354660B1 (en) 2017-04-27 2022-06-07 Wells Fargo Bank, N.A. Encapsulation of payment information
US10425235B2 (en) 2017-06-02 2019-09-24 Analog Devices, Inc. Device and system with global tamper resistance
US10958452B2 (en) 2017-06-06 2021-03-23 Analog Devices, Inc. System and device including reconfigurable physical unclonable functions and threshold cryptography
EP4210271A1 (en) * 2017-06-07 2023-07-12 nChain Licensing AG Credential generation and distribution method and system for a blockchain network
CN107257279B (en) * 2017-06-29 2020-02-11 广东浩云长盛网络股份有限公司 Plaintext data encryption method and device
JP7043203B2 (en) * 2017-08-29 2022-03-29 Kddi株式会社 Cryptographic device, decryption device, encryption system, encryption method and encryption program
WO2019074479A1 (en) * 2017-10-09 2019-04-18 Hewlett-Packard Development Company, L.P. Encrypted transaction receipts
US11146397B2 (en) * 2017-10-31 2021-10-12 Micro Focus Llc Encoding abelian variety-based ciphertext with metadata
US10846412B2 (en) * 2017-11-14 2020-11-24 Blackberry Limited Electronic device including display and method of encrypting and decrypting information
US10594666B2 (en) 2017-12-19 2020-03-17 Micron Technology, Inc. Secure message including a vehicle private key
US11323249B2 (en) * 2017-12-20 2022-05-03 Lg Electronics, Inc. Cryptographic methods and systems for authentication in connected vehicle systems and for other uses
SG10201801094VA (en) 2018-02-08 2019-09-27 Huawei Int Pte Ltd System and method for computing an escrow session key and a private session key for encoding digital communications between two devices
US10911227B2 (en) * 2018-04-12 2021-02-02 Mastercard International Incorporated Method and system for managing centralized encryption and data format validation for secure real time multi-party data distribution
AU2019273039A1 (en) * 2018-05-25 2020-11-26 Finco Services, Inc. Cryptographic technology platform and methods for providers to enable users to monetize their data
EP3883178A4 (en) * 2018-11-13 2022-08-10 Bluepopcon Inc. Encryption system and method employing permutation group-based encryption technology
EP3664361A1 (en) * 2018-12-06 2020-06-10 Secure-IC SAS Methods and devices for secured identity-based encryption systems with two trusted centers
CN109687959B (en) * 2018-12-29 2021-11-12 上海唯链信息科技有限公司 Key security management system, key security management method, key security management medium, and computer program
US11764940B2 (en) 2019-01-10 2023-09-19 Duality Technologies, Inc. Secure search of secret data in a semi-trusted environment using homomorphic encryption
US11139982B2 (en) * 2019-01-30 2021-10-05 Rsa Security Llc Communication-efficient device delegation
CN110166254B (en) * 2019-05-27 2020-09-29 国家电网有限公司 Method and device for realizing identity-based key management by using intelligent contract
JP2020195100A (en) * 2019-05-29 2020-12-03 株式会社bitFlyer Blockchain Device and method for proving reliability of public key, and program therefor
WO2020242614A1 (en) 2019-05-30 2020-12-03 Kim Bong Mann Quantum safe cryptography and advanced encryption and key exchange (aeke) method for symmetric key encryption/exchange
US11588646B2 (en) 2019-09-05 2023-02-21 Cisco Technology, Inc. Identity-based application and file verification
JP7338405B2 (en) 2019-10-31 2023-09-05 凸版印刷株式会社 Payment authentication system and payment authentication method
EP4066437A1 (en) 2019-11-28 2022-10-05 VIBE Cybersecurity IP Inc. Method and system for a verifiable identity based encryption (vibe) using certificate-less authentication encryption (clae)
JP7254296B2 (en) 2019-12-12 2023-04-10 日本電信電話株式会社 Key exchange system, information processing device, key exchange method and program
WO2021242524A2 (en) * 2020-05-12 2021-12-02 Bae Systems Information And Electronic Systems Integration Inc. Wireless multi-fuze setter interface
US11870898B2 (en) * 2020-05-21 2024-01-09 Workday, Inc. Split keys for wallet recovery
US11405200B1 (en) 2020-05-21 2022-08-02 Workday, Inc. Multilevel split keys for wallet recovery
CN111740958A (en) * 2020-05-22 2020-10-02 卓望数码技术(深圳)有限公司 Data encryption method, data decryption method, encryption and decryption transmission method and system
CN111698095B (en) * 2020-06-17 2023-07-11 南京如般量子科技有限公司 Data chain anti-quantum computing communication method and system based on ID cryptography and symmetric key pool
US11122021B1 (en) 2020-06-25 2021-09-14 Bank Of America Corporation Server for handling multi-encrypted messages
US11451389B2 (en) 2020-06-25 2022-09-20 Bank Of America Corporation Multi-encrypted message response manager
US11757846B2 (en) 2020-06-25 2023-09-12 Bank Of America Corporation Cognitive multi-encrypted mail platform
WO2022008940A1 (en) 2020-07-07 2022-01-13 Vibe Cybersecurity Inc. Method and system for a verifiable identity based encryption (vibe) using certificate-less authentication encryption (clae)
US11621837B2 (en) * 2020-09-03 2023-04-04 Theon Technology Llc Secure encryption of data using partial-key cryptography
US11310042B2 (en) 2020-09-11 2022-04-19 Crown Sterling Limited, LLC Methods of storing and distributing large keys
CN112019335B (en) * 2020-09-18 2023-12-29 上海市数字证书认证中心有限公司 SM2 algorithm-based multiparty collaborative encryption and decryption method, device, system and medium
CN112583590B (en) * 2020-12-14 2022-06-17 联芸科技(杭州)有限公司 Information issuing method and system based on group shared key
CN112528312B (en) * 2020-12-24 2023-10-03 贵州大学 Signcryption method and system based on Cocks identity cryptosystem
CN113312608B (en) * 2021-04-23 2024-03-08 中国电力科学研究院有限公司 Electric power metering terminal identity authentication method and system based on time stamp
CN113094675B (en) * 2021-04-29 2023-03-28 香港中文大学(深圳) User authentication method and device based on distributed model training
JPWO2022259494A1 (en) * 2021-06-10 2022-12-15
WO2022259495A1 (en) * 2021-06-10 2022-12-15 日本電信電話株式会社 Communication system, user terminal, communication method and communication program
CA3226534A1 (en) * 2021-07-22 2023-01-26 Howard University Hybrid public-key and private-key cryptographic systems based on iso-rsa encryption scheme
CN113794702A (en) * 2021-08-31 2021-12-14 杭州控客信息技术有限公司 Communication high-level encryption method in intelligent household system
US11755772B2 (en) 2021-09-20 2023-09-12 Crown Sterling Limited, LLC Securing data in a blockchain with a one-time pad
CN113890730A (en) * 2021-09-23 2022-01-04 上海华兴数字科技有限公司 Data transmission method and system
CN114065171B (en) * 2021-11-11 2022-07-08 北京海泰方圆科技股份有限公司 Identity authentication method, device, system, equipment and medium
US11791988B2 (en) 2021-11-22 2023-10-17 Theon Technology Llc Use of random entropy in cryptography
US11902420B2 (en) 2021-11-23 2024-02-13 Theon Technology Llc Partial cryptographic key transport using one-time pad encryption
EP4195581A1 (en) * 2021-12-08 2023-06-14 Nagravision Sàrl Improvements in and relating to cryptography
CN114679262A (en) * 2021-12-31 2022-06-28 广东国腾量子科技有限公司 Quantum key distribution system and method fusing asymmetric system
CN114422220B (en) * 2022-01-06 2024-02-27 浙江数秦科技有限公司 Ciphertext non-unique data encryption transmission method

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4405829A (en) * 1977-12-14 1983-09-20 Massachusetts Institute Of Technology Cryptographic communications system and method
US4748668A (en) * 1986-07-09 1988-05-31 Yeda Research And Development Company Limited Method, apparatus and article for identification and signature
US5016276A (en) * 1986-07-31 1991-05-14 Kabushiki Kaisha Advance Common cryptokey generation system and communication system using common cryptokeys
US5146500A (en) * 1991-03-14 1992-09-08 Omnisec A.G. Public key cryptographic system using elliptic curves over rings
US5150411A (en) * 1990-10-24 1992-09-22 Omnisec Cryptographic system allowing encrypted communication between users with a secure mutual cipher key determined without user interaction
US5159632A (en) * 1991-09-17 1992-10-27 Next Computer, Inc. Method and apparatus for public key exchange in a cryptographic system
US5179301A (en) * 1989-09-06 1993-01-12 U.S. Philips Corporation Switched current differentiator circuit for differentiating an input signal in the form of a sampled analog current
US5271061A (en) * 1991-09-17 1993-12-14 Next Computer, Inc. Method and apparatus for public key exchange in a cryptographic system
US5272755A (en) * 1991-06-28 1993-12-21 Matsushita Electric Industrial Co., Ltd. Public key cryptosystem with an elliptic curve
US6061448A (en) * 1997-04-01 2000-05-09 Tumbleweed Communications Corp. Method and system for dynamic server document encryption
US6307935B1 (en) * 1991-09-17 2001-10-23 Apple Computer, Inc. Method and apparatus for fast elliptic encryption with direct embedding
US20020076042A1 (en) * 2000-12-19 2002-06-20 Ravi Sandhu System and method for crypto-key generation and use in cryptosystem
US6886096B2 (en) * 2002-11-14 2005-04-26 Voltage Security, Inc. Identity-based encryption system

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5202921A (en) * 1991-04-01 1993-04-13 International Business Machines Corporation Method and apparatus for authenticating users of a communication system to each other
JP2000515649A (en) * 1996-08-07 2000-11-21 バンカーズ・トラスト・コーポレーション Simultaneous electronic transactions by visible and trusted parties
US5982898A (en) * 1997-03-07 1999-11-09 At&T Corp. Certification process
JP3542895B2 (en) * 1997-08-22 2004-07-14 インターナショナル・ビジネス・マシーンズ・コーポレーション Time-constrained cryptosystem
JP3275812B2 (en) * 1997-12-12 2002-04-22 日本電気株式会社 ID-authenticated key distribution method and apparatus, and machine-readable recording medium recording program
JP2002501218A (en) * 1998-01-09 2002-01-15 サイバーセイフ コーポレイシヨン Client-side public key authentication method and device using short-lived certificate
US6446205B1 (en) * 1998-12-10 2002-09-03 Citibank, N.A. Cryptosystems with elliptic curves chosen by users
JP2001209313A (en) * 2000-01-25 2001-08-03 Canon Inc Certificate issuing device, information processor, information communication system, attribute certifying method and storage medium
US7239701B1 (en) * 2000-05-02 2007-07-03 Murata Machinery Ltd. Key sharing method, secret key generating method, common key generating method and cryptographic communication method in ID-NIKS cryptosystem
JP4450969B2 (en) 2000-05-02 2010-04-14 村田機械株式会社 Key sharing system, secret key generation device, common key generation system, encryption communication method, encryption communication system, and recording medium
JP2002164877A (en) * 2000-09-14 2002-06-07 Advanced Mobile Telecommunications Security Technology Research Lab Co Ltd Key escrow and group communication method
GB2370471B (en) 2000-12-20 2004-06-23 Director Government Comm Headq Directoryless Public Key Cryptographic System and Method
WO2003017559A2 (en) * 2001-08-13 2003-02-27 Board Of Trustees Of The Leland Stanford Junior University Systems and methods for identity-based encryption and related cryptographic techniques
FR2892251A1 (en) * 2005-10-14 2007-04-20 Gemplus Sa CRYPTOGRAPHIC METHOD IMPLEMENTING AN IDENTITY-BASED ENCRYPTION SYSTEM
US8694771B2 (en) * 2012-02-10 2014-04-08 Connect In Private Panama Corp. Method and system for a certificate-less authenticated encryption scheme using identity-based encryption

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4405829A (en) * 1977-12-14 1983-09-20 Massachusetts Institute Of Technology Cryptographic communications system and method
US4748668A (en) * 1986-07-09 1988-05-31 Yeda Research And Development Company Limited Method, apparatus and article for identification and signature
US5016276A (en) * 1986-07-31 1991-05-14 Kabushiki Kaisha Advance Common cryptokey generation system and communication system using common cryptokeys
US5179301A (en) * 1989-09-06 1993-01-12 U.S. Philips Corporation Switched current differentiator circuit for differentiating an input signal in the form of a sampled analog current
US5150411A (en) * 1990-10-24 1992-09-22 Omnisec Cryptographic system allowing encrypted communication between users with a secure mutual cipher key determined without user interaction
US5146500A (en) * 1991-03-14 1992-09-08 Omnisec A.G. Public key cryptographic system using elliptic curves over rings
US5272755A (en) * 1991-06-28 1993-12-21 Matsushita Electric Industrial Co., Ltd. Public key cryptosystem with an elliptic curve
US5159632A (en) * 1991-09-17 1992-10-27 Next Computer, Inc. Method and apparatus for public key exchange in a cryptographic system
US5271061A (en) * 1991-09-17 1993-12-14 Next Computer, Inc. Method and apparatus for public key exchange in a cryptographic system
US5581616A (en) * 1991-09-17 1996-12-03 Next Software, Inc. Method and apparatus for digital signature authentication
US6307935B1 (en) * 1991-09-17 2001-10-23 Apple Computer, Inc. Method and apparatus for fast elliptic encryption with direct embedding
US6061448A (en) * 1997-04-01 2000-05-09 Tumbleweed Communications Corp. Method and system for dynamic server document encryption
US20020076042A1 (en) * 2000-12-19 2002-06-20 Ravi Sandhu System and method for crypto-key generation and use in cryptosystem
US6886096B2 (en) * 2002-11-14 2005-04-26 Voltage Security, Inc. Identity-based encryption system

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080091947A1 (en) * 2006-10-17 2008-04-17 Andrew John Dancer Software registration system
US8271788B2 (en) * 2006-10-17 2012-09-18 Trend Micro Incorporated Software registration system
US8290146B2 (en) * 2007-01-19 2012-10-16 Mitsubishi Electric Corporation Ciphertext generating apparatus, cryptographic communication system, and group parameter generating apparatus
US20100104094A1 (en) * 2007-01-19 2010-04-29 Mitsubishi Electric Corporation Ciphertext generating apparatus, cryptographic communication system, and group parameter generating apparatus
US20120233465A1 (en) * 2007-04-05 2012-09-13 International Business Machines Corporation Distribution of Credentials
US9112680B2 (en) * 2007-04-05 2015-08-18 International Business Machines Corporation Distribution of credentials
US10511579B2 (en) 2007-06-29 2019-12-17 Microsoft Technology Licensing, Llc Confidential mail with tracking and authentication
US9847977B2 (en) * 2007-06-29 2017-12-19 Microsoft Technology Licensing, Llc Confidential mail with tracking and authentication
US20090006851A1 (en) * 2007-06-29 2009-01-01 Microsoft Corporation Confidential mail with tracking and authentication
US20090030778A1 (en) * 2007-07-23 2009-01-29 Motivepath, Inc. System, method and apparatus for secure multiparty location based services
US8090108B2 (en) * 2008-04-15 2012-01-03 Adaptive Chips, Inc. Secure debug interface and memory of a media security circuit and method
US20090257594A1 (en) * 2008-04-15 2009-10-15 Amjad Qureshi Secure debug interface and memory of a media security circuit and method
US8045708B2 (en) * 2008-05-21 2011-10-25 Apple Inc. Discrete key generation method and apparatus
US20090319769A1 (en) * 2008-05-21 2009-12-24 Apple Inc. Discrete key generation method and apparatus
US20100119058A1 (en) * 2008-11-11 2010-05-13 Seiichi Matsuda Information processing apparatus, information processing method, and program
US8166203B1 (en) * 2009-05-29 2012-04-24 Google Inc. Server selection based upon time and query dependent hashing
EP2700189A4 (en) * 2011-04-01 2015-03-18 Certicom Corp Identity-based decryption
WO2012129640A3 (en) * 2011-04-01 2012-12-06 Certicom Corp. Identity-based decryption
US9490974B2 (en) * 2011-04-01 2016-11-08 Certicom Corp. Identity-based decryption
US20120254616A1 (en) * 2011-04-01 2012-10-04 Certicom Corporation Identity-Based Decryption
US20130322620A1 (en) * 2012-05-31 2013-12-05 Samsung Sds Co., Ltd. Apparatus and method for generating secret key for id-based encryption system and recording medium having program recorded thereon for causing computer to execute the method
US9172530B2 (en) * 2012-05-31 2015-10-27 Samsung Sds Co., Ltd. Apparatus and method for generating secret key for ID-based encryption system and recording medium having program recorded thereon for causing computer to execute the method
US20150120650A1 (en) * 2013-10-30 2015-04-30 Gordon E. Seay Methods and Systems for Utilizing Global Entities In Software Applications
US10019519B2 (en) * 2013-10-30 2018-07-10 Gordon E. Seay Methods and systems for utilizing global entities in software applications
US20160301531A1 (en) * 2015-04-09 2016-10-13 Qualcomm Incorporated Proof of work based user identification system
US10015017B2 (en) * 2015-04-09 2018-07-03 Qualcomm Incorporated Proof of work based user identification system

Also Published As

Publication number Publication date
JP2011151866A (en) 2011-08-04
DE60236094D1 (en) 2010-06-02
EP2224637A3 (en) 2012-05-23
WO2003017559A3 (en) 2003-07-10
EP1425874A4 (en) 2009-04-15
JP2005500740A (en) 2005-01-06
AU2002332671A1 (en) 2003-03-03
EP1425874A2 (en) 2004-06-09
EP1425874B1 (en) 2010-04-21
EP2429116A2 (en) 2012-03-14
US7634087B2 (en) 2009-12-15
US7113594B2 (en) 2006-09-26
JP5933786B2 (en) 2016-06-15
EP2224637A2 (en) 2010-09-01
EP2429116B1 (en) 2013-07-10
US9356779B2 (en) 2016-05-31
US8130964B2 (en) 2012-03-06
US20030081785A1 (en) 2003-05-01
EP2224637B1 (en) 2014-10-08
ATE465571T1 (en) 2010-05-15
US20070041583A1 (en) 2007-02-22
US20100208895A1 (en) 2010-08-19
JP2012032843A (en) 2012-02-16
EP2429116A3 (en) 2012-05-30
JP2015144495A (en) 2015-08-06
US20120159188A1 (en) 2012-06-21
WO2003017559A2 (en) 2003-02-27

Similar Documents

Publication Publication Date Title
US7634087B2 (en) Systems and methods for identity-based encryption and related cryptographic techniques
Baek et al. Identity-based threshold decryption
Boneh et al. Identity-based encryption from the Weil pairing
Dutta et al. Pairing-based cryptographic protocols: A survey
Gentry Certificate-based encryption and the certificate revocation problem
US8320559B1 (en) Identity-based-encryption system
US7751558B2 (en) Certificate-based encryption and public key infrastructure
Gentry et al. Identity-based aggregate signatures
Galindo et al. Improved certificate-based encryption in the standard model
Paterson Cryptography from pairings: a snapshot of current research
Gorantla et al. A survey on id-based cryptographic primitives
Chen An interpretation of identity-based cryptography
Wang et al. Two proxy signcryption schemes from bilinear pairings
Yang et al. Efficient mediated certificates public-key encryption scheme without pairings
an Wang et al. On the role of pkg for proxy re-encryption in identity based setting
Ahmad et al. TIBC: Trade-off between Identity-Based and Certificateless Cryptography for future internet
Maftei et al. A Note on IBE Performance of a Practical Application
Yong et al. Identity-based threshold signature and mediated proxy signature schemes
Elkamchouchi et al. An efficient ID-based proxy signcryption scheme without bilinear pairings
Lee et al. Efficient and robust secure key issuing protocol in id-based cryptography
Penev Identity Based Public Key Infrastructures

Legal Events

Date Code Title Description
AS Assignment

Owner name: UNIVERSITY OF CALIFORNIA DAVIS, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FRANKLIN, MATTHEW;REEL/FRAME:018145/0644

Effective date: 20060712

Owner name: BOARD OF TRUSTEES OF THE LELAND STANFORD JUNIOR UN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BONEH, DAN;REEL/FRAME:018121/0027

Effective date: 20060719

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: VENTURE LENDING & LEASING VII, INC., CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:VOLTAGE SECURITY, INC.;REEL/FRAME:032170/0273

Effective date: 20140131

Owner name: VENTURE LENDING & LEASING VI, INC., CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:VOLTAGE SECURITY, INC.;REEL/FRAME:032170/0273

Effective date: 20140131

AS Assignment

Owner name: VOLTAGE SECURITY, INC., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNORS:VENTURE LENDING & LEASING VI, INC.;VENTURE LENDING & LEASING VII, INC.;REEL/FRAME:035110/0726

Effective date: 20150227

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., DELAWARE

Free format text: SECURITY INTEREST;ASSIGNORS:ATTACHMATE CORPORATION;BORLAND SOFTWARE CORPORATION;NETIQ CORPORATION;AND OTHERS;REEL/FRAME:044183/0718

Effective date: 20170901

Owner name: JPMORGAN CHASE BANK, N.A., DELAWARE

Free format text: SECURITY INTEREST;ASSIGNORS:ENTIT SOFTWARE LLC;ARCSIGHT, LLC;REEL/FRAME:044183/0577

Effective date: 20170901

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12

AS Assignment

Owner name: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC), CALIFORNIA

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:063560/0001

Effective date: 20230131

Owner name: NETIQ CORPORATION, WASHINGTON

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131

Owner name: MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.), WASHINGTON

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131

Owner name: ATTACHMATE CORPORATION, WASHINGTON

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131

Owner name: SERENA SOFTWARE, INC, CALIFORNIA

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131

Owner name: MICRO FOCUS (US), INC., MARYLAND

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131

Owner name: BORLAND SOFTWARE CORPORATION, MARYLAND

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131

Owner name: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC), CALIFORNIA

Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062746/0399

Effective date: 20230131