You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one scenario where the gnupg2 package is not present, when running update_redmine_pgpkey rake task, I receive the error GPGME::Error::InvalidEngine: Invalid crypto engine.
Also when an email emission is triggered, in Redmine's production.log I see Email delivery error: Invalid crypto engine.
The cause of this, I believe, is that the libgpgme11 package is required by the GPGME gem, and needs to be installed. However, this package depends on gnupg2, so if you avoid ever installing GPG 2.x in order to deal with the known passphrase callback issue, shit will break. I believe this is why it's recommended to move /usr/bin/gpg2 elsewhere, and symlink it to /usr/bin/gpg.
However, if there's no passphrase on your secret key at all, shouldn't calling out to GnuPG 2 or greater simply just work correctly with GPGME?
The text was updated successfully, but these errors were encountered:
In one scenario where the
gnupg2
package is not present, when runningupdate_redmine_pgpkey
rake task, I receive the errorGPGME::Error::InvalidEngine: Invalid crypto engine
.Also when an email emission is triggered, in Redmine's production.log I see
Email delivery error: Invalid crypto engine
.The cause of this, I believe, is that the
libgpgme11
package is required by the GPGME gem, and needs to be installed. However, this package depends ongnupg2
, so if you avoid ever installing GPG 2.x in order to deal with the known passphrase callback issue, shit will break. I believe this is why it's recommended to move /usr/bin/gpg2 elsewhere, and symlink it to /usr/bin/gpg.However, if there's no passphrase on your secret key at all, shouldn't calling out to GnuPG 2 or greater simply just work correctly with GPGME?
The text was updated successfully, but these errors were encountered: