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
I am an end user for this plugin.
As far as I realized, even if you use "separate database" once, the database file creates a OTP database for OTP seeds, burried in the "master" database file. Even if I switch to not using a separate database, then back to using separate database, there's always some garbage coming back from this OTP database, I thought were gone.
How do I clean up my database from this?
The text was updated successfully, but these errors were encountered:
In order to not lose any data, the KeePassOTP database is not deleted when switching to entry-specific storage - users might forget to migrate their otp data...
If you want to delete the KeePassOTP database, you currently have to delete it manually.
Find KeePassOTP.DB - This field holds the KeePassOTP database as described in the wiki
Delete
I'll leave this issue open and create a pull request to prompt for deletion of KeePassOTP database if the user decides to switch to entry-specific storage
Summary
I am an end user for this plugin.
As far as I realized, even if you use "separate database" once, the database file creates a OTP database for OTP seeds, burried in the "master" database file. Even if I switch to not using a separate database, then back to using separate database, there's always some garbage coming back from this OTP database, I thought were gone.
How do I clean up my database from this?
The text was updated successfully, but these errors were encountered: