User doesn’t need to backup the ID keys, since he
can regenerate them anytime. If user loses the device,
ID key is gone, but he can generate the same ID key
again. Others who illegally gets the device cannot use
the ID private key, if they cannot pass the access con-
trol. If user bought a new device, he can register it
with a proper name and install ID private key into the
device by himself. If user does not need to distin-
guish device name, he can use the same device name
in multiple devices.
In the point of managing others’ key, user doesn’t
need to manage opponent’s device key, but only needs
to manage the certificate of opponent. Though we are
considering multiple user device scenario, the number
of keys that user has to manage is not much different
from the single device situation.
Validity Period of ID Keys. In traditional ID-based
cryptosystems it is hard to set validity period to ID
key. To achieve this, ID key was sometimes set in-
cluding explicit validity period in ID information. But
in the proposed scheme ID private key was derived
from the certified key of the user and is always used
together with it that its validity is highly coupled to
the validity of the certified public key. If user has re-
newed certificate and got a new certified key pair, the
ID private keys also have to be renewed using the new
certified private key. Thus the device ID keys have the
inherent validity period which is equal to that of the
certificate.
Same ID Public Key in Certificate Renewal. Cer-
tificate has to be renewed periodically using a new
key pair and in this case ID keys also have to be re-
newed. But note that ID public key, for example,
A.M
i
can remain the same though ID private key has
to be changed. Since ID is a kind of persistent in-
formation advertised to others, this property is a big
advantage of the proposed key management system
compared with the traditional certificate-based sys-
tem. This property is very useful specially for login
management where login ID to service should be per-
sistent for long time.
Easy Adaptation/transition. In the proposed key
management scheme certificate issuing for user (by
CA) and personal key management for user devices
(by user) are independent. Existing PKI systems,
mainly based on RSA signature, can be used for the
proposed scheme without big change with the only
condition that user’s long-term key should be pairing-
based. All ID-based functions such as device key
management and secure communication will be im-
plemented in user-side systems. Thus, it is expected
that the transition from current PKI-based systems
to the proposed hybrid-style key management system
can be easy and smooth.
Offline PKMS. PKMS needs to be connected to
the Internet only during the certificate issuing stage.
Once it acquired the certificate, it can be maintained
in offline state or local communication state in per-
sonal area network (PAN). Since PKMS is used only
for device registration, it can be switched off if de-
vice registration is finished. Thus PKMS can be main-
tained safely against various online attacks.
3.2 Comparison with Chen et al.’s
Scheme
If we compare our proposal with the PKI-IBE hybrid
scheme of Chen et al. (Chen, Harrison, Moss, Sol-
dera & Smart, 2002), both schemes use similar hybrid
approach of certificate-based and ID-based cryptog-
raphy, but application scenario is different. Chen et
al.’s scheme applied the hybrid approach to user au-
thentication in public sector while our proposal is an
application to personal key management for multiple
user devices in ubiquitous computing environment.
Chen et al.’s scheme is not practical in the sense
that it requires user’s full trust to the KGC. In our pro-
posal PKMS and devices are owned by the same user
and personal key management is a highly trusted en-
vironment that we don’t need to worry about the key
escrow problem of the ID-based cryptography. For
real world deployment Chen et al.’s scheme requires
a severe change to the existing PKI mechanism, re-
placing end CA to KGC, but our proposal does not
require big change in PKI.
3.3 Efficiency Analysis
User is using multiple devices with different ID keys,
but he only needs to take good care of the certified pri-
vate key, thus the proposed scheme provides great ef-
ficiency in key management. In the proposed system
the certified private key is used only for generating
ID private keys for user devices, normally not used
for everyday secure communications between users,
which results that the number of key usage is reduced
a lot and key is less exposed to attack. If certificate
becomes a stable one and revocation occurs less fre-
quently, then the cost of operating CRL mechanism
will be reduced a lot. In this case certificate can be
issued with longer validity period.
Finally, we need to compare the efficiency of
the proposed hybrid-style personal key management
scheme with the more typical approach of using cer-
tificates instead of ID keys. In this case user has to
take care of the following drawbacks of certificate-
based systems.
SECRYPT2014-InternationalConferenceonSecurityandCryptography
242