Split TOTP storage and retrieval into a separate extension and database
Feature function
What will this feature do differently? I would like TOTP information to be stored in a seperate database and access by a separate extension.
What benefits will this feature bring? if someone were to social engineer your login credentials, they would only be able to get your usernames and passwords, and not your TOTP credentials. Ideally, your TOTP login credentials would not match yout Bitwarden credentials. I don’t expect this to be the default behavior, but it would be nice to have a “paranoid mode” as an option.
Remember to add a tag for each client application that will be affected
Related topics + references
Are there any related topics that may help explain the need and function of this feature? Not that I see
Are there any references to this feature or function on other platforms that may be helpful? No that I see