|
|
| Line 57: |
Line 57: |
|
| |
|
| A secret and biometric on the authenticator can be used together, similarly to how they would be used on a [[smartphone]]. For example, a fingerprint is used to provide convenient access to your smartphone but occasionally fingerprint access fails, in which case a PIN can be used. | | A secret and biometric on the authenticator can be used together, similarly to how they would be used on a [[smartphone]]. For example, a fingerprint is used to provide convenient access to your smartphone but occasionally fingerprint access fails, in which case a PIN can be used. |
|
| |
| == Advantages over traditional password-based authentication ==
| |
| WebAuthn addresses by design many inherent issues in traditional password-based authentication:
| |
|
| |
| * '''Secure Credential Generation and Storage''': WebAuthn generates unique credentials for each website using robust algorithms, storing them securely in trusted authenticators. This eliminates common vulnerabilities such as:
| |
| ** Weak passwords that can be easily brute-forced due to insufficient length.
| |
| ** Predictable passwords vulnerable to dictionary attacks (e.g., "password", "12345678").
| |
| ** Guessable passwords based on personal information (e.g., birthdates, addresses).
| |
| ** Poor client-side password storage (e.g., written down, stored in phone contacts).
| |
| ** Password reuse across multiple websites, as WebAuthn credentials are specific to individual websites by design.
| |
| ** Inadequate server-mandated password requirements (e.g., overly lax or restrictive criteria, arbitrary maximum length limits, limited charsets).
| |
| ** Restrictions preventing password manager auto-fill features.
| |
| * '''No Server-Side Credential Storage''': The private part of a credential is never stored on a server, eliminating risks and vulnerabilities such as:
| |
| ** Insecure password storage in databases (e.g., plaintext or relying on weak hash-based algorithms/constructions).
| |
| ** Database leaks exposing passwords.
| |
| ** Mandatory, ineffective periodic password changes.
| |
| * '''Unique Credentials for Each Website''': WebAuthn ensures credentials are unique per website, eliminating the following risks and vulnerabilities:
| |
| ** Credential stuffing attacks, where attackers use credentials from one data breach across multiple sites.
| |
| ** Phishing attacks, as credentials cannot be reused or misapplied to different websites.
| |
|
| |
|
| == Overview == | | == Overview == |