I have a client who never keeps track of his passwords. He lets Firefox remember them. I just set up a new system for him and recovered 135 of his pws from the old system using Nirsoft's wbpv. The most functional export is via the View Menu: View/HTML Report.
This creates a very useable table report in .htm format that opens with Firefox and can be searched quickly and easily using FF's ctrl+F find function.
When he goes to the site, he can just open the wbpv report.htm in FF, search for the site (i.e., typing face will take him straight to the www-dot-facebook-dot-com entry). Copy and paste his username, allow the browser to remember (he'll accept nothing else and I've learned to let it go...) and he's good to go.
I guess the question is: Is this a secure method to allow him to restore his pws as needed? Could the htm file somehow 'leak' info? If so, is there some way this could be managed? I don't see a way to create an outbound rule for an individual file in WFW.
Thanks for any ideas!
This creates a very useable table report in .htm format that opens with Firefox and can be searched quickly and easily using FF's ctrl+F find function.
When he goes to the site, he can just open the wbpv report.htm in FF, search for the site (i.e., typing face will take him straight to the www-dot-facebook-dot-com entry). Copy and paste his username, allow the browser to remember (he'll accept nothing else and I've learned to let it go...) and he's good to go.
I guess the question is: Is this a secure method to allow him to restore his pws as needed? Could the htm file somehow 'leak' info? If so, is there some way this could be managed? I don't see a way to create an outbound rule for an individual file in WFW.
Thanks for any ideas!