password manager
≈ 5 min read
Names in other languages
- Françaisgestionnaire de mots de passe
- Portuguêsgerenciadores de senhas
- Españolgestor de contraseñas
- DeutschKennwortverwaltung
- Englishpassword manager
- Русскийменеджер паролей
- Polskimenedżer haseł
- 日本語パスワードマネージャー
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
is an example of a password manager. Pictured above is its vault interface showing a saved login entry, which keeps one's usernames and passwords. A password manager is software that stores usernames and passwords in a collection called a password vault. The vault is intended to be encrypted, and its encryption key is commonly derived from a master password chosen by the user. Most password managers can generate passwords, save credentials as they are entered, and fill them when the user returns. Some can also synchronize records between devices, share credentials with other users, and store payment-card details, notes, and documents. Password managers are available as standalone applications, browser extensions, features built into web browsers, and services integrated with an operating system. A vault may remain on one device, be synchronized through a provider's servers, or be copied between devices through a separate file-storage service. By generating and storing a different password for each account, a password manager can reduce the need to memorize many passwords or reuse the same password across accounts. Because a single vault may contain credentials for many accounts, the vault and its master password are valuable targets for attack. Security depends on how the vault is protected and on features such as autofill, synchronization, sharing, and account recovery.…
is an example of a password manager. Pictured above is its vault interface showing a saved login entry, which keeps one's usernames and passwords. A password manager is software that stores usernames and passwords in a collection called a password vault. The vault is intended to be encrypted, and its encryption key is commonly derived from a master password chosen by the user. Most password managers can generate passwords, save credentials as they are entered, and fill them when the user returns. Some can also synchronize records between devices, share credentials with other users, and store payment-card details, notes, and documents. Password managers are available as standalone applications, browser extensions, features built into web browsers, and services integrated with an operating system. A vault may remain on one device, be synchronized through a provider's servers, or be copied between devices through a separate file-storage service. By generating and storing a different password for each account, a password manager can reduce the need to memorize many passwords or reuse the same password across accounts. Because a single vault may contain credentials for many accounts, the vault and its master password are valuable targets for attack. Security depends on how the vault is protected and on features such as autofill, synchronization, sharing, and account recovery. Users may also avoid or stop using password managers because of concerns about security or control, inconvenience, or compatibility with websites. Password managers have existed since the 1990s. They later became available as browser components, mobile applications, cloud-based services, and features built into an operating system. Some password managers can also create and store passkeys, login credentials based on public-key cryptography that can replace passwords or serve as an additional authentication factor. Some websites have tried to limit password manager usage by blocking pasted passwords or by using HTML settings that ask browsers not to save or automatically fill login fields. In 2015, British Gas used onpaste="return false" on a password field and said it had chosen not to provide compatibility with password managers. Following criticism, the company said it would reconsider its approach. Paste restrictions were also found on T-Mobile, the German Barclaycard site, and Western Union. T-Mobile said its restriction was unintended and later removed it. A site can use autocomplete="off" to ask the browser not to retain a field's value for later auto-completion, but modern browsers generally ignore it for username and password fields. For other fields, autocomplete="off" can still discourage later auto-completion. A password field meant for a newly assigned password can instead use autocomplete="newpassword" . The National Institute of Standards and Technology (NIST) guidance, NIST SP 800-63B, requires password verifiers to allow password managers and autofill, and recommends allowing passwords to be pasted when autofill APIs are unavailable. OWASP (Open Worldwide Application Security Project), in its Authentication Cheat Sheet, similarly recommends standard HTML username and password fields, support for passwords up to at least 64 characters and for printable characters, and the ability to paste into username, password, and multifactor authentication fields.
Text derived from https://en.wikipedia.org/w/index.php?oldid=1375950542 under CC BY-SA 4.0; modifications have been made.