CROSS REFERENCE TO RELATED APPLICATIONS

[0001]
The present application is a continuation of U.S. patent application Ser. No. 11/454,394, filed Jun. 16, 2006, incorporated herein by reference, which is a division of U.S. patent application Ser. No. 11/304,200 filed on Dec. 15, 2005, incorporated herein by reference, which claims priority under 35 U.S.C. §119(e) to provisional U.S. patent application No. 60/637,177 filed Dec. 17, 2004, incorporated herein by reference.
BACKGROUND OF THE INVENTION

[0002]
The present invention relates to performing authentication as to whether or not an element possesses a prespecified property. An example is authenticating validity of a digital revocation in a public key infrastructure, or authenticating validity of an entitlement to use a resource (e.g. to sign onto a World Wide Web site).

[0003]
FIG. 1 illustrates digital certificate validation and revocation in a public key infrastructure. Digital certificates 104 are used in public key infrastructures (PKI) to facilitate secure use and management of public keys in a networked computer environment. Users U1, U2, . . . utilize their computer systems 110.1, 110.2, . . . to generate respective key pairs (PK, SK) where PK is the public key and SK is the secret key. FIG. 1 shows a key pair (PK_{U1}, SK_{U1}) for user U1. The users register their public keys PK, over a network, with a certification authority (CA) 120. Alternatively, the key pairs can be generated by CA 120 and sent to the users. CA 120 is a secure, trusted computer system. For each public key PK, CA 120 generates a digital certificate 104. Certificate 104 contains the public key PK and the user's name and/or email address or addresses, may also contain the certificate's serial number SN (generated by the CA to simplify the certificate management), the certificate issue date D1, the expiration date D2, an identification of algorithms to be used with the public and secret keys, an identification of the CA 120, and possibly other data. The data mentioned above is shown at 104D. Certificate 104 also contains CA's signature 104Sig_{CA }on the data 104D. The signature is generated using CA's secret key SK_{CA}. CA 120 sends the certificate 104 to the user's (key owner's) computer system 110. Either the owner or the CA 120 can distribute the certificate to other parties to inform them of the user's public key PK. Such parties can verify the CA's signature 104Sig_{CA }with the CA's public key PK_{CA }to ascertain that the certificate's public key PK does indeed belong to the person whose name and email address are provided in the certificate.

[0004]
A certificate may have to be revoked prior to its expiration date D2. For example, the certificate owner U may change his affiliation or position, or the owner's private key SK_{U }may be compromised. Other parties must be prevented from using the owner's public key if the certificate is revoked.

[0005]
One approach to prevent the use of public keys of revoked certificates is through a certificate revocation list (CRL). A CRL is a signed and timestamped list issued by CA 120 and specifying the revoked certificates by their serial numbers SN. These CRLs must be distributed periodically even if there are no new revoked certificates in order to prevent any type of replay attack. The CRL management may be unwieldy with respect to communication, search, and verification costs. The CRL approach can be optimized using socalled deltaCRLs, with the CA transmitting only the list of certificates that have been revoked in the previous time period (rather than for all time periods). The deltaCRL technique still has the disadvantage that the computational complexity of verifying that a certificate is currently valid is basically proportional to the number of time periods, since the verifier must confirm that the certificate is not in any of the deltaCRLs.

[0006]
Certificate revocation trees (CRTs) can be used instead of CRLs as described in [15] (the bracketed numbers indicate references listed at the end before the claims).

[0007]
Instead of CRLs and CRTs, CA 120 could answer queries about specific certificates. In FIG. 1, user U2 issues a query 150 with the serial number SN of certificate 104 of user U1. CA 120 responds with a validity status information 160 containing the serial number SN, a validity status field 160VS (“valid”, “revoked” or “unknown”), and a time stamp “Time”. The response is signed by CA (field 160Sig_{CA}). This approach is used for Online Certificate Status Protocol (OCSP). See [23]. Disadvantageously, the CA's digital signature 160Sig_{CA }can be quite long (over 1024 bits with RSA), especially since the CA must be very secure. In addition, if CA 120 is centralized, the CA becomes a validation bottleneck. If CA 120 is decentralized (replicated), the security is weakened as the CA's signing key SK_{CA }is replicated.

[0008]
FIG. 2 illustrates a “NOVOMODO” approach, which allows CA 120 to provide an unsigned validity status through untrusted directories 210 at prespecified time intervals (e.g. every day, or every hour, etc.). Directories 210 are computer systems that do not store secret information. The system works as follows.

[0009]
Let f be a predefined public lengthpreserving function

[0010]
f: {0,1}^{n}→0,1^{n }

[0000]
where {0,1}^{n }is the set of all binary strings of a length n. Let f^{i }denote the ffold composition; that is, f^{i}(x)=x for i=0, and f^{i}(x)=f(f^{i−1}(x)) for i>0. Let f be oneway, i.e. given f(x) where x is randomly chosen, it is hard (infeasible) to find a preimage z such that f(z)=f(x), except with negligible probability. “Infeasible” means that given a security parameter k (e.g. k=n), the preimage z cannot be computed in a time equal to a predefined polynomial in k except with negligible probability. Let us assume moreover that f is oneway on its iterates, i.e. for any i, given y=f^{i}(x), it is infeasible to find z such that f(z)=y.

[0011]
We can assume, without loss of generality, that CA is required to provide a fresh validity status every day, and the certificates are valid for one year, i.e. 365 days (D2D1=365 days). To create a certificate 104 (FIG. 2), CA 120 picks a random “seed” number x and generates a “hash chain” c_{0}, c_{1}, . . . c_{365 }wherein:

[0000]
c _{365} =f(x), c _{364} =f(f(x)), . . . c _{1} =f ^{365}(x), c _{0} =f ^{366}(x). (1)

[0000]
We will sometimes denote x as x(SN) for a certificate with a serial number SN, and similarly c_{i}=c_{i}(SN) where i=0, 1, . . . . The value c_{0 }is called a “validation target”. CA 120 inserts C_{0 }into the certificate 104 together with data 104D (FIG. 1). CA 120 also generates a random revocation seed number N_{0}, computes the “revocation target” N_{1}=f(N_{0}), and inserts N_{1 }into certificate 104. CA 120 keeps all c_{i }secret for i>0. The values x and N_{0 }are also secret. Clearly, all c_{i }can all be computed from x, and the validation target c_{0 }can be computed from any c_{i}. CA 120 stores in its private storage the values x and N_{0 }for each certificate 104, and possibly (but not necessarily) caches the c_{i }values.

[0012]
Every day i (i=1, 2, . . . 365), a certificate revalidation is performed for the valid certificates as follows. For each certificate
104, CA distributes to directories
210 a validation data structure which includes, in addition to a validity status indication (not shown in
FIG. 2, can be “valid” or “revoked”):
 1. the certificate's “itoken” c_{i }if the certificate is valid on day i;
 2. the revocation seed N_{0 }if the certificate has been revoked.
(We will call c_{i }a “validity proof”, and N_{0 }a “revocation proof”.) This information is distributed unsigned. Each directory 210 provides this information, unsigned, to a requester system 110 in response to a validity status request 150 (FIG. 1). To verify, the requester (verifier) 110 performs the following operations:
 1. If the validity status is “valid”, the verifier 110 checks that f^{i}(c_{i})=c_{0}.
 2. If the validity status is “revoked”, the verifier 110 checks that f(N_{0})=N_{1}. Despite the validity information being unsigned, the scheme is secure because given c_{i}, it is infeasible to compute the subsequent tokens c_{i+1}, c_{i+2}, . . . .

[0017]
To reduce the communication between CA 120 and directories 210, a hash chain (1) can be generated for a set of certificates 104, and a single itoken c_{i }can be distributed for the set if the set is “unrevoked” (i.e. all the certificates are unrevoked in the set). The certificate 140 will contain a separate target c_{0 }for each set containing the certificate and associated with a hash chain (see [1]).

[0018]
Certificate revocation can also be performed using accumulators. See [37]. An accumulator is a way to combine a set of values (e.g. a set of valid certificates) into a shorter value. A formal definition of a “secure” accumulator is given in Appendix A at the end of this disclosure before the claims. An accumulator example can be constructed as follows. Let us denote all possible values that can be accumulated as p_{1}, . . . , p_{t}. (For example, each p_{i }can be a unique number assigned to a certificate, and we want to accumulate the values corresponding to the valid certificates.) Suppose v_{0 }is the accumulator value for the empty set. Let ƒ be a oneway function. To accumulate p_{1}, we compute the accumulator as follows:

[0000]
v({p _{1}})=ƒ(v _{0} , p _{1}) (2)

[0000]
Now to accumulate p_{2}, we set the accumulator to be v_{2}=ƒ(v_{1}, p_{2}), and so on. More generally, the accumulator value for some set {p_{i} _{ 1 }, . . . , p_{i} _{ } is }

[0000]
v({p _{i} _{ 1 }, . . . , p_{i} _{ m }})=ƒ(ƒ( . . . ƒ (v _{0} , p _{i} _{ 1 }) . . . ), p _{i} _{ m }) (3)

[0000]
The function ƒ can be chosen such that the accumulation order does not matter, i.e.

[0000]
ƒ(ƒ(v, p _{i}), p _{j})=ƒ(ƒ(v, p _{j}), p _{i}) (4)

[0000]
(this is the “quasicommutative” property).

[0019]
In each period j, CA 120 can send to the directories 210 a pair (v_{j}, t) where v_{j }is the accumulator value for the set of the valid certificates, and t is a time stamp. The directories can respond to queries 150 with some proof that the accumulator value v_{j }accumulates the value p_{i }corresponding to the certificate of interest.

[0020]
A common accumulator is an RSA accumulator defined as follows:

[0000]
ƒ(v, p)=v ^{p }mod n (5)

[0000]
where p is a positive integer, and n=q_{1}q_{2 }is the product of large prime numbers q_{1 }and q_{2}. In this case,

[0000]
v({p _{i} _{ 1 }, . . . , p_{i} _{ m }})=v _{0} ^{pi} ^{ 1 } ^{, . . . , pi} _{ m }mod n (6)

[0021]
The certificate validation is performed as follows. Without loss of generality, suppose that the values p_{1}, . . . , p_{m }correspond to the valid certificates in a period j. Then the accumulator value distributed by CA 120 to directories 210 is

[0000]
v _{j} =v _{0} ^{p} ^{ 1 } ^{. . . p} ^{ m }mod n (7)

[0000]
If a verifier 110 inquires a directory 210 of the status of a certificate corresponding to the value p_{i }which is one of p_{1}, . . . , p_{m}, the directory sends to the verifier the accumulator value v_{j }and a “witness” value

