Skip to content
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

There's no way to encrypt-to-self if using gpgme #89

Open
WhyNotHugo opened this issue Feb 6, 2015 · 3 comments
Open

There's no way to encrypt-to-self if using gpgme #89

WhyNotHugo opened this issue Feb 6, 2015 · 3 comments

Comments

@WhyNotHugo
Copy link

gpgme is cool, because it simplifies configuration, works better with gpg-agent, and has nicer output, but, there seems to be no way to encrypt-to-self.

Would it be possible to add an option to encrypt-to-self using gpgme as well?

@WhyNotHugo
Copy link
Author

Well, I sort of got around this by using encrypt-to in gpg.conf, though I'd prefer to have this done by mutt by default (or with some simple setting), rather than to change the user-wide gpg config.

@duckdalbe
Copy link

There's this patch: https://www.mandarb.com/mutt/patch-1.5.19-ow.smime-encrypt-self.1, which applies with little adjustments (adjusted here: https://gist.github.com/duckdalbe/49f1b0171db662074dcc). But apparently it fails to properly add the default-key to the keylist: when running mutt with the option it core-dumps while encrypting saying

error adding recipient `0xREALRECIPIENT0xDEFAULTKEY?': End of file?

Fixing this is out of my leage. But maybe it's not too hard for someone else?

@duckdalbe
Copy link

Sorry, I wasn't thinking. The previous comment and patch refers to using encrypt-to-self with S/MIME.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants