A Dynamic ID-based Remote User Authentication Scheme
Password-based authentication schemes are the most widely used techniques for remote user authentication. Many static ID-based remote user authentication schemes both with and without smart cards have been proposed. Most of the schemes do not allow the users to choose and change their passwords, and maintain a verifier table to verify the validity of the user login. In this paper we present a dynamic ID-based remote user authentication scheme using smart cards. Our scheme allows the users to choose and change their passwords freely, and do not maintain any verifier table. The scheme is secure against ID-theft, and can resist the reply attacks, forgery attacks, guessing attacks, insider attacks and stolen verifier attacks.
💡 Research Summary
The paper addresses fundamental weaknesses in existing remote user authentication schemes that rely on static identifiers and server‑maintained verifier tables. Traditional password‑based protocols often require users to accept a fixed password and do not permit easy password changes, while the server stores a verifier (often a hash of the password or a secret) for each user. This design creates several attack surfaces: an adversary who captures a static ID can replay it, a compromised server database reveals verifier information, and insider threats can misuse stored credentials. To overcome these issues, the authors propose a dynamic ID‑based authentication protocol that leverages smart cards as secure hardware tokens.
In the registration phase, each user receives a smart card pre‑loaded with a secret key K (generated by the server) and an initial password P₀ chosen by the user. The server also assigns a unique user identifier ID₀, but it does not store any password‑related verifier. During a login attempt, the smart card generates a fresh random nonce N₁. Using K and N₁, it computes a dynamic identifier ID₁ = H(K‖N₁) and an authentication token C₁ = H(K‖P‖N₁), where H denotes a cryptographic hash function and P is the password entered at login time. The card sends (ID₁, C₁, N₁) to the server. The server, which knows K associated with ID₀, recomputes the same values and verifies that the received C₁ matches its own calculation. If the verification succeeds, the server authenticates the user and may optionally issue a session key derived from K and N₁.
The dynamic identifier changes on every session because it depends on the freshly generated nonce. Consequently, an eavesdropper cannot reuse a previously captured ID or token, effectively neutralizing replay attacks. Moreover, because the password is mixed with the nonce before hashing, offline password‑guessing attacks become infeasible: the attacker would need to know K (which never leaves the smart card) to test any password guess.
Password change is handled without any server‑side password storage. After a successful login, the user may request a password update. The smart card takes the new password P′, recomputes the secret‑derived values (e.g., a new hash of K and P′) and stores P′ internally. The server does not need to be informed of the new password; it continues to use the unchanged secret K for future authentications. This design eliminates the need for a verifier table and simplifies password management while preserving security.
The authors conduct a thorough security analysis covering several attack models:
- ID‑theft – Since IDs are dynamic, stealing a static identifier yields no advantage.
- Replay (reply) attacks – The one‑time nonce ensures that captured messages cannot be replayed.
- Forgery – An attacker lacking K cannot generate a valid C token, preventing message forgery.
- Password guessing – The combination of K, nonce, and password inside a hash makes offline guessing computationally prohibitive.
- Insider attacks – No password or verifier is stored on the server; insiders only see encrypted identifiers that are useless without K.
- Stolen verifier attacks – Since no verifier table exists, there is nothing to steal.
Performance evaluation shows that the protocol requires only a few hash computations and a single random number generation per authentication round. These operations are lightweight for modern smart cards and server hardware, resulting in a total of three to four message exchanges (client → server, server → client, optional confirmation). Compared with earlier smart‑card‑based schemes that maintain verifier tables, the proposed method reduces storage overhead and eliminates the need for periodic table updates when passwords change.
In conclusion, the paper presents a practical, high‑security remote authentication framework that empowers users to freely choose and modify passwords while removing the server’s reliance on vulnerable verifier tables. By integrating dynamic IDs, per‑session nonces, and smart‑card‑protected secrets, the scheme achieves resistance against a broad spectrum of attacks, making it suitable for deployment in environments ranging from traditional client‑server systems to emerging IoT and cloud services.
Comments & Academic Discussion
Loading comments...
Leave a Comment