should #passwordstore #pass standardize?
- best practice YAML for password entry supported by #Browserpass, and pass-simple (https://sourceforge.net/projects/pass-simple/)
- folder name for exported public keys created by #gopass and #PassSimple
?
should #pass be managed in github instead of a mailing list?
#Pass #PasswordStore #introduction #QtPass #gopass #PassSimple #gnupg #gpgme #OpenPGP #PGP
#passwordstore #pass #browserpass #gopass #passsimple #introduction #qtpass #GnuPG #gpgme #OpenPGP #PGP
Hi' I have found that true also.
Therefore I've wrapt #gpgme in RIIA
https://github.com/shemeshg/gpgme-cmake-example
I know python, requires deferent approach, (RIIA and destructors are c++ methodology only).
The good news, that when implemented correctly it is stable (https://github.com/shemeshg/pass-simple-qt) and does for tou all the complicated work of `pinantery` smart cards and session management.
# the bad news
GPGME is not multithreading, and will crash when multiple threads runs of the same gpg's Home
Pass-simple,
gui for pass I've written (Qt Qml C++),
https://sourceforge.net/projects/pass-simple/
Documentation, for step by step install for all platforms
https://shemeshg.github.io/pass-simple-mdbook/index.html
#Pass #PasswordStore #introduction #QtPass #gopass #PassSimple #gnupg #gpgme #OpenPGP #PGP
#OpenPGP #PGP #pass #passwordstore #introduction #qtpass #gopass #GnuPG #gpgme #passsimple