
 
A Certification Authority (CA) has a key pair 
},{ PKSK
, where 
>=< ndSK ,
 
is used to sign all MN certificates. Any certificate in this approach can be verified by 
the system public key 
SK
, that is know by ever MN in the network. 
According to threshold cryptography, 
SK
 is divided in the network. Every MN 
i
v
, besides its own key pair, has the partial key 
vi
P
. Any subgroup 
k
of 
MN can 
work as a CA. However it is not possible to any MN to know 
SK
, but in the system 
initialization.  
Threshold cryptography is indicated in MANET due to some of its proprieties: (a) 
the distribution and decentralized control of the keys fits the profile of Ad Hoc 
networks, (b) security omnipresence is guaranteed since the secret is fully distributed 
in the network and
 intrusion detection is more practical and efficient, (c) the limit 
k
 
is the balance between the service availability and intrusion tolerance. In other words, 
a group of adversaries need to destroy 
)1( +− kn
 partial key holders to bring the 
system down (once it would block one auto configuration) and at least break 
k
partial 
keys to steal 
SK
 secret.  
System is initialization is a very careful step to 
k
choosing. As lower the 
k
 value 
the greater the facility of break 
SK
 secret. In other hand the greater the value of 
k
 
the higher the system security, which reduces fault tolerance at the same time. After 
all, the most close 
k
 is from 
, the probability of 
)1( +− kn
 MN leaving the network 
raises, which would forbid the service. 
Certificates generated by a CA formed by a subgroup of 
k
 MN have the finality 
of certificate, as in a normal cryptographic system, the public key of every MN. 
Therefore, every MN has its own 
i
cert
 certificate that must be signed by 
SK
, in 
><
iresignii
TTpkv
exp
,,,
 format, where 
i
v
 is the MN identifier, 
i
pk
 is its public 
key, 
sign
T
 is the signature date and 
ire
T
exp
 is the expiration certificate date.  
To control the certificate validity are used to methods: (a) Implicit certificate 
revocation that defines that every MN must renew its certificate at least ever period 
renew
T
 where 
renewsignire
TTT +≤
exp
, (b) explicit certificate revocation where a 
certificate is assumed by Certificate Revocation List (CRL) is not valid anymore even 
its 
ire
T
exp
 is valid. This implies directly that only revoked certificates that did not 
expire must be in CRL. 
This model was implemented in [1] which involves only subgroups, 
k
 size, of 
partial key holders. The basic operations include: (a) secret key negotiation, where the 
secret key can be obtained by on MN with the system initialization or with the auto 
configuration service. In the first case, both keys and certificates are distributed to 
MN by a central negotiator before MANET formation. In the second case, an auto 
initialization algorithm where 
k
 MN can provide a partial key to new MN in the 
network, (b) the secret key update, instead of changing the system key from time to 
time, only changes the partial key with the main purpose of protecting the secret key 
from being broken. The system supports until 
1−k
 partial secret breaks because 
SK
 
is obtained with 
k
 keys. If in a update situation there is less than 
k
 discovered keys, 
SK
 is protected and does not need to be changed, (c) the certification service permits, 
that when a MN requests using the certification service, one subgroup of 
k
 
(coalition) partial secret key holders is created and every MN 
i
v
 generates a partial 
signed certificate to the requesting MN. MN then generates its certificate by grouping 
k
 received certificates that represents a signed certificate from 
SK
. This service 
includes emission, renovation and revocation of certificates, besides, even before the 
MANET formation, a security policy for each step should be defined. 
61