[0000]
s _{i, j} =v _{0} ^{p} ^{ 1 } ^{. . . p} ^{ i−1 } ^{p} ^{ i+1 } ^{. . . p} ^{ m }mod n (8)

[0000]
The verifier checks that

[0000]
s _{i, j} ^{p} ^{ i } =v _{j }mod n (9)

[0000]
If this equality holds, the certificate is assumed to be valid.

[0022]
The witness s_{i, j }is hard to forge provided that it is hard to compute the p_{i}th root of v_{j}. The p_{i}th root computation is hard if the adversary does not know the factorization of n and the strong RSA assumption is valid (this assumption is defined in Appendix A). However, it is possible to keep p_{i }and s_{i, j }secret. For example, instead of providing the values s_{i, j }and p_{i }to the verifier, the verifier can be provided with a proof that such values exist and are known to the certificate owner.

[0023]
Accumulators can be used more generally to prove that an element satisfies some prespecified property.
SUMMARY

[0024]
This section summarizes some features of the invention. Other features are described elsewhere in this disclosure. The invention is defined by the appended claims.

[0025]
In some embodiments of the present invention, accumulators are constructed using modular roots with exponents corresponding to the accumulated values. For example, suppose we need an accumulator to accumulate all the elements that possess some property (e.g. all the valid certificates) or all the elements that do not possess that property (e.g. all the revoked certificates). We will associate each element with an integer greater than 1. Let PP_{m}={p_{1}, . . . , p_{m}} be the set of integers associated with the elements to be accumulated (as in (7)), and denote the product of these integers as P_{m}:

[0000]
$\begin{array}{cc}{P}_{m}=\prod _{l=1}^{m}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89e{p}_{l}& \left(10\right)\end{array}$

[0000]
(By definition herein, the product of the empty set of numbers is 1; i.e. P_{m}=1 if PP_{m }is empty.) In some embodiments, the accumulator value represents the P_{m}th root of some value u, e.g.

[0000]
v _{j} =u ^{1/P} ^{ m }mod n (11)

[0000]
In some embodiments, the following advantages are achieved.

[0026]
Suppose the value (11) accumulates valid digital certificates. The value (11) can be modified by exponentiation to deaccumulate all the values p_{l }except for some given value p_{i }i.e. to compute

[0000]
v _{j} ^{p} ^{ 1 } ^{. . . p} ^{ i−1 } ^{p} ^{ i+1 } ^{. . . p} ^{ m } =u ^{1/p} ^{ i } (12)

[0000]
This exponentiation can be performed by a directory 210 or by the certificate owner's system 110, without knowledge of factorization of the modulus n. The value (12) is the accumulator value as if p_{i }were the only accumulated value. The witness value needed for verification can also be computed as if p_{i }were the only accumulated value. The verification (the authentication) can be performed using the values that do not depend on accumulated values other than p_{i}. Alternatively, the verification can be performed with the accumulator and witness values that incorporate some other accumulated values but not necessarily all the accumulated values. Therefore, if a directory 210 or a user 110 are responsible for providing validity proofs for less than all of the certificates, the directory 210 or the user 110 (the “validity prover”) can use an accumulator that accumulates less than all of the valid certificates. In some embodiments, this feature reduces the number of computations needed to be performed by all of the provers.

[0027]
In some embodiments, the value u=u(j) can depend on the time period j for which the authentication is provided (unlike the value v_{0 }in (7)). Therefore, the time stamp t can be omitted.

[0028]
In some embodiments, the accumulator accumulates the revoked certificates rather than the valid certificates. In some embodiments, the witness values for an integer p_{i }depend on other p values.

[0029]
In some embodiments, the witness values are used as encryption keys for encrypting validity proofs. The validity proofs can be constructed using a nonaccumulator based validation system, e.g. as in FIG. 2. For example, let c_{j}(i) denote the token c_{j }for the period j for a certificate 140.i, where c_{j }is formed as in (1). At the setup time, when a user system 110 joins the certificate validation system, the CA generates the tokens c_{j}(i) for all the periods j for the user. The CA also generates the witness values for all the periods j. The CA encrypts each token c_{j}(i) under a key equal to (or obtained from) the witness value for the period j, under a symmetric encryption system. CA 120 transmits all the encrypted values to the user.

[0030]
In each period j, if the certificate 140.i is still valid, CA 120 transmits the decryption key (the witness value) for the period j to the user, enabling the user to recover the token c_{j}(i). The user provides the token to the verifiers to proof the certificate validity as described above in connection with FIG. 2.

[0031]
Some embodiments of the invention are suitable for limited bandwidth or low reliability networks, for example in ad hoc networks, where the nodes 110 may have low computational and transmission power, and where the nodes may have only incomplete information about the topology of the network. (An ad hoc network is a selfconfiguring wireless network of mobile routers.)

[0032]
Some embodiments are communication and storage efficient.

[0033]
The invention is not limited to the features and advantages described above. Other features are described below. The invention is defined by the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS

[0034]
FIGS. 1, 2 are block diagrams illustrating prior art certificate revocation schemes.

[0035]
FIG. 3 illustrates a digital certificate according to some embodiments of the present invention.

[0036]
FIG. 4 is a flowchart of operations performed by a certification authority (CA) in initial certification according to some embodiments of the present invention.

[0037]
FIG. 5 is a block diagram illustrating certificate revalidation operations performed by a CA according to some embodiments of the present invention.

[0038]
FIG. 6 is a flowchart of witness derivation operations according to some embodiments of the present invention.

[0039]
FIG. 7 is a flowchart of authentication according to some embodiments of the present invention.

[0040]
FIG. 8 is a block diagram showing data transmitted over networks in deaccumulation operations according to some embodiments of the present invention.

[0041]
FIG. 9 is a state diagram illustrating accumulator transmissions according to some embodiments of the present invention.

[0042]
FIG. 10 is a block diagram showing data transmissions in determining the network paths according to some embodiments of the present invention.

[0043]
FIG. 11 is a flowchart of operations performed by a certification authority (CA) in initial certification according to some embodiments of the present invention.

[0044]
FIG. 12 is a block diagram illustrating certificate revalidation operations performed by a CA according to some embodiments of the present invention.

[0045]
FIG. 13 is a flowchart of witness derivation operations according to some embodiments of the present invention.

[0046]
FIG. 14 is a flowchart of authentication according to some embodiments of the present invention.
DESCRIPTION OF PREFERRED EMBODIMENTS

[0047]
The embodiments described in this section illustrate but do not limit the invention. The invention is defined by the appended claims.

[0048]
In the following description, numerous details are set forth. However, the present invention may be practiced without these details. Some portions of the detailed descriptions that follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a selfconsistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0049]
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or some computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and other storage into other data similarly represented as physical quantities within the computer system storage, transmission or display devices.

[0050]
The present invention also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a generalpurpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CDROMs, and magneticoptical disks, readonly memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system.

[0051]
Some of the algorithms presented herein are not inherently related to any particular computer or other apparatus. Various generalpurpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required operations. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. A machinereadable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machinereadable medium includes read only memory (“ROM”); random access memory (“RAM”); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.
Preliminaries

[0052]
Model And Notation.

[0053]
In our model, we have a certification authority CA, a certificate owner or holder Owner, and a certificate verifier VV. Here Owner has a certificate issued by CA. The concept of a certification authority may apply more generally to any authority responsible for issuing access control privileges or authorizations to a plurality of individuals. The concept of an owner may be tied to a specific human being or organization operating a computer or to the computer itself, e.g. a world wide web server. Similarly, the verifier may be tied to a specific human being or organization operating a computer or to the computer itself, e.g. an access control server determining if it should permit access to certain services.

[0054]
In a given transaction, VV wishes to ascertain that the certificate has not been revoked prior to its expiration date. To do so, VV must obtain a proof of validity or a proof of revocation that is or has been issued by the certification authority CA. VV may obtain this proof either from the CA directly, or through some other distribution mechanism.

[0055]
We let {0,1}* denote the set of all bit strings. For a bit string s, we denote its length by s. We let H denote a cryptographic compression function that takes as input a bbit payload as well as a vbit initialization vector or IV, and produces a vbit output. We assume b≧2v, which holds for all wellknown constructions in use. For the constructions we describe here, we typically take b=2v. We assume these cryptographic compression functions are collision resistant; that is, finding two distinct inputs m_{1}≠m_{2 }such that H (IV, m_{1})=H (IV, m_{2}) is difficult. We assume that the IV is fixed and publicly known. For notational simplicity, we will not always explicitly list IV as an argument in the hash function. A practical example of such a cryptographic compression function is SHA1[26]. SHA1's compression function has an output and IV size of 20bytes and a 64byte payload size. In many embodiments, we will not need to operate on data larger than the compression function payload size; however there are numerous standard techniques such as iterated hashing or Merkletrees [19] for doing so. For simplicity, we will use the term hash function instead of compression function, where it is understood that a hash function can take arbitrary length strings {0,1}* and produce a fixed length output in {0,1}^{v}.

[0056]
In practice, one often constructs a length preserving function that is one way on its iterates by starting with a hash function H and padding part of the payload to make it length preserving.

[0057]
Finally, for a real number r, we set ┌r┐ to be the ceiling of r, that is, the smallest integer value greater than or equal to r. Similarly, └r┐ denotes the floor of r, that is, the largest integer value less than or equal to r.

[0058]
Let A be an algorithm. By A(·) we denote that A has one input. By A(·, . . . ,·) we denote that A has several inputs). By A_{(.) }we will denote that A is an indexed family of algorithms. y←A(x) denotes that y was obtained by running A on input x. In case A is deterministic, then this y is unique; if A is probabilistic, then y is a random variable. If S is a set, then y←S denotes that y was chosen from S uniformly at random. Let b be a boolean function. The notation (y←A(x):b(y)) denotes the event that b(y) is true after y was generated by running A on input x. Finally, the expression

[0000]
Pr[{x _{i} ←A _{i}(y _{i})}_{1≦i≦n} :b(x _{n})]

[0000]
denotes the probability that b(x_{n}) is TRUE after the value x_{n }was obtained by running algorithms A_{1 }. . . , A_{n }on inputs y_{1}, . . . y_{n}.
Accumulation of Valid Certificates

[0059]
Some accumulator schemes will now be described with respect to the digital certificate validation. These schemes can also be used for other authentication operations as described above.

[0060]
To simplify the description, we will assume that each certificate owner Ui operates just one system 110.i and owns at most one certificate. This is not in fact necessary.

[0061]
CA SetUp.

[0062]
The CA 120 generates a composite modulus n. In some embodiments, n is the product of two primes, but n can also be the product of three or more primes. In some embodiments, n is public, but n is hard to factor, and the factorization is known only to the CA 120.

[0063]
Initial Certification (FIG. 4):

[0064]
Suppose the ith user u_{i }joins the system in or after some time period j_{0}. At step 410, the CA assigns a positive integer p_{i }to u_{i}. The numbers p_{i }are chosen to be mutually prime with the modulus n. Also, each p_{i }does not divide the LCM (lowest common multiple) of the remaining numbers p_{l}, 1≠i. For example, the numbers p_{1}, . . . , p_{i }can be distinct prime numbers, or pairwise relatively prime.

[0065]
The CA computes a unique public value m_{i}∈(Z/nZ)* for the user u_{i}. (Z/nZ is the ring of all residue classes modulo n, and (Z/nZ)* is the multiplicative group of the invertible elements of Z/nZ, i.e. of the elements defined by integers mutually prime with n.) In some embodiments,

[0000]
m _{i} =H _{1}(u _{i} , p _{i} , j _{0} , w _{i})∈(Z/nZ)* (13)

[0000]
where H_{1 }is a predefined function, e.g. a oneway collision resistant function, u_{i }is the user identification (e.g. user name), and w_{i }is an optional string (which may contain u_{i}'s public key and/or some other information). The value m_{i }thus binds p_{i }to u_{i}'s identity. If desired, any one or more of the values j_{o}, p_{i}, m_{i }and the identification of the function H_{1 }can be made part of the certificate 140. See FIG. 3 showing a certificate 140 containing m_{i}, j_{o}, and specifying the functions H_{1 }and H_{2 }(H_{2 }is described below).

[0066]
At step 420, the CA computes an “initial certificate” value

[0000]
s _{i, j} _{ 0 } =m _{i } ^{1/p} ^{ i }(mod n) (14)

[0000]
The CA keeps this value secret, and transmits it to the user u_{i}'s system 110 in an encrypted form.

[0067]
Certificate ReValidation by CA in Time Period j (FIG. 5):

[0068]
At the start of, or shortly before, the period j, the CA performs the following operations. Let t denote the total number of users in the system (i.e. the total number of users for whom the initial certification of FIG. 4 has been performed). Let UU denote the set of these users: UU={u_{1}, . . . . , u_{t}}. PP denotes the set of the corresponding p numbers: PP={p_{1}, . . . , p_{t}}. Let UU_{j} ⊂ UU be the subset of users that are to be revalidated in period j. Let PP_{j} ⊂ PP be the corresponding set of numbers p, and let

[0000]
P _{j}=π_{pk} ∈PP _{j} ^{pk } (15)

[0000]
i.e., P_{j }is the product of the integers in PP_{j}. (By definition, the product of the empty set of numbers is 1.) The CA computes

[0000]
h _{j} =H _{2}(j)∈(Z/nZ)*, h _{j−1} =H _{2}(j−1)∈(Z/nZ)* (16)

[0000]
where H_{2 }is the same as H_{1 }or some other function. The CA also computes the accumulator

[0000]
v _{j} =v _{j}(PP _{j})=(h _{j} /h _{j−1})^{1/P} ^{ j }(mod n) (17)

[0000]
Of note, in some embodiments, the root in (17) exists with a very high probability.

[0069]
The CA transmits the following data to the system
110 of each user in UU
_{j }(this data can also be broadcast to a larger set of users if such broadcast transmission is more efficient in terms of communication):
 1. v _{j};
 2. the list of users in UU_{j}, which may be just the list of numbers p_{i }in PP_{j}. (Since there can be overlap among these lists for different periods j, the CA can simply transmit the information that has changed since the previous period; in this case, the CA transmits the list of numbers in PP_{j }to each new user at step 430 of FIG. 4.)

[0072]
Personal Accumulator and Witness Derivation by Users (FIG. 6):

[0073]
At step 610, each user u_{i }in UU_{j }computes its “personal accumulator” v_{j}(p_{i}), i.e. the accumulator which accumulates only the user's p_{i }value:

[0000]
v _{j}(p _{i})=(h _{j} /h _{j−1})^{1/p} ^{ i }(mod n) (18)

[0000]
This value is computed from the v_{j }value (17) by exponentiation:

[0000]
$\begin{array}{cc}{v}_{j}\ue8a0\left({p}_{i}\right)={v}_{j}^{\stackrel{\prod}{\mathrm{pk}\in {\mathrm{PP}}_{j}\ue89e{\left\{{p}_{i}\right\}}^{\mathrm{pk}}}}\ue8a0\left(\mathrm{mod}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89en\right)& \left(19\right)\end{array}$

[0000]
At step 620, the user aggregates this personal accumulator with previous personal accumulators to obtain a witness for the period j:

[0000]
s _{i, j} =s _{i, j−1} v _{j}(p _{i})=s _{i, j−1}(h _{j} /h _{j−1})^{1/p} ^{ i }(mod n) (20)

[0000]
The equations (20) and (14) imply that

[0000]
s _{i, j} =s _{i, j} _{ 0 }(h _{j} /h _{j} _{ 0 })^{1/p} ^{ i }(mod n) (21)

[0074]
User Authentication (FIG. 7):

[0075]
A user u
_{i }can provide s
_{i, j }to the verifier, along with (if necessary) the values for (u
_{i}, p
_{i}, j
_{0}, w
_{i}). At step
710, the verifier:
 1. computes m_{i }from (13) or obtains it from the certificate 140 (FIG. 3);
 2. computes h_{j}=H_{2}(j) and h_{j} _{ o }=H_{2}(j_{o}) (see (16)); and
 3. confirms that

[0000]
s _{i, j} ^{p} ^{ i } =m _{i} h _{j} /h _{j} _{ 0 }(mod n) (22)

[0079]
Alternative User Authentication:

[0080]
Instead of giving the witness s_{i, j }to the verifier, the user can use s_{i, j }as a private key in an identitybased GQ (GuillouQuisquater) signature scheme. This scheme is described in Appendix B at the end of this disclosure before the claims. The CA performs the functions of GQ's PKG (private key generator); GQ's parameters are set as follows: B=s_{i, j}, v=p_{i}, and J=m_{i} ^{−1 }mod n. The authentication proceeds as follows:

[0081]
The verifier sends to the user a random message m.

[0082]
The user generates a random number r and computes:

[0000]
d=H(m∥r ^{p} ^{ i }), D=rs _{i, j} ^{d } (23)

[0000]
where H is some predefined public function (e.g. H_{1 }or H_{2}). The user sends the values m, r^{P} ^{ i }, and D to the verifier.

[0083]
The verifier computes J=m_{i} ^{−1 }mod n and checks that the following equations hold:

[0000]
d=H(m∥J ^{d } D ^{p} ^{ i }) (24)

[0000]
J ^{d } D ^{p} ^{ i } =r ^{p} ^{ i }(h _{j} /h _{j} _{ o })^{d }(mod n)

[0084]
This scheme may reduce total bandwidth because the verifier does not need the certificate 140. Note: for the GQ signature scheme to be secure, it is desirable that each p_{i}>2^{160}.

[0085]
Remarks.

[0086]
1. First, s_{i, j} _{ 0 }can be computed in some other way, not necessarily as in (14).

[0087]
2. Anonymous Authentication.

[0088]
If we want to allow the user nodes 110 to sign messages anonymously—i.e., to be able to authenticate themselves as users that have been certified by the CA, but without revealing their actual identities—we can handle initial certification differently. For example, instead of (13), the CA can set m_{i }to be independent of the user's identity, e.g.:

[0000]
m _{i} =h _{j} _{ 0 } =H(j _{0})∈(Z/nZ)* (25)

[0000]
The m_{i }value is then provided to the user. To hide the fact that the m_{i }value is provided to the user, the m_{i }value may be transmitted to the user via a secure channel (e.g., by encrypting this value such that only u_{i }can decrypt it). Then, it follows from (14) and (21) that:

[0000]
s _{i, j} =h _{j} ^{1/p} ^{ i }(mod n) (26)

[0089]
As mentioned below in Appendix A, there are efficient zeroknowledge (ZK) proofs through which user u_{i }can prove, in the j^{th }time period, that it knows a p^{th }root of h_{j }modulo n for some (unrevealed) number p that is contained in a specified interval I of integers, i.e.

[0000]
PK{(α, β): α
^{β} =h _{j }mod
n β∈I}

[0000]
See [41], [42]. The interval I can be an interval containing all the numbers p_{i}. Using this scheme, the user can authenticate itself anonymously if and only if it has obtained an initial certificate s_{i, J} _{ 0 }and the subsequent personal accumulator values v_{j}(p_{i}) (see (18), (19)).
The CA can revoke the user as before—i.e., by not revalidating it (not including p_{i }in the product P_{j }in FIG. 5).

[0090]
As mentioned above, the accumulator techniques are not limited to a user possessing a single certificate or to a digital certificate revocation. For example, a user u_{i }may or may not possess one or more of entitlements e_{1}, e_{2}, . . . e_{r}. During initial certification, the user u_{i }is assigned a unique integer p_{i, k }if the user is to be certified for an entitlement e_{k}. The entitlement proof proceeds as described above with respect to equations (13)(26), with numbers p_{i }replaced by p_{i, k }with s_{i, j }replaced by s_{i, k, j}, etc.

[0091]
In some of these embodiments, however, a value p_{i }is computed as the product of P_{i, k}. For example, if the user is initially certified for all the entitlements, then:

[0000]
p _{i} =p _{i, 1 } . . . p _{i, r } (27)

[0000]
In some embodiments, the integers p_{i, k }are mutually prime relative to each other and to the CA's modulus n. The user u_{i}'s initial certificate is s_{i, j} _{ 0 }=m_{i} ^{1/p} ^{ i }(mod n) as in (14), and u_{i }can use exponentiation to deaccumulate all the values p_{i, l }except a selected value p_{i, k }for some k:

[0000]
$\begin{array}{cc}{s}_{i,k,{j}_{0}}={m}_{i}^{1/{p}_{i,k}}\ue8a0\left(\mathrm{mod}\ue89en\right)={s}_{i,{j}_{0}}^{\prod _{l\ne k}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89e{p}_{i,l}}\ue8a0\left(\mathrm{mod}\ue89en\right)& \left(28\right)\end{array}$

[0000]
The user can use this value to demonstrate that it possesses the entitlement that corresponds to prime p_{i, k }without revealing the user's other entitlements. The CA can revoke a specific entitlement e_{k }for the user without revoking the user's other entitlements, simply by issuing a validation accumulator in (17) that does not accumulate p_{i, k }(i.e. the product P_{j }is computed as in (15) except that p_{i }is replaced with p_{i}/p_{i, k }(the number p_{i, k }is not included in the product)). If the user wants to sign anonymously and unlinkably, then the user cannot reveal its specific value of p_{i, k}, but it would seem to make it difficult for a verifier to determine what entitlement the user is claiming (if the verifier cannot see the value of p_{i, k}). We can get around this problem by, for example, associating each entitlement e_{k }to a range of integers I_{i}. This range will contain all the p_{i, k }values for all the users u_{i }initially certified to have the entitlement e_{k}. The ranges I_{k }do not overlap in some embodiments. Then the user can prove in ZK that it possesses a modular pth root (for some unrevealed number p in the range I_{k}) of the appropriate value, i.e. the user can provide the following proof of knowledge:

[0000]
PK{(α, β): α
^{β} =C mod
n β∈I
_{k}} (29)

[0000]
where C=m_{i}h_{j}/h_{j−1 }or C=h_{j }(see (21), (26)). See [41], [42]. The user can also prove that it possesses multiple entitlements simultaneously, e.g., by proving (in ZK if desired) its possession of a p^{th }root for some p that is the product of (for example) two integers p_{1 }and p_{2 }in ranges corresponding to the claimed entitlements:

[0000]
PK{(α, β): α
^{β} =C mod
n β=β
_{1}β
_{2} β
_{1}∈I
_{k} _{ 1 } β
_{2}∈I
_{k} _{ 2 }} (30)
See [41], [42].

[0092]
Users Moving From Network to Network:

[0093]
Suppose the CA has users (certificate owner systems) 110 in different networks, and the users move from a network to a network (e.g. some of the networks may be ad hoc networks). The CA can calculate a separate accumulator (say, (17)) for each network. Each accumulator will accumulate only the valid users in the corresponding network based on the CA's knowledge of the current composition of users in each network. Each user will compute its personal accumulator value and/or witness value (e.g., as in (18), (20), (26), and/or (28)). The user can move to another network and use the same personal accumulator value and/or witness value in the other network.

[0094]
Aggregation of Personal Accumulators:

[0095]
Multiple personal accumulators can be aggregated into a single value, in order to save bandwidth; from this aggregated value, a verifier can batchverify that multiple users are indeed certified. For example, in the scheme of equations (17), (22), user u_{i }(if it is still valid) possesses a personal value s_{i, j }that satisfies

[0000]
s _{i, j} ^{p} ^{ i } =m _{i}(h _{j} /h _{j} _{ 0, i })(mod n) (31)

[0000]
where m_{i }as in (13), and j_{o, i }is the period j_{o }for the user u_{i}. Denote

[0000]
z _{i} =m _{i}(h _{j} /h _{j} _{ 0, i })(mod n). (32)

[0000]
Then, for multiple users in period j, their personal values can simply be multiplied together

[0000]
$\begin{array}{cc}S=\prod _{i=1}^{{t}^{\prime}}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89e{s}_{i,j}\ue8a0\left(\mathrm{mod}\ue89en\right)& \left(33\right)\end{array}$

[0000]
where t′ is the number of users which take part in the aggregation (or the number of certificates or entitlements belonging to a user if each u_{i }is a certificate or an entitlement). A verifier can use the value (33) to confirm that users (or certificates or entitlements) (u_{i}, . . . , u_{t′}) are valid by confirming that:

[0000]
$\begin{array}{cc}{S}^{\prod _{i=1}^{{t}^{\prime}}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89e{p}_{i}}=\prod _{i=1}^{{t}^{\prime}}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89e{z}_{i}^{\frac{1}{{p}_{i}}\ue89e\prod _{i=1}^{{t}^{\prime}}\ue89e\phantom{\rule{0.3em}{0.3ex}}\ue89e{p}_{i}}\ue8a0\left(\mathrm{mod}\ue89en\right).& \left(34\right)\end{array}$

[0096]
DeAccumulation.

[0097]
We will now discuss concrete approaches to the deaccumulation of values from the accumulator computed by the CA; however, we note that the CA does not need to compute a single accumulator value that accumulates all of the values associated to all of the valid nodes 110 in the network. Instead, the CA can use a tradeoff, which we now describe. Deaccumulation is somewhat computationally expensive. Procedure Split(v,P) below performs deaccumulation on an accumulator v that accumulates t kbit numbers P={p_{i}}; the procedure's output is t personal accumulators; the execution time is O(t log^{2 }t) (where we consider k to be a constant). Let us denote the accumulator accumulating an empty set of values as u (in equation (17), u=h(j)/h(j−1)).
Then

[0098]
u=v ^{π} ^{ pi } ^{∈P} ^{ pi }(mod n). (35)

[0099]
Procedure Split(v,P):

 1. Split the set P into two disjoint halves P_{1 }and P_{2}.
 2. Compute v_{1} =v ^{π} ^{ pi } ^{∈P} ^{ 2 } ^{ pi }(mod n); this is the accumulator for the set P_{1}.
 3. Compute v_{2} =v ^{π} ^{ pi } ^{∈P} ^{ 1 } ^{ pi }(mod n); this is the accumulator for the set P_{2}.
 4. If P_{1 }has only one member, output (v_{1}, P_{1}), otherwise call Split (v_{1}, P_{1}).
 5. If P_{2 }has only one member, output (v_{2}, P_{2}), otherwise call Split (v_{2}, P_{2}).
End of Split (v,P)

[0105]
As a rule of thumb, exponentiating a number modulo n by a product of t′ numbers takes time proportional to t′; thus, the first split operation (steps 2 and 3 in procedure Split(v,P)) is the most expensive one in the recursion above. (Actually, since there are t distinct numbers (p_{1}, . . . , p_{t}), the p_{i }are O(log t) bits apiece on average, so that the exponentiation is proportional to t′ log t′; since the Split algorithm can recurse to a depth of log t′, the overall computation complexity is t log^{2 }t.) To reduce the amount of deaccumulation that needs to be performed, the CA can (for example) compute two accumulators—one for each of two halves P_{1 }and P_{2 }of P—and transmit these two accumulators to the users, thereby allowing the users to skip the first split operation and thereby reducing their computation. The CA can reduce their computation further by transmitting even more accumulators, each for an even smaller subset of the users. In computing these multiple accumulators, it is advantageous for the CA to use its knowledge of the current network topology to enhance the performance of the scheme. For example, suppose that the users are divided into several (say, 10) topological areas. Then, instead of using one product of integers P_{j }as in (15), the CA can compute 10 such products P_{j, 1}, . . . , P_{j, 10}, and 10 areaspecific accumulators (h_{j}/h_{j−1})^{1/P} ^{ j, k }. The CA then transmits each one of these 10 areaspecific accumulators to the respective one of the 10 topological areas (along with a list of the revalidated users in that area). Users in a given area can compute their personal accumulators and witnesses from the areaspecific accumulators.

[0106]
Deaccumulation is also relevant to how the personal accumulators (18)(19) are computed. Clearly, in terms of computation, it is nonoptimal for each of the t users to perform deaccumulation (18), (19) independently; doing it this way would entail O(t^{2}) computation (actually, worse, since the size of the p_{i }must grow at least as fast as log t). In some embodiments, the users compute their personal accumulators cooperatively, as illustrated, for example, in FIG. 8 and described below.

[0107]
If the performance metric is minimum communication, a simple broadcast by the CA of the accumulator (17) to t users (see FIG. 5) is a good way of accumulator distribution. This results in overall communication of O(t). However, overall computation is at least O(t^{2}) because each of t users has to perform t−1 exponentiations on the same accumulator.

[0108]
Referring to FIG. 8, let PP_{j }be the set of valid users (i.e. the set of the p numbers corresponding to the valid users). At the stage of FIG. 5 (revalidation), the CA sends the accumulator v_{j}(PP_{j}) (see (17) for example) and the numbers p in the set PP_{j }to a designated node 110 (also marked D in FIG. 8). Node D divides the set PP_{j }into subgroups (subsets). In one example, the subgroup PP_{j}−0 includes one or more of nodes 110.0, 110.00, 110.01; the subgroup PP_{j}−1 includes one or more of nodes 110.1, 110.10, 110.11; the third subgroup consists of node 110 itself if this is a valid node. Node D computes the accumulator v_{j}(PP_{j}−0) for the subgroup PP_{j}−0, and the accumulator v_{j}(PP_{j}−1) for the subgroup PP_{j}−1. This computation can be performed by deaccumulating the nodes which are not subgroup members. See e.g. equation (19) and Procedure Split(v,P), steps 1 and 2. If node D is valid (i.e. its number p is in PP_{j}), node D also computes its personal accumulator as in FIG. 6. Node D transmits the accumulator v_{j}(PP_{j}−0), and the p numbers in the set PP_{j}−0, to node 110.0. Node D transmits the accumulator v_{j}(PP_{j}−1), and the p numbers in the set PP_{j}−1, to node 110.1. The nodes 110.0, 110.1 perform the same operations as node D. In particular, node 110.0 divides the valid users PP_{J}−0 into subgroups. In one example, the nodes 110.0, 110.00, 110.01 are valid; the subgroup PP_{j}00 consists of node 110.00; the subgroup PP_{j}01 consists of node 110.01; the third subgroup consists of node 110.0. The subgroups are determined by node 110.0 from the p numbers in PP_{j}0. Node 110.0 computes accumulators v_{j}(PP_{j}00), v_{j}(PP_{j}01) for the respective subgroups PP_{j}00, PP_{j}01, and also computes its personal accumulator as in FIG. 6. Node 110.0 transmits the accumulator v_{j}(PP_{j}00), and the corresponding p number, to node 110.00. Node 110.0 transmits the accumulator v_{j}(PP_{j}01), and the corresponding p number, to node 110.01. The accumulators v_{i}(PP_{j}00), v_{j}(PP_{j}01) are personal accumulators, so the nodes 110.00, 110.01 do not need to derive their personal accumulators.

[0109]
Node 110.1 performs operations similar to those for node 110.0.

[0110]
This procedure can be extended recursively to any number of nodes. The procedure is not limited to the “binarytree” type of FIG. 8. A node can split a set of users into any number of subgroups in addition to itself, possibly resulting in a nonbinarytree type operation. Also, in some embodiments, the accumulators are transmitted only to valid nodes. For example, if node 110 is invalid, then CA 120 transmits the accumulator v_{j}(PP_{j}) to a valid node instead. For communication efficiency, the subgroups are selected so that the communications are efficient within each subgroup. For example, in case of ad hoc networks, the subgroups can be selected based on geographic proximity, with the proximate nodes being grouped together.

[0111]
Now, we describe one approach for selecting the subgroups, where nodes only have local topology information. Roughly speaking, the idea is as follows. To partition (a portion of) the network, the designated node D chooses two “group heads” in the network, such as nodes 110.0, 110.1 in FIG. 8. (More than two group heads can also be selected.) These group heads can be chosen randomly. Alternatively, if the designated node has some topological information, it can use that information to attempt to choose the two group heads in a way that they are topologically distant—preferably on opposite sides of the network from each other. After D picks the two group heads, the designated node tells the two group heads to transmit different messages; for example, the designated node may tell the first group head to transmit ‘0’ and the second to transmit ‘1’. Then, each group head (e.g. 110.0, 110.1) “floods” the network with its particular message. When this occurs, the other nodes in the network will either receive a ‘0’ first or the ‘1’ first. Nodes that receive a ‘0’ first (e.g. nodes 110.00, 110.01) report back to the designated node D (or to the group head 110.0) that they are a member of the 0group; the members of the 1group report similarly. The designated node D (or the respective group heads) receives this information, and it deaccumulates the accumulator into two halves—one accumulator for the 0group and one for the 1group. If the designated node performed this deaccumulation (as in the procedure illustrated in FIG. 8), it passes along the appropriate accumulators to their corresponding group heads (110.0, 110.1). Then, each group head becomes the designated node for its corresponding subnetwork, and the entire process described above is repeated for the subnetworks. Now, we will provide more detail for one embodiment.

[0112]
At the beginning, there is only a single group PP of users which covers the whole network. Each recursion step is carried out in four phases as depicted in FIG. 9. The first recursion step is started by a node which is preferably located in the center of the network. We call this node the current designated node D. Node D executes the following four phases of recursion:

[0113]
Search Group Heads (State 910):

[0114]
Node D selects randomly two nodes out of its group as group heads GH0 and GH1. (For the sake of illustration, assume that node GH0 is node 110.0 of FIG. 8 or 10, and node GH1 is node 110.1). Node D sends out a broadcast message m_{searchGH }with its group ID, the addresses of GH0 and GH1, and a path variable containing D's address. All receiving nodes within the same group obtain a copy of the path and check if they are GH0 or GH1. If not, they add their address to the path variable in the message and forward it (broadcast it) once. The path variable provides each node with the path to D. FIG. 10 shows the messages m_{searchGH }transmitted by nodes D, 110.01, 110.10, 110.11.

[0115]
Build Group (State 920):

[0116]
If the receiver of m_{searchGH }is either GH0 or GH1, it starts building a subgroup by broadcasting a message m_{buildG }containing its address. If a receiver of m_{buildG }which belongs to the same group hasn't already received a message from a group head and therefore, joined its subgroup, he joins the subgroup announced in m_{buildG }and forwards the message once. FIG. 10 illustrates the m_{buildG }messages broadcast by nodes GH0, GH1, 110.01, 110.10, 110.11, assuming that the node 110.01 received the m_{u} buildG message from GH0 first, and nodes 110.10, 110.11 received the m_{buildG }message from GH1 first.

[0117]
Report Group (State 930):

[0118]
After some prescribed amount of time, all members of both subgroups start reporting their membership status to D. Therefore, they include their addresses together with their subgroup IDs 0 or 1 in the message m_{reportG }and send it over the path obtained in phase 1 to D. To make the reporting more efficient, nodes which are more distant from D start the reporting first. Nodes on the path of m_{reportG }add their subgroup membership information to the message and forward it according to the path to D. Nodes having forwarded a m_{reportG }don't initiate a report themselves.

[0119]
Transmit Accumulator (State 940):

[0120]
After D has received all reports, it looks up the paths p0 to GH0 and p1 to GH1 included in the received reports, exponentiates the accumulator v_{j }for its group to obtain the accumulators v_{j}(0) and v_{j}(1) for the respective subgroups, and sends the accumulators in respective messages m_{transmitu0 }over p0 to GH0 and m_{transmitu1 }over p1 to GH1, respectively. Additionally to the accumulators v_{j}(0) and v_{j}(1), these messages contain a list of the corresponding subgroup members. After reception of m_{transmitu0 }or m_{transmitu1}, respectively, GH0 and GH1 become designated nodes D of their subgroups and enter phase 910 of the next recursion step. The recursion ends if the subgroup accumulator is a personal accumulator.

[0121]
Considering a set of all users UU with cardinality UU=2^{R}=t, and equal distribution of each group PP into two groups of identical size PP/2, the recursion will end after R steps with a total number of t subgroups of size 1. Here, we mention a few aspects of the scheme's computational and communication complexity, assuming that, at each step, the split is into approximately equal halves.

[0122]
Search Group Heads:

[0123]
Within a subnetwork of size t′, this step requires O(t′) messages, each of size log t (since it requires log t bits on average to specify a single member of a group of t elements). Each message contains a path with average length C_{1 }√{square root over (t′)}. Therefore, communication for this subnetwork is of O(t′√{square root over (t′)} log t). If we assume that the partitions are always equallysized, the total communication of the entire recursive procedure is also O(t′√{square root over (t′)} log t).

[0124]
Build Group:

[0125]
This step involves a total of t messages, each of constant size, for communication complexity O(t).

[0126]
Report Group:

[0127]
Group membership information of the nodes is transmitted over C_{3}*√{square root over (t)} hops, where C_{3 }is a constant depending on the network density and reflecting the number of reports initiated: this results in communication of O (t′ √{square root over (t′)} log t).

[0128]
Transmit Accumulator:

[0129]
Accumulators together with group membership information of t nodes is transmitted over C_{4}*√{square root over (t)} hops, where C_{4 }is a constant depending on the network density: this results in communication of O (t′√{square root over (t′)} log t) and computation of O(tR log t)=O(t log^{2 }t).

[0130]
Overall, the communication is O(t√{square root over (t)} log t) and the computation is O(t log^{2 }t).

[0131]
If we assume that there is an entity E of the network with less stringent limitations in terms of computational power and energy such as the certification authority itself, another interesting opportunity arises. By acquiring some topology knowledge this entity may predeaccumulate the accumulator into accumulators for constant size groups. In detail, such a scheme works as follows: Some node C which holds the current accumulator for all users and has connectivity to E initiates a distributed clustering algorithm of FIG. 9. In a second step, C provides the clustering information to E and lets E perform the predeaccumulation for all clusters. Then C distributes the accumulators to the clusters. Suitable clustering algorithms have communication complexity of O(t√{square root over (t)} log t), but perhaps with a smaller constant factor than the approach described above.

[0132]
Briefly, we mention a distributed approach that splits a connected network into two connected subnetworks, where neither subnetwork is more than twice the size of the other. As before, we begin with a subnetwork that has a designated node. We assume that the subnetwork is connected, and that its topology is basically constant during the accumulator distribution (though it may change dramatically from period to period). The first step in the preferred algorithm for achieving O(t log t) communication and O(t log t) computation is that, in a distributed fashion, the nodes of the subnetwork establish an enumeration of themselves. This can be accomplished as follows. The designated node initiates the procedure by broadcasting a message. The nodes that receive the message transmit an acknowledgement message back to the designated node, and they log the designated node as the node from which they received the message. The designated node logs the acknowledging nodes as the nodes that received its message. This process recurses throughout the network. Specifically, a node that received the message from the designated node broadcasts the message, and nodes that have not sent or received the message before log the identity of the node that they received the message from and they send back an acknowledgment, after which the sending node logs the acknowledgers. If a node receives the message more than once, it only logs and responds back to the first node that sent it. In this fashion, since the subnetwork is connected, every node in the subnetwork (except the designated node) has a unique node from which it received the message, as well as a list of the nodes that received the message directly from it. Each node that has a nonempty list of acknowledgers chooses an arbitrary enumeration of those acknowledgers. In effect, from this procedure, we have constructed a tree (a graph with no loops) from the network, as well as an enumeration of all of the tree nodes given by the depthfirst preorder traversal of the tree. If the subnetwork has t′ nodes, this procedure can be accomplished with O(t′) communication and computation.

[0133]
The next stage of the algorithm is to use the enumeration to approximately bisect the subnetwork. There are a variety of different ways of doing this. One method is that each node, beginning with the nodes with no acknowledgers, could backtransmit (backwards according to the enumeration) the number of nodes in its subtree including itself; in this fashion, each node computes the number of nodes in its subtree. There must be exactly one node that has at least half of the nodes in its subtree, but such that none of its children have at least half. This node is designated to be the midpoint of the subnetwork. Now, viewing the midpoint point as the root of the tree, it divides its children into two groups, such that the number of nodes that are in a subtree emanating from one of the children in the first group is approximately equal to the number of nodes that are in a subtree emanating from one of the children in the second group. (This can always be accomplished such that ratio between the two numbers is at most two.) Thus, all of the network nodes except the midpoint become members of one of the two groups; the midpoint is considered to be a member of both groups. The step of computing how many nodes are in each subtree requires O(t′log t′) communication, since there are t transmissions, where the size of each transmission (which is a number between 1 and t′ representing how many nodes are in the given subtree) is log t′ bits. Viewing the midpoint node as the root node, a new enumeration of the nodes is established with the midpoint node as the initiator of the message, beginning with the nodes in the first group. (This new enumeration could be computed as before, or it could actually be derived indirectly from the previous enumeration. Either way, it does not add to the asymptotic communication complexity of the protocol, which is t log^{2 }t overall.)
AccumulatorBased Encryption of Validity Proofs

[0134]
The personal accumulators v_{j}(p_{i}) and/or the witness values s_{i, j }(see e.g. equations (17), (20), (21), (26)) can be used to obtain symmetric keys that users can use to decrypt validation proofs under other validation systems. An example will now be given for the validation system obtained by combining the systems of FIGS. 2, 47, but this is not limiting.

[0135]
Initial Certification:

[0136]
When a user u
_{i }joins the system, the CA:
 1. Generates the validation and revocation seeds x, N_{0 }as in FIG. 2.
 2. Generates all the tokens c_{j }for all the periods j (see FIG. 2 and equation (1)).
 3. Generates the certificate 140 as in FIG. 2 and transmits the certificate to the user u_{i}.
 4. Performs the steps of FIG. 4, i.e. generates the values p_{i}, m_{i}, s_{i, j} _{ 0 }and transmits S_{i, j} _{ 0 }to the validity prover (which can be the user u_{i }and/or the directories 210). The values p_{i}, m_{i}, can also be transmitted to the prover.
 5. Generates all the witness values s_{i, j }(for all the periods j) for the user u_{i}. Also generates the encryption keys K_{i, j }of which is s_{i, j }or some function of s_{i, j }.
 6. Encrypts each token c_{j }(generated at step 2 in this procedure) with the encryption key K_{i, j }under some encryption scheme (possibly a symmetric encryption scheme). Let us denote the encrypted c_{j }value as E_{i, j}.
 7. Transmits all the values E_{i, j }(for all j) to the prover (i.e. the directories 210 and/or the certificate owner u_{i}).

[0144]
ReValidation by CA:

[0145]
At the start of, or shortly before, each period j, the CA:
 1. Performs the procedure of FIG. 5, i.e. computes and broadcasts the accumulator value v_{j }and the list of valid p numbers to the provers.
 2. If the user u_{i}'s certificate is invalid, the CA transmits the revocation seed N_{0 }to the prover corresponding to the certificate (e.g. to the user u_{i }and/or the directories 210).

[0148]
Proof Derivation by the Prover:

[0149]
If the user u
_{i}'s certificate is valid (as indicated by the transmission of number p
_{i }in the REVALIDATION procedure at step 1), the prover:
 1. Performs the procedure of FIG. 6 to derive the witness value s_{i, j}.
 2. Obtains the decryption key K_{i, j }from s_{i, j}.
 3. Decrypts E_{i, j }to recover

[0153]
Authentication (Validity Proof): As in FIG. 2.

[0154]
Many variations are possible. For example, the decryption keys can be some different function of s_{i, j }than the encryption keys.
Accumulation of Revoked Certificates

[0155]
Above, we have described an approach in which an accumulator accumulates the valid certificates; an alternative approach is to accumulate revoked certificates. The valid certificates' owners (or validity provers) then use the “dynamic” feature of dynamic accumulators to compute a new accumulator for the valid nodes, and to compute their personal accumulators with respect to this new accumulator.

[0156]
As before, we will assume for the sake of illustration that each user operates a corresponding computer system 110 and owns at most one certificate 140. This is not limiting, as a user may own multiple certificates and/or operate multiple systems 110. The scheme is also applicable to controlling resource access and other kinds of authentication. We will use the word “user” to denote both the system 110 and the system's operator where no confusion arises. As described below, each user u_{i }will be assigned a positive integer p_{i }with the same properties as in the scheme of FIGS. 47 (e.g. p_{i }are mutually prime relative to the CA's public composite modulus n and to each other). The symbols n, PP, p_{i }will be as in the scheme of FIGS. 47. In particular, PP is the set of the p_{i }numbers.

[0157]
For each period j, the symbol QQ_{j }will denote the set of the revoked p_{i }numbers (i.e. the set of the p_{i }numbers corresponding to the certificates to be declared as revoked in period j). Q_{j }denotes the product of the numbers in QQ_{j}:

