Project structure about mozilla-password-decrypt HOT 1 OPEN

mozpassword would be okay to me for a Python package name. But I would not want to rename it before we have encoding/encryption in there, too.

For the decrypting and encrypting class, master password support should come first, in my eyes.
I'm also not sure, if that class should take care of NSS init/deinit itself.

I could imagine to go a more data centric way: to have two kinds of instances:

• encrypted log-in instances with a method .decrypt(..) to produce a new plaintext instance from it and
• plaintext instances with a method .encrypt(..) to produce encrypted instances.

About signons.txt I don't object, but I won't be able to test it live so there will need to be automated regression test cases for it.

from mozilla-password-decrypt.