You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Status
Currently, one has to put in the password every time the extension locks, or the browser is closed/re-opened.
With a randomly-generated password of 128 characters (Upper/lower case letters, numbers, symbols) this is incredibly tedious to type, and storing it anywhere else accessible is a huge safety/integrity risk.
Feature Description
The BitWarden extension, for instance, supported optionally adding a device-local PIN (and/or Biometric) lock after initial setup, so that unlocking the extension wasn't as difficult, and security could be maintained.
Additional context
This would align with BitWarden UX, and to an extent Mozilla FireFox.
The text was updated successfully, but these errors were encountered:
Current Status
Currently, one has to put in the password every time the extension locks, or the browser is closed/re-opened.
With a randomly-generated password of 128 characters (Upper/lower case letters, numbers, symbols) this is incredibly tedious to type, and storing it anywhere else accessible is a huge safety/integrity risk.
Feature Description
The BitWarden extension, for instance, supported optionally adding a device-local PIN (and/or Biometric) lock after initial setup, so that unlocking the extension wasn't as difficult, and security could be maintained.
Additional context
This would align with BitWarden UX, and to an extent Mozilla FireFox.
The text was updated successfully, but these errors were encountered: