Qt-SESAM
Qt-SESAM copied to clipboard
Encrypted password export
Define an encrypted export format which allows to share passwords between different password managers.
Flow:
- Select passwords to export
- Enter transport password / button to generate a complex password
- Export to file
@digulla In which format would you like Qt SESAM export passwords? Which other password manager do you want to use?
I've started to write my own: https://bitbucket.org/digulla/darks-password-manager since FPM more closely resembles my own needs (multi-platform, ability to type in my own passwords, smart clipboard and command line support).
But more realistically: Sometimes, you need to share accounts with team mates or with a different instance of your password manager (like copying passwords between remote databases). It would be great if that was possible without decrypting the passwords.
The same function could be used to create backups of a subset of the passwords.
Note: I'm using XML as a file format but the encryption is compatible with Qt-SESAM. If it would help, I could fork out an encryption library which would make it easier to interact with other password managers written in Java.
Qt-SESAM already supported legacy passwords, i.e. passwords chosen on your own.
With Qt as its basis Qt-SESAM is multiplatform by design.
And … Qt-SESAM now comes with smart login (see commit f19d051f358007303c395e0c43449ec6120c18b5). Thanks for this neat idea, @digulla :+1:
I'm wary of your comment "is multiplatform by design" when I read "Windows only" in commits :-) And how about Mac?
I suggest to promote the links for the build wiki pages in the README.
@digulla OS X usually isn't a problem in my experience. Unfortunately I haven't had the time/opportunity to check it out.
@digulla The "Windows only" commits affect changes to Qt SESAM regarding the smart login facility.
I haven't found a way to react on clipboard paste actions on other platforms than Windows. So I'm curious how you've managed to intercept events like this with Java. Do you like to tell me? ;-)
@digulla The README will be completely rewritten when time permits. Thanks for your feedback.