2008
DOI: 10.1016/j.ins.2007.08.004
|View full text |Cite
|
Sign up to set email alerts
|

Three weaknesses in a simple three-party key exchange protocol

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
45
0

Year Published

2008
2008
2017
2017

Publication Types

Select...
7
2

Relationship

0
9

Authors

Journals

citations
Cited by 65 publications
(45 citation statements)
references
References 16 publications
0
45
0
Order By: Relevance
“…Actually, many previous cryptographic schemes containing only informal arguments for security were subsequently shown to be insecure, e.g. [33][34][35][36][37]. Therefore, based on the results listed in the table, we conclude that our scheme is more practical than the related schemes for the users of mobile devices.…”
Section: Instantiationmentioning
confidence: 71%
“…Actually, many previous cryptographic schemes containing only informal arguments for security were subsequently shown to be insecure, e.g. [33][34][35][36][37]. Therefore, based on the results listed in the table, we conclude that our scheme is more practical than the related schemes for the users of mobile devices.…”
Section: Instantiationmentioning
confidence: 71%
“…It helps in maintaining a secure link by using a common session key for specific communication. Schemes [5][6][7] discuss secure session key establishment between participants but later [8][9][10] identified that these plans are vulnerable to man-in-the-middle attack and undetectable online and offline dictionary attacks for guessing passwords. ECC-based schemes are also explored to evaluate the applicability of efficient solutions with desired security strengths using small key sizes as compared to preliminaries.…”
Section: Introductionmentioning
confidence: 99%
“…A number of three-party PAKE protocols have been proposed over the last decade [2,3,5,6,[11][12][13][14][15][16][17][18][19][20][21][22][23][24][25]. Many of these protocols have never been proven secure in any model [3,13,[17][18][19][20][21] and/or have been found to be vulnerable to some attack(s) [2,3,5,6,8,[18][19][20]23,[26][27][28][29][30][31][32].…”
Section: Introductionmentioning
confidence: 99%
“…Many of these protocols have never been proven secure in any model [3,13,[17][18][19][20][21] and/or have been found to be vulnerable to some attack(s) [2,3,5,6,8,[18][19][20]23,[26][27][28][29][30][31][32]. Some protocols [2,11,12,15,23,24] have been proven secure only in a restricted model, in which the adversary is not allowed to corrupt protocol participants, and thus, no attacks by malicious clients can be captured.…”
Section: Introductionmentioning
confidence: 99%