-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crypto-wrapper #30
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are two use-cases on gpg and opmsg that can be greatly facilitated by having our own crypto-wrapper:
the first point can be solved having a very simple config file that matches keyid and email on two columns, then wrap the encrypt phase of gpg when looking for keys with our own crypto-wrapper
the second can be solved wrapping the import and encrypt phases in opmux with something that will setup the default persona on import but also allow mapping of personas from a config file (perhaps the same file for gpg) and have also an option to generate disposable random keys for some recipients
About persona-linking: https://github.com/stealth/opmsg#persona-linking
The text was updated successfully, but these errors were encountered: