| Literature DB >> 23844397 |
Peng Jiang1, Qiaoyan Wen, Wenmin Li, Zhengping Jin, Hua Zhang.
Abstract
With advancement of computer community and widespread dissemination of network applications, users generally need multiple servers to provide different services. Accordingly, the multiserver architecture has been prevalent, and designing a secure and efficient remote user authentication under multiserver architecture becomes a nontrivial challenge. In last decade, various remote user authentication protocols have been put forward to correspond to the multi-server scenario requirements. However, these schemes suffered from certain security problems or their cost consumption exceeded users' own constrained ability. In this paper, we present an anonymous remote user authentication with key agreement scheme for multi-server architecture employing self-certified public keys without pairings. The proposed scheme can not only retain previous schemes' advantages but also achieve user privacy concern. Moreover, our proposal can gain higher efficiency by removing the pairings operation compared with the related schemes. Through analysis and comparison with the related schemes, we can say that our proposal is in accordance with the scenario requirements and feasible to the multi-server architecture.Entities:
Mesh:
Year: 2013 PMID: 23844397 PMCID: PMC3691932 DOI: 10.1155/2013/419592
Source DB: PubMed Journal: ScientificWorldJournal ISSN: 1537-744X
Notations used in proposed scheme.
| Notations | Descriptions |
|---|---|
| RC | The registration center |
|
| The |
|
| The |
|
| The private key of RC |
| SID | The identity of |
| ID | The identity of |
|
| A generator of group |
|
| A one-way hash function |
| PW | The password of |
| SK | A session key shared between |
|
| The secret value maintained by RC |
| ⊕ | A simple Exclusive-OR operation |
| || | The concatenation operation |
Figure 1The proposed scheme.
Functionality and security comparison with the related schemes.
| Functionality | Ours | [ | [ | [ | [ | [ | [ |
|---|---|---|---|---|---|---|---|
| No repetitive registration | Y | Y | Y | Y | Y | Y | Y |
| No verification table | Y | Y | Y | Y | Y | Y | Y |
| Mutual authentication with key agreement | Y | Y | N | N | Y | N | N |
| No synchronization clock | Y | Y | N | Y | Y | N | Y |
| Change password freely | Y | Y | Y | Y | Y | Y | Y |
| Anonymity | Y | N | N | Y | Y | Y | Y |
| Perfect forward and backward secrecy | Y | Y | N | N | Y | N | N |
| No key control | Y | Y | Y | Y | Y | Y | Y |
| Known session key security | Y | Y | Y | Y | Y | Y | Y |
| Impersonation attack | Y | N | N | N | N | N | N |
| Stolen smart card attack | Y | Y | N | N | N | N | N |
| Off-line password guessing attack | Y | N | N | Y | N | N | N |
| Man-in-the-middle attack | Y | Y | N | Y | Y | N | N |
| Server spoofing attack | Y | N | N | Y | Y | Y | N |
| Local password verification | Y | N | N | Y | Y | Y | Y |
Cost comparison with the related schemes.
| Phase | Ours | [ | [ |
|---|---|---|---|
| Server registration | 5 | 5 | — |
| User registration | 2 | 3 | 3 |
| Login |
| 3 | 3 |
| Verification | 9 | 2 | 2 |
| Password change | 2 | 2 | 2 |
|
| |||
| Total | 19 | 4 | 2 |
Figure 2Performance comparison between our scheme and others.