Identity-based fault tolerant conference key agreement
Yi, Xun (2004) Identity-based fault tolerant conference key agreement. IEEE transactions on dependable and secure computing, 1 (3). pp. 170-178. ISSN 1545-5971Full text for this resource is not available from the Research Repository.
Lots of conference key agreement protocols have been suggested to secure computer network conference. Most of them operate only when all conferees are honest, but do not work when some conferees are malicious and attempt to delay or destruct the conference. Recently, Tzeng proposed a conference key agreement protocol with fault tolerance in terms that a common secret conference key among honest conferees can be established even if malicious conferees exist. In the case where a conferee can broadcast different messages in different subnetworks, Tzeng’s protocol is vulnerable to a “different key attack” from malicious conferees. In addition, Tzeng’s protocol requires each conferee to broadcast to the rest of the group and receive n 1 messages in a single round (where n stands for the number of conferees). Moreover, it has to handle n simultaneous broadcasts in one round. In this paper, we propose a novel fault-tolerant conference key agreement protocol, in which each conferee only needs to send one message to a “semitrusted” conference bridge and receive one broadcast message. Our protocol is an identity-based key agreement, built on elliptic curve cryptography. It is resistant to the different key attack from malicious conferees and needs less communication cost than Tzeng’s protocol.
|Uncontrolled Keywords:||Computer network conference, conference key agreement, fault tolerance, semitrusted, passive and active attacks|
|Subjects:||Faculty/School/Research Centre/Department > School of Engineering and Science
RFCD Classification > 280000 Information, Computing and Communication Sciences
|Depositing User:||Ms Phung T Tran|
|Date Deposited:||20 Oct 2008 00:35|
|Last Modified:||15 Oct 2010 23:24|
|ePrint Statistics:||View download statistics for this item|
|Citations in Scopus:||9 - View on Scopus|
Repository staff only