Apparent duplicate password manager
I use Firefox and ESET Antivirus on Windows 10 I am using the Firefox password manager with a Primary Password. When I open a window to a bank or other sensitive site ESET Antivirus Banking and Payment Protection automatically opens a new Protected window. The password manager then fills in the login details for the site or offers a choice from a listbox if I have more than one login for that site without me having to provide a password for the password manager. Clicking on "View Saved Logins" from the listbox opens the password manager Search Logins window also without me having to enter a Primary Password. I can now view Usernames AND Passwords without having to enter any Primary Password. This appears to be an out of date copy of the passwords in a unprotected file since it is missing a few recently created entries. When using an standard Firefox browser window everything seems to work as expected with the Primary Password being required to activate the Pasword Manager and the recently created entries are present. One other point which may be relevant is that when viewing the same username/password in both the valid and the duplicate versions the window addresses are identical. This suggests to me that the Password Manager keeps the username/password data and a list of that data as separate enties and that what I have is actually one set of data with two seperate lists of the data. This makes me nervous about trying to delete anything from the unprotected list in case I am deleting the original data. This state of affairs may have come about when I was setting up Firefox Sync and inadvertantly Sync-ed Password Manager with Primary Password turned off. I have since turned off Sync but with no effect on th problem. Is there any way of deleting this apparent additional password list? The alternative seems to be to just uninstall Firefox and ESET Antivirus and re-install and hope that all the data is cleared out in the process and the re-import a password file.
All Replies (1)
You may have to take this to ESET support as it looks like their protected browser made a snapshot of the Firefox profile and hasn't updated the logins stored in this profile and uses a key4.db file that doesn't have the PP set (key4.db stores the encryption key and the PP encrypts this key).