By using Message Authenticate Code (MAC), the
prover can also designate the verifier. MAC is also
verified the validity without interaction. However the
prover and the verifier must share a common secret
key before using MAC. In the DVS system, the signer
can designate the verifier using only the verifier’s pub-
lic key.
In the DVS system, the validity of a signature is
checked by following two procedures: Decision and
Distinction. By Decision, the signature is checked
whether it is “accepted” by the decision procedure.
By Distinction, the signature is checked whether it is
exactly generated by the signer. In this paper, we call
a signature which is accepted by Decision an accept-
able signature, and a signature which is acceptable
signature and generated by the signer a valid signa-
ture. The meaning of verifying the validity of a sig-
nature is confirming that the signature is valid by per-
forming Decision and Distinction.
In the DVS system, the verifier can also generate
an acceptable signature. We call such an acceptable
signature a dummy signature, while we call a signa-
ture generated by a signer an original signature. Only
the original signature must be confirmed as the valid
signature. Any third party should be unable to distin-
guish the original signature from dummy signatures.
Even if a third party accepts a signature, he is unable
to confirm that the signature is the original signature
because it could be a dummy signature. Therefore,
a third party is unable to verify the validity of the
signature. On the other hand, the verifier can decide
whether the signature is the original signature by us-
ing his own list of dummy signatures generated by
himself. Hence, the verifier cannot convince a third
party the validity of the signature.
In several DVS systems (Jakobsson et al., 1996;
Rivest et al., 2001; Lipmaa et al., 2005; Shahandashti
and Safavi-Naini, 2008), anyone can perform the De-
cision. However, a third party cannot confirm the va-
lidity of a signature because he can not perform Dis-
tinction. We call those DVS systems ordinary DVS.
In the ordinary DVS system, a third party can nar-
row the signer to two candidates. On the other hand,
strong DVS (Saeednia et al., 2004; Laguillaumie and
Vergnaud, 2005; Steinfeld et al., 2003) in which only
the verifier can perform the Decision was proposed.
In the strong DVS system, a third party cannot even
narrow two signer candidates.
1.2 A Motivating Problem
In a strong DVS system, all processes of the verifica-
tion can be performed by only a verifier. If one person
is designated by large numbers of signers, he must
proceed large amount of the task of the verification
procedure by himself.
This situation will often occur if the DVS system
is applied to the situation of public procedures. In
this case, a lot of people would send their documents
with DVSs to one government office. Then, the offi-
cer must verify large amount of DVSs. Hence, the of-
ficer would like to entrust other organizations to some
processes of verification.
1.3 Contribution
In order to reduce the computational cost for verifi-
cation, we will propose Proxiable Designated Verifier
Signature (PDVS) where the verifier can make a third
party (i.e. the proxy) substitute some process of the
verification. In previous DVS systems, if the third
party can perform the Decision, but he cannot con-
firm the validity of a signature. Hence in the PDVS
system, the Decision is delegated to the proxy and the
verifier performs only the Distinction. If the verifier
does not issue any dummy signature for message m,
he verifies that (m, σ) is valid immediately when he is
reported that (m, σ) is acceptable by the proxy. Hence
the verifier can reduce his computational cost.
In previous strong DVS systems (Saeednia et al.,
2004; Laguillaumie and Vergnaud, 2005; Steinfeld
et al., 2003), there is only one kind of verifier’s se-
cret key which is used for performing the Decision al-
gorithm and for generating dummy signatures. If the
verifier gives his secret key in order to delegate the
Decision, the proxy can also generate a dummy sig-
nature. In this case, the verifier cannot perform the
Distinction. Thus in the previous strong DVS systems,
the verifier cannot delegate the verification task to the
proxy.
Hence in the PDVS system, there are two kinds of
verifier’s keys; one is a key for performing the Deci-
sion and the other is for generating dummy signatures.
The verifier can delegate the Decision to the proxy by
giving only the secret key for performing the Deci-
sion, and the verifier keeps the both of keys; a key
for performing the Decision and a key for generating
dummy signatures.
Unlike the previous DVS systems, there is the new
entity proxy in the PDVS system. Hence we consider
the requirements for each position, not only the veri-
fier and the third party but also the proxy. We define
security requirements for PDVS scheme by capturing
following requirements. (1) The verifier can surely
verify the validity of the signature at any time. (2) The
proxy can perform the Decision, but cannot generate
any acceptable signature. (3) The third party cannot
perform even the Decision. We describe the definition
PROXIABLE DESIGNATED VERIFIER SIGNATURE
345