[0000]
Q _{j}=π_{Pk} ∈QQ _{j} ^{Pk } (36)

[0000]
The symbol α will denote an accumulator seed, which is an integer mutually prime with the modulus n. The accumulator of the values in Q_{j }is:

[0000]
v _{j}=α^{1/Q} ^{ j }mod n (37)

[0158]
Let RR_{j}=QQ_{j}−QQ_{j−1}, i.e. RR_{j }is the set of the p numbers corresponding to the certificates declared as revoked in period j but not in period j−1; in period j−1 these certificates were either declared as valid or were not yet part of the validation system. Let R_{j }denote the product of the numbers in RR_{j}:

[0000]
R _{j}=π_{Pk} ∈RR _{j} ^{Pk } (38)

[0000]
It is easy to see from (37) that if each certificate cannot be “unrevoked” (i.e. cannot be made valid once revoked), then:

[0000]
v _{j} =v _{j−1} ^{1/R} ^{ j }mod n (39)

[0159]
CA Set Up:

[0160]
The CA generates its modulus n and the accumulator seed α. The CA sets the initial accumulator value v_{j}=α for the initial period j.

[0161]
Initial Certification (FIG. 11):

[0162]
Suppose a user u_{i }wants to join the system in a period j_{o}, to be validated starting the next period j_{o}+1. At step 1110, CA 120 generates p_{i}, m_{i }as at step 410 in FIG. 4. These numbers can be made part of the user's certificate 140 (FIG. 3). At step 1120, the CA computes the following secret numbers:

