Difference between revisions of "Credential Management"

Revision as of 12:30, 24 May 2021

This page is about the W3C CredentialManagement API which is often abbreviated as CredMan..
This also is support by Web Authentication and WebAuthn 2.

For general information about recovery or other topics see the web page Credential.

Protection against phishing: An attacker who creates a fake login website can't login as the user because the signature changes with the origin of the website.
Reduced impact of data breaches: Developers don't need to hash the public key, and if an attacker gets access to the public key used to verify the authentication, it can't authenticate because it needs the private key.
Invulnerable to password attacks: Some users might reuse passwords, and an attacker may obtain the user's password for another website (e.g. via a data breach). Also, text passwords are much easier to brute-force than a Digital Signature.

@@ Line 8: / Line 8: @@
 * Protection against phishing: An attacker who creates a fake login website can't login as the user because the signature changes with the origin of the website.
 *Reduced impact of data breaches: Developers don't need to hash the public key, and if an attacker gets access to the public key used to verify the authentication, it can't authenticate because it needs the private key.
-* Invulnerable to password attacks: Some users might reuse passwords, and an attacker may obtain the user's password for another website (e.g. via a data breach). Also, text passwords are much easier to brute-force than a digital signature.
+* Invulnerable to password attacks: Some users might reuse passwords, and an attacker may obtain the user's password for another website (e.g. via a data breach). Also, text passwords are much easier to brute-force than a [[Digital Signature]].
 ==Solutions==