approaches lie somewhere between the key transport
and key agreement categories
1
. Furthermore, most, if
not all, have been derived from modifications of pre-
existing x-round protocols.
Almost all one-pass approaches belong to the cat-
egory of authenticated key establishment (AK) proto-
cols, because they provide implicit key authentication
(IKA), meaning that the two (uncorrupted) parties us-
ing the protocol are assured that no one else can pos-
sibly learn the value of their session key. On the other
hand, one-pass protocols cannot achieve known key
security (K-KS) because an adversary can simply re-
play a previous protocol run that he has managed to
record; nor can they provide perfect forward secrecy
(PFS) because there can be no protocol for implicit
authentication that achieves PFS with two or fewer
messages (Krawczyk, 2005). Finally, one-pass ap-
proaches are prone to key-compromise impersonation
(K-CI) attacks, in a number of ways which will be
discussed shortly.
Arguably, protocol designers are often more con-
cerned with PFS, and seem to ignore K-CI (Strangio,
2006). However, K-CI can potentially have more seri-
ous consequences: besides reading past or future con-
versations, an attacker would also be able to elicit ad-
ditional information that may never have been com-
municated otherwise, by masquerading as a different
honest principal. Because of this, it is our opinion
that more emphasis should be given on a protocol
being K-CI–resistant. In this paper, we discuss and
demonstrate a series of impersonation attacks that af-
fect one-pass key establishment protocols, after a key-
compromise has occurred. We also examine the use
of time-stamps and standard digital signatures for the
purpose of withstanding certain types of K-CI attacks.
To the best of our knowledge, this is the first detailed
study of such attacks on one-pass key establishment
protocols.
The remainder of this paper is organized as fol-
lows: In Section 2 we fix notation and review some
required definitions. Section 3 describes some of
the best known one-pass two-party key establishment
protocols. Section 4 discusses the K-CI vulnerability
vis-a-vis a series of important and widely-used appli-
cations, and describes two basic types of K-CI attacks
and possible responses.
1
For this reason, it seems more appropriate to speak of
one-pass key establishment as opposed to key agreement, as
is done in most of the literature.
2 NOTATION AND PRIMITIVES
The protocols described in the next Section can be
defined over any finite commutative group G of order
n, that comes equipped with a difficult discrete log-
arithm problem. Throughout this paper we consider
asymmetric protocols based on elliptic curve cryp-
tosystems (G will be the group of points on an ellip-
tic curve), and we will use additive representation for
group operations (Kaliski, 2001). We will let P de-
note a generator of G, and will assume that G, P and
n are fixed and known in advance to the parties. We
will write cP to denote scalar multiplication, where
c ∈ Z
∗
n
.
The security of the protocols discussed next is
linked to the following problems, whose solution is
assumed to be difficult to compute in polynomial
time:
Definition 1 Discrete Log Problem (DLP)
Given P, Q ∈ G, find an integer a ∈ Z
∗
n
such that Q =
aP ∈ G.
Definition 2 Computational Diffie-Hellman Prob-
lem (CDHP)
Given P,aP,bP ∈ G, for some unknown a, b ∈ Z
∗
n
, find
abP ∈ G.
In the following we will apply hash functions and
signature schemes to lists of several arguments. In
such cases, we are going to write function arguments
separated by commas, e.g., example H(X,Y,Z). By
doing so, we assume that we have a collision-free
encoding which maps lists of arguments to binary
strings, and that the parties’ identities are arbitrary bi-
nary strings.
An entity, say
ˆ
A , participating in a protocol is
assigned a static key pair (a, A) which consists of a
public and a private key. Public keys (denoted by up-
per case letters) are elements of G, while private keys
(denoted by the corresponding lower case letters) are
elements of Z
∗
n
. For example, the private key a may
correspond to the public key A = aP.
Public keys are registered with a trusted directory,
called the certificate authority (CA). The CA regis-
ters arbitrary keys with the restriction that no party
can have more than one registered public key. We as-
sume that all honest parties have a priori generated
their public keys and have registered them with the
CA, so that they can be known to and verified by other
parties during protocol execution.
Table 1 lists the notation used throughout the pa-
per.
ON THE KEY-COMPROMISE IMPERSONATION VULNERABILITY OF ONE-PASS KEY ESTABLISHMENT
PROTOCOLS
223