[0000]
t _{i} =m _{i} ^{1/p} ^{ i }(mod n) (40)

[0000]
s _{i, j} _{ 0 } =v _{j} _{ 0 } ^{1/p} ^{ i }(mod n) (41)

[0000]
Here, v_{j} _{ 0 }is the accumulator value for the period j_{o }(v_{j} _{ 0 }=α if QQ_{j} _{ 0 }is empty). At step 1130, the CA transmits the values t_{i}, s_{i, j} _{ 0 }to the user u_{i }in an encrypted form. As will be explained, the user will be able to derive the value

[0000]
s _{i, j} =v _{j} ^{1/p} _{ i }(mod n) (42)

[0000]
for each period j>j_{o }for which the certificate is valid.

[0163]
Certificate ReValidation (FIG. 12):

[0164]
In period j, suppose that v
_{j−1}∈Z/nZ is the accumulator value for period j−1. For validation in period j, the CA:
 1. Computes v_{j }(using the equation (37) or (39) for example);
 2. Transmits the value v_{j }together with a list of the newlyrevoked certificates (perhaps represented by the set RR_{j}) to the users. If desired, the CA may also sign the pair (v_{j}, j) and transmit the signature to the users.

[0167]
Witness Derivation (FIG. 13):

[0168]
If a user u
_{i }is valid for the period j, then the user has the value s
_{i, j−1}=v
_{j−1} ^{1/p} _{ i }(mod n). See (41), (42). At step
1310, the user computes s
_{i, j}=v
_{j} ^{1/p} _{ i }as follows:
 1. The user applies the Extended Euclidian Algorithm to compute integers a and b such that

[0000]
ap _{i} +bR _{j}=1 (43)

[0000]
(this is possible because p
_{i}∉RR
_{j}, so p
_{i }and R
_{j }are mutually prime).
 2. The user sets s_{i, j }to the value:

[0000]
v _{j} ^{a} s _{i, j−1} ^{b }mod n (44)

[0000]
This value is indeed a p_{i}th root of v_{j }modulo n, because (note equation (39)):

[0000]
${\left({v}_{j}^{a}\ue89e{s}_{i,j1}^{b}\right)}^{{p}_{i}}={v}_{j}^{{\mathrm{ap}}_{i}}\ue89e{v}_{j1}^{\frac{1}{{p}_{i}}\ue89e{\mathrm{bp}}_{i}}={v}_{j}^{{\mathrm{ap}}_{i}}\ue89e{v}_{j}^{{R}_{j}\ue89eb}={v}_{j}\ue89e\mathrm{mod}\ue89en$

[0171]
At step 1320, the user computes the witness

[0000]
w _{i, j} =t _{i} s _{i, j } (45)

[0172]
User Authentication (FIG. 14):

[0173]
The user u_{i }provides t_{i}s_{i, j }(mod n) to the verifier, along with (if necessary) the values for (u_{i}, p_{i}, j_{0}, w_{i}). In addition, the user provides to the verifier the accumulator value v_{j }and the CA's signature on (v_{j},j). At step 1410, the verifier checks the CA's signature and confirms that:

[0000]
w _{i, j} ^{p} ^{ i } =m _{i} v _{j }(mod n) (46)

[0174]
Alternative User Authentication:

[0175]
The authentication can be performed using the identitybased GQ signature scheme as described above in connection with equations (23), (24), using w_{i, j }as a private key. The CA performs the functions of GQ's PKG (private key generator); GQ's parameters are set as follows: B=w_{i, j}, v=p_{i}, and J=m_{i} ^{−1 }mod n. The authentication proceeds as follows:

[0176]
The verifier sends to the user a random message m.

[0177]
The user generates a random number r and computes:

[0000]
d=H(m∥r ^{p} ^{ i }), D=rw _{i, j} ^{d }(mod n) (47)

[0000]
where H is some predefined public function. The user sends the values m, m_{i}, r^{P} ^{ i }, and D to the verifier.

[0178]
The verifier computes J=m_{i} ^{−1 }mod n and checks that the following equations hold:

[0000]
d=H(m∥J ^{d } D ^{p} ^{ i }) (48)

[0000]
J ^{d } D ^{p} ^{ i } =r ^{p} ^{ i } v _{j }(mod n)

[0179]
This scheme may reduce total bandwidth because the verifier does not need the certificate 140. Note: for the GQ signature scheme to be secure, it is desirable that p_{i}>2^{160}.

[0180]
The use of accumulator v_{j }allows a user to revoke itself, without the CA's help. To revoke itself in a period j, user u_{i }simply broadcasts v_{j} ^{1/p}(mod n), after which every other user u_{k }can update the accumulator to be v_{j}←v_{j} ^{1/p} ^{ i }(mod n) and can recompute its personal s_{k, j }and w_{k, j }values as in (43)(45). Of note, R_{j }can be recomputed by multiplying the previous R_{j }value by p_{i}.

[0181]
In some embodiments, this scheme allows efficient distribution (e.g. broadcast) for the CA at the stage of FIG. 12, since the CA transmits the same information to all the users. This information requires only O(t) transmissions. On the other hand, each transmission is proportional in size to the size of RR_{j}. Clients of the CA may include many users that are not in the particular tmember network that we are concerned about. If the “supernetwork” of clients of the CA is very large in proportion to t, this may not be a very good solution. Even if the CA only manages our tmember network, the CA's size of each transmission is still, strictly speaking, proportional to t, since the number of revocations within the network in a given period will tend to be a constant fraction of the total number of users. In this sense, the communication complexity of certificate distribution in this scheme is analogous to the communication complexity of a deltaCRL scheme. Recall that in a deltaCRL scheme, the CA transmits a list of users revoked in the given period, together with a signature on that list, to all users. On the other hand, since a personal accumulator's size is independent of the number of time periods, the scheme has better communication complexity for authentication than deltaCRLs, because in the deltaCRL scheme the verifier must separately check the deltaCRLs for all time periods to confirm that a given user has not been revoked during any of these periods.

[0182]
The invention is not limited to the embodiments described above. The invention is not limited to secure or dynamic accumulators. An accumulator can be any data that accumulate some elements. Further, the invention is not limited to the accumulators described above. For example, the accumulator seed h(j)/h(j−1) in equation (17) can be replaced with a value independent of the period j, and the accumulator seed α in the accumulator (37) can be replaced with a function of j. The accumulator methods can be used to prove (authenticate) membership in a set or possession of some property. Examples include authentication of valid entitlements, or authentication of people as being members of some organization.

[0183]
In some embodiments, the CA 120, the directories 210, and the systems 110 are computer systems communicating with each other over a network or networks. Each of these systems may itself be a computer system having components communicating over networks. Each computer system includes one or more computer processors executing computer instructions and manipulating computer data as described above. The term “data” includes “computer data” and covers both computer instructions and computer data manipulated by the instructions. The instructions and data can be stored on a data carrier such as a computer storage, i.e. a computer readable medium (e.g. a magnetic or optical disk, a semiconductor memory, and other types of media, known or to be invented). The data carrier may include an electromagnetic carrier wave transmitted over a network, e.g. through space, via a cable, or by some other means. The instructions and data are operable to cause the computer to execute appropriate algorithms as described above.

[0184]
The invention is not limited to any particular hash functions, or to cryptographic functions (which are easy to compute but are oneway or collision resistant). In some embodiments, it is desirable that a function ƒ or H be collision resistant not in the sense that it is difficult to find different x and y with the same image but in the sense that if x and y are uniformly drawn from the function's domain, the probability is small that they both will have the same image:

[0000]
P{H(x)=H(y)}≦α

[0000]
where α is a small constant (e.g. 1/10, or 1/100, or 2^{−25}, or 2^{−50}, or 2^{−80}, or 2^{−160}, or some other value). Some or all of the techniques used for validity proofs can also be used for invalidity proofs and vice versa. The CA, the directories, and the systems 110 may include softwareprogrammable or hardwired computer systems interconnected via a network or networks. Each function ƒ or H represents an evaluation method performed by a computer system. The invention is not limited to the step sequences shown in the flowcharts, as the step order is sometimes interchangeable and further different steps may be performed in parallel. Other embodiments and variations are within the scope of the invention, as defined by the appended claims.
REFERENCES

[0185]
All of the following references are incorporated herein by reference.
 [1] W. Aiello, S. Lodha, and R. Ostrovsky. Fast digital identity revocation. In Proc. of CRYPTO '98, 1998.
 [2] G. Ateniese, J. Camenisch, M. Joye, and G. Tsudik. A Practical and Provably Secure CoalitionResistant Group Signature Scheme. In Proceedings of CRYPTO 2000, 2000.
 [3] M. Bellare and P. Rogaway. Random oracles are practical: A paradigm for designing efficient protocols. In Proc. First Annual Conference on Computer and Communications Security, ACM, 1993.
 [4] D. Boneh, B. Lynn, and H. Shacham. Short signatures from the Weil pairing. In Proceedings of Asiacrypt '01, 2001.
 [5] F. Elwailly and Z. Ramzan. QuasiModo: More Efficient Hash TreeBased Certificate Revocation. Manuscript, 2003.
 [6] I. Gassko, P. S. Gemmell, and P. MacKenzie. Efficient and fresh certification. In Proceedings of PKC 2000, 2000.
 [7] S. Goldwasser, S. Micali, and R. L. Rivest. A Digital Signature Scheme Secure Against Adaptive ChosenMessage Attacks. SIAM Journal on Computing, 17(2):281308, 1988.
 [8] YC. Hu, A. Perrig, and D. Johnson. Efficient security mechanisms for routing protocols. In proceedings of the 10th Annual Network and Distributed System Security Symposium (NDSS), 2003.
 [10] M. Jakobsson, JP. Hubaux, and L. Buttyan. A micropayment scheme encouraging collaboration in multihop cellular networks. In Proceedings of the 7th International Conference on Financial Cryptography, 2003.
 [10] M. Jakobsson, T. Leighton, S. Micali, and M. Szydlo. Fractal merkle tree representation and traversal. In Proceedings of the Cryptographer's Track, RSA Conference., 2003.
 [11] S. Jarecki and A. Odlyzko. An efficient micropayment system based on probabilistic polling. In Proceedings of the 1st International Conference on Financial Cryptography, 1997.
 [12] Robert Johnson, David Molnar, Dawn Xiaodong Song, and David Wagner. Homomorphic signature schemes. In CTRSA, pages 244262, 2002.
 [13] C. Jutla and M. Yung. PayTree: Amortized signatures for flexible micropayments. In Proceedings of the second USENIX workshop on electronic commerce, 1996.
 [14] S. Kim and H. Oh. An atomic micropayment system for a mobile computing environment. IEICE Transactions of Information and Systems, E84D(6):709716, 2001.
 [15] P. Kocher. On Certificate Revocation and Validation. In Proceedings of the 2nd International Conference on Financial Cryptography, 1998.
 [16] Satoshi Koga and Kouichi Sakurai. A distributed certificate status protocol with single public key. In Proceedings of PKC 2004, pages 389401, 2004.
 [17] R. J. Lipton and R. Ostrovsky. MicroPayments via Efficient Coin Flipping. In Proceedings of the 2nd International Conference on Financial Cryptography, 1998.
 [18] A. Malpani, R. Housely, and T. Freeman. Simple Certificate Validation Protocol—(SCVP). In IETF Draft—draftietfpkixscvp12.txt, June 2003.
 [19] R. C. Merkle. Protocols for PublicKey Cryptography. In IEEE Symposium on Security and Privacy, 1980.
 [20] S. Micali. Efficient Certificate Revocation. MIT/LCS/TM 542b, Massachusetts Institute of Technology, 1996.
 [21] S. Micali. Efficient Certificate Revocation. In Proceedings of the RSA Data Security Conference, 1997. Also U.S. Pat. No. 5,666,416.
 [22] S. Micali. NOVOMODO: scalable certificate validation and simplified PKI management. In Proceedings of the 1st Annual PKI Research Workshop, 2002.
 [23] M. Myers, R. Ankney, A. Malpani, S. Galperin, and C. Adams. X.509 internet public key infrastructure Online Certificate Status Protocol—OCSP. In Internet RFC 2560, June 1999.
 [24] M. Naor and K. Nissim. Certificate Revocation and Certificate Update. In Proceedings of USENIX Security, 1998.
 [25] National Bureau of Standards. NBS FIPS PUB 81: DES modes of operation. 1980.
 [26] National Institute of Standards. FIPS 1801: Secure hash standard. 1995.
 [27] M. Pierce and D. O'Mahony. Micropayments for Mobile Networks. In Proceedings of European Wireless, 1999. Winner of Best Paper Award.
 [28] R. L. Rivest. The MD5 message digest algorithm. In Internet RFC 1321, April 1992.
 [29] R. L. Rivest. Electronic Lottery Tickets as Micropayments. In Proceedings of the 2nd International Conference on Financial Cryptography, 1997.
 [30] R. L. Rivest and A. Shamir. PayWord and MicroMint—Two Simple Micropayment Schemes. CryptoBytes (RSA Laboratories), 2(1), 1996. Proceedings of 1996 International

[0216]
Workshop on Security Protocols.
 [31] R. L. Rivest, A. Shamir, and L. Adleman. A Method for Obtaining Digital Signatures and PublicKey Cryptosystems. Communications of the ACM, 21:120126, 1978.
 [32] Ron Steinfeld, Laurence Bull, and Yuliang Zheng. Content extraction signatures. In Proceedings of the 4th International Conference Seoul on Information Security and Cryptology, pages 285304. SpringerVerlag, 2002.
 [33] H. Tewari and D. O'Mahony. Multiparty Micropayments for AdHoc Networks. In Proceedings of the IEEE Wireless Communications and Networking Conference (WCNC), 2003.
 [34] H. Tewari and D. O'Mahony. RealTime Payments for Mobile IP. IEEE Communications, 41(2):126 136, 2003.
 [35] D. Wheeler. Transactions Using Bets. In Proceedings of Fourth Cambridge Workshop on Security Protocols, 1996.
 [36] J. Zhou and KY. Lam. Undeniable Billing in Mobile Communication. In Proceedings of MOBICOM, 1998.
 [37] M. Goodrich, R. Tamassia. An Efficient Dynamic and Distributed Cryptographic Accumulator. 2001.
 [38] J. Benaloh and M. de Mare. OneWay Accumulators: A Decentralized Alternative to Digital. Signatures.
 [39] J. Camenisch and A. Lysyanskaya. Dynamic Accumulators and Application to Efficient Revocation of Anonymous Credentials. 2002.
 [40] S. Gokhale and P. Dasgupta. Distributed Authentication for PeertoPeer Networks. Symposium on Applications and the Internet Workshops (SAINT'03 Workshops), 2003.
 [41] O. Goldreich, S. Micali, A. Wigderson. Proofs that Yield Nothing But their

[0228]
Validity and a Methodology of Cryptographic Protocol Design. Extended Abstract, 27th FOCS, 1986 (IEEE).
 [42] O. Goldreich and A. Kahan. How to Construct ConstantRound ZeroKnowledge Proof Systems for NP. Journal of Cryptology, Volume 9, No. 3, 1996, pages 167190.
Appendix A
Accumulators and Proofs of Knowledge

[0230]
Definition (Secure Accumulator).

[0231]
A secure accumulator for a family of inputs {XX_{k}} is a family of families of functions GG={FF_{k}} with the following properties:

[0232]
Efficient generation: There is an efficient probabilistic algorithm G that on input 1^{k }produces a random element f of {FF_{k}}. G also outputs some auxiliary information about f, denoted by aux_{f}.

[0233]
Efficient evaluation: f∈{FF_{k}} is a polynomialsize circuit that, on input (u, x)∈UU_{f}x XX_{k}, outputs a value v∈UU_{f}, where UU_{f }is an efficientlysamplable input domain for the function f, and {XX_{k}} is the intended input domain whose elements are to be accumulated.

[0234]
Quasicommutative: For all k, for all f∈FF_{k}, for all u∈UU_{f}, for all x_{1}, x_{2}∈XX_{k}, f(f(u, x_{1}), x_{2})=f(f(u, x_{2}), x_{1}). If X={x_{1}, . . . , x_{m}}⊂XX_{k}, then by f(u, X) we denote f(f(. . . (u, x_{1}), . . . ).

[0235]
Witnesses: Let v∈UU_{f }and x∈XX_{k}. A value w∈UU_{f }is called a witness for x in v under f if v=f(w, x).

[0236]
Security: Let UU′_{f }x XX′_{k }denote the domains for which the computational procedure for function f∈FF_{k }is defined (thus UU_{f} ⊂UU′_{f}, XX_{k} ⊂XX′_{k}). For all probabilistic polynomialtime adversaries A_{k},

[0000]
Pr[f←G(1^{k}); u←UU _{f}, (x, w, X)←A _{k}(f, UU _{f}, u) : X∈XX _{k} ; w∈UU _{f}′; x∈XX _{k} ; x∉X; ƒ(w, x)=ƒ(u, X)] −neg(k).

[0237]
Camenisch and Lysyanskaya ([39]) define the notion of a dynamic accumulator:

[0238]
Definition (Dynamic Accumulator).

[0239]
A secure accumulator is dynamic if it has the following property:

[0240]
Efficient Deletion: There exist efficient algorithms D and W such that, if v=f(u, X), x, x′∈X, and f(w, x)=v, then:

[0000]
D(aux_{f} , v, x′)=v′ such that v′=f(u, X−{x′}) and

[0000]
W(f, v, v′, x, x′)=w′ such that f (w′, x)=v′.

[0241]
ZeroKnowledge Proofs. An advantage of accumulators (at least, RSAbased accumulators, which are described later) is that it is possible to construct efficient zeroknowledge proofs (ZK proofs) that a value has been accumulated. It has been proven that any statement that is in NP (nondeterministic polynomialtime) can be proven in ZK, but some statements can be proven in ZK much more efficiently than others. Briefly, we describe the concept of a ZK proof, which was introduced independently by Brassard, Chaum, and Crepeau and by Goldwasser, Micali, and Racko, and further refined by Bellare and Goldreich.

[0242]
Let x be an input, and let R be a polynomially computable relation. Roughly speaking, a zeroknowledge proof of knowledge of a witness w such that R(x, w)=1 is a probabilistic polynomialtime protocol between a prover P and a verifier V such that, after the protocol, V is convinced that P knows such a witness w, but V does not obtain any explicit information about w. In other words, apart from “proving” that it knows a witness w such that R(x, w)=1, P imparts “zero knowledge” to V.

[0243]
In the sequel, we may use the notation introduced by Camenisch and Stadler for various proofs of knowledge of discrete logarithms and proofs of the validity of statements about discrete logarithms. For instance,

[0000]
PK {(α, β, γ):
y=g ^{α} h
^{β} =g′
^{α} h′
^{γ} (
u≦α≦v)}

[0000]
denotes a zeroknowledge Proof of Knowledge of integers α, β, and γ such that y=g^{α} h^{β} and y′=g′^{α} h′^{γ}, where u≦α≦v and where g, g′, h, h′, y, and y′ are elements of some groups G=<g>=<h> and G′=<g′>=<h′>. The convention is that Greek letters denote quantities the knowledge of which is being proved, while all other parameters are known to the verifier. Using this notation, a proofprotocol can be described by just pointing out its aim while hiding all details.

[0244]
Often, these proofs of knowledge are instantiated by a threepass protocol, in which the prover first sends the verifier a commitment to certain values, after which the verifier sends the prover a challenge bitstrings, and the prover finally sends a response that incorporates both the “known value”, the committed values and the challenge value in such a way that it convinces the verifier is convinced of the prover's knowledge.

[0245]
These proofs of knowledge can be turned into signature schemes via the FiatShamir heuristic. That is, the prover determines the challenge c by applying a collisionresistant hash function H to the commitment and the message m that is being signed and then computes the response as usual. We denote such signature proofs of knowledge by the notation, e.g., SPK {α:y=ƒ(α)}(m). Such SPK's can be proven secure in the random oracle model, given the security of the underlying proofs of knowledge.

[0246]
ZK proofs are often accomplished with the help of a commitment scheme. A commitment scheme consists of the algorithms Commit and VerifyCommit with properties as follows. The commitment algorithm Commit takes as input a message m, a random string r and outputs a commitment C, i.e., C=Commit(m,r). The (commitment) verification algorithm VerifyCommit takes as input (C, m, r) and outputs 1 (accept) if C is equal to Commit(m,r) and 0 (reject) otherwise. The security properties of a commitment scheme are as follows. The hiding property is that a commitment C=Commit(m, r) contains no (computational) information on m. The binding property is that given C, m, and r, where 1 =VerifyCommit(C,m,r), it is (computationally) impossible to find a message m_{0 }and a string r_{0 }such that 1 =VerifyCommit(C, m_{0}, r_{0}).

[0247]
To prove, in ZK, knowledge of a witness w of a value x that has been accumulated—i.e., that f(w, x)=v, where v is the accumulator value—the usual method is to choose a random string r and construct a commitment c=Commit(x, r) and then provide the following proof of knowledge:

[0000]
PK{(α, β, γ):
c=Commit(α, γ)
ƒ(γ,α)=
v}.

[0248]
Above α represents the (hidden) x value, while β represents r and γ represents w.

[0249]
RsaBased Accumulators.

[0250]
Here we describe a common concrete instantiation of accumulators, which uses mathematics related to the wellknown RSA publickey cryptosystem, invented by Rivest, Shamir and Adleman in 1977. Above, our description focused on some RSAbased instantiation of accumulators, but this description should not be considered limiting; our accumulatorbased certificate revocation schemes could be used with any type of accumulators. An accumulator structure has an advantage that its size does not depend on the number of accumulated elements. An RSAbased accumulator makes use of a composite integer n, called a modulus, that should be chosen in such a way that it is hard to factor. In some embodiments of the schemes defined above, the modulus is an RSA modulus, which is defined as follows:

[0251]
Definition (RSA modulus). A 2k bit number n is called an RSA modulus if n=pq, where p and q are kbit prime numbers.

[0252]
Of course, one can choose n in a different way—e.g., as the product of three primes, or as the product of two primes of different sizes.

[0253]
Definition (Euler totient function). Let n be an integer. The Euler totient function φ(n) is the cardinality of the group Z_{n} ^{* }(the multiplicative group of elements having an inverse in the ring Z_{n }of the integers modulo n; Z_{n} ^{* }is the set of all elements mutually prime with n).

[0254]
If n=pq is the product of two primes, then φ(n)=(p−1)(q−1).

[0255]
The security of RSAbased accumulators is based on the following assumption.

[0256]
Definition (Strong RSA Assumption) The strong RSA assumption is that it is “hard,” on input an RSA modulus n and an element u∈Z_{n} ^{*}, to compute values e>1 and v such that v^{e}=u(mod n). By “hard”, we mean that, for all polynomialtime circuit families {A_{k}}, there exists a negligible function neg(k) such that

[0000]
Pr[n←RSAmodulus(1^{k}); u←Z _{n} ^{*}; (v, e)←A _{k}(n, u): v ^{e}=u(mod n)]=neg(k),

[0000]
where RSAmodulus(1^{k}) is an algorithm that generates an RSA modulus as the product of two random kbit primes, and a negligible function neg(k) is a function such that for all polynomials p(k), there is a value k_{0 }such that neg(k)<1/p(k) for all k>k_{0}. The tuple (n, u) generated as above, is called a general instance of the strong RSA problem.

[0257]
Corollary 1. Under the strong RSA assumption, it is hard, on input a flexible RSA instance (n, u), to compute integers e>1 and v such that v^{e}=u(mod n).

[0258]
The most common concrete instantiation of accumulators is based on the above strongRSA assumption. Roughly speaking, the idea is as follows: Given a fixed base u(mod n), one can compute an accumulator of values x_{1 }and x_{2 }(for example) as v=u^{x} ^{ 1 } ^{x} ^{ 2 }(mod n). To prove that x_{1 }(for example) has been accumulated, one can forward the witness w=u^{x} ^{ 2 }(mod n) and a verifier can confirm that indeed w^{x} ^{ 1 }(mod n).

[0259]
Now, we relate the formal description of accumulators to the concrete RSAbased construction. A secure RSAbased accumulator for a family of inputs X_{k }is a family of functions FF_{k}, where the particular function f∈FF_{k }depends on what the modulus n is. For reasons that will become clear later, we assume that elements of X_{k }are pairwise relatively prime integers. Then, aux_{f }is the (secret) factorization of n. As alluded to above, given an initial accumulator value v′, an additional value x is added to the accumulator by computing a new accumulator value v=v′^{x }(mod n). Notice that the computational complexity of this algorithm is independent of the number of prior values that have been accumulated. The RSAbased accumulator possesses the quasicommutative property; e.g., regardless of the order in which x_{1 }and x_{2 }are incorporated into an initial accumulator v′, the result is v=v′^{x} ^{ 1 } ^{x} ^{ 2 }(mod n). Given an accumulator v(mod n), the witness that a value x has been accumulated is w=v^{1/x }(mod n), which can readily be verified by confirming that v=w^{x}(modn). To reiterate, the security of the construction is based on the assumption that the strong RSA problem is infeasible to solve.

[0260]
RSAbased accumulators can be made dynamic. Recall that an accumulator is dynamic if, given an accumulator v that accumulates values of the set X and given the secret information aux_{f}, one can “deaccumulate” a value x′∈X—i.e., compute a new accumulator v′ that accumulates the values of the set X−{x′}. Moreover, given a witness w that a value x has been accumulated (with respect to accumulator v that accumulates members of the set X) and given the accumulator v′ that only accumulates members of X−{x′}, one can compute a new witness w′ for x with respect to the accumulator v′. Specifically, for RSAbased accumulators, one can use the factorization of n to deaccumulate x′ by computing v′=v^{1/x′}(mod n). And given a witness w for x with respect to v—i.e., w^{x}=v(mod n)—and given the value of v′, one can compute a witness w′ for x with respect to v′—i.e., w′^{x}=v′=v′^{1/x′}(mod n)←w′=v′^{1/xx′}(mod n) as follows. Assuming that x and x′ are relatively prime, one can compute integers (a, b) such that ax+bx′=1, by using the Extended Euclidean Algorithm. Then w′=v′^{a}w^{b}=v^{a/x′}v^{b/x}=v^{(ax+bx′)/xx′}=v^{1/xx′}(mod n). Notice that the computation of w′ is efficient, and (after v′ is computed) it doesn't require any secret knowledge (e.g., the factorization of n).

[0261]
Given a witness w that a value x is accumulated (with respect to an accumulator v(mod n)), it also wellknown in the art how to construct a ZK proof of knowledge of a pair (w, x) that satisfies w^{x}=v(mod n) (that hides the values of both w and x from the verifier).
End of Appendix A
APPENDIX B
GuillouQuisquater (GQ) IDbased Signature Scheme

[0262]
SetUp:

[0263]
1. A public key generator (PKG, a trusted party), publishes its public key (v, n) where n=q_{1}q_{2 }(a product of two primes) is such that its factorization is hard to find, and v is a prime less than φ(n)=(p−1)(q−1).

[0264]
2. For a user with an identity ID (e.g., an email address), the PKG computes the secret signing key B such that JB^{v}=1 mod n, where J=R(ID), where R is a predefined public function, e.g. a redundancy function. In some embodiments, the function R maps ID into an element of Z_{n}. The function R is such that the number of elements in Z_{n }that correspond to mappings from valid ID's is small. The PKG sends B to the user via a secure channel (e.g. encrypted).

[0265]
Signing: To sign a message M, the user:
 1. Computes J=R(ID)
 2. Generates a random number r and computes

[0000]
d=H(M∥r ^{v}), D=rB ^{d } (B1)

[0000]
where H is a predefined public function (e.g. a hash function).
 3. Sends the values M, r^{v}, d, D to the verifier.

[0269]
Verification: The verifier:
 1. Computes J=R(ID);
 2. Checks that d=H(M∥r^{v});
 3. Checks that J^{d}D^{v}=r^{v}.
End of Appendix B