Bug 1297872
Summary: | mutt should use gpg2 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Till Maas <opensource> |
Component: | mutt | Assignee: | Matej Mužila <mmuzila> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | hhorak, jpacner, mjg, mmuzila, mrunge, opensource |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-08 14:51:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Till Maas
2016-01-12 16:46:26 UTC
Replacing the gpg.rc contents from /etc/Muttrc with "set crypt_use_gpgme=yes" fixes this. Why is gpgme not used in Fedora's mutt by default? (In reply to Till Maas from comment #1) > Replacing the gpg.rc contents from /etc/Muttrc with "set > crypt_use_gpgme=yes" fixes this. Why is gpgme not used in Fedora's mutt by > default? gpg is still gpg 1 by default in Fedora, so there is every reason for mutt to use that default gpg by default, unless it requires specific gpg 2(.1) functionality. The mess with different secret key stores is entirely due to the (one-)way from gpg 1 to gpg 2.1. That surely is confusing, but it's the user's decision to use gpg2. Luckily, mutt can use gpg 2.1 with a simple config setting, as you confirmed. In particular, it is ready to use that by default once gpg 2.1 is the default gpg in Fedora. |