multiple password management
I visit sites which require password changes on a regular basis and each time I do this I save the login details in Firefox.
Now I have sites where over 20 login options are displayed.
I want to delete all of the expired login combinations but when I try to manage the passwords I only have the latest (correct) combination displayed.
How do I prune my password lists to remove obsolete details but retain the current ones?
Can this be done by exporting the list, editing it externally and then re-importing? I don't want to try and then lose this useful feature.
Solution choisie
You can keep a copy of the current logins.json to be able to recover from mistakes, that is why I wrote above to rename the current logins.json (e.g. loginsSAV.json) instead of removing the file. If you would keep the file and import then nothing will change and you would still have all old logins. A CSV file has a separate line for each login, so you can possibly copy the lines you remove to another file for backup.
Lire cette réponse dans son contexte 👍 0Toutes les réponses (5)
Open the Password Manager. Delete unwanted entries from there.
You can export the logins to a CSV file and edit this file. You can rename the existing logins.json in the Firefox profile folder to start with a fresh file and import the edited logins.
See:
See the note at the bottom of this article about how to enable CSV import via the about:config page.
Thank you FredMcD I've tried that but for some reason when I search for passwords for the site in question only the current login details are shown. Other sites give a complete history from which I can, and do, delete obsolete entries.
If I go to the site login then I am presented with several years worth of login options to select from.
Cor-el
This may well be what I end up doing but I was concerned that I could mess things up and loose the passwords that are saved (I know, I'll have the .CSV file to fall back on :) ) I was hoping for a simple 2-3 click option.
Solution choisie
You can keep a copy of the current logins.json to be able to recover from mistakes, that is why I wrote above to rename the current logins.json (e.g. loginsSAV.json) instead of removing the file. If you would keep the file and import then nothing will change and you would still have all old logins. A CSV file has a separate line for each login, so you can possibly copy the lines you remove to another file for backup.
Thanks Cor-el.
This is a good work around and should do the job.
Looking at the csv file has already shown me I have a lot of housekeeping to do. ;)