2017
DOI: 10.1155/2017/7810352
|View full text |Cite
|
Sign up to set email alerts
|

Deniable Key Establishment Resistance against eKCI Attacks

Abstract: In extended Key Compromise Impersonation (eKCI) attack against authenticated key establishment (AKE) protocols the adversary impersonates one party, having the long term key and the ephemeral key of the other peer party. Such an attack can be mounted against variety of AKE protocols, including 3-pass HMQV. An intuitive countermeasure, based on BLS (Boneh-Lynn-Shacham) signatures, for strengthening HMQV was proposed in literature. The original HMQV protocol fulfills the deniability property: a party can deny it… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2019
2019
2021
2021

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 41 publications
0
2
0
Order By: Relevance
“…The extended version of these protocols cannot withstand the extended KCI (eKCI) 38 . Table 1 shows that the mHMQV‐1 76 protocol can provide AKC; however, it is higher than that of the proposed protocol in terms of communication and computation complexities. The YAK protocol has a comparable performance with the proposed protocol as shown in Table 1.…”
Section: Security and Performance Comparisonsmentioning
confidence: 99%
“…The extended version of these protocols cannot withstand the extended KCI (eKCI) 38 . Table 1 shows that the mHMQV‐1 76 protocol can provide AKC; however, it is higher than that of the proposed protocol in terms of communication and computation complexities. The YAK protocol has a comparable performance with the proposed protocol as shown in Table 1.…”
Section: Security and Performance Comparisonsmentioning
confidence: 99%
“…Many other variants of HMQV have been proposed in the literature. [24][25][26][27][28][29] In the literature, there is an alternative method to ensure the authentication of the secret key by incorporating the one-way functions in the DH key agreement protocol 12,[30][31][32][33][34][35] in order to confirm the validity of the shared secret key.…”
mentioning
confidence: 99%