Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1829822

Summary:	Rebase gpgme to version 1.13.1 to accommodate gnupg-2.2.20
Product:	Red Hat Enterprise Linux 8	Reporter:	Tomas Mraz <tmraz>
Component:	gpgme	Assignee:	Jiri Kucera <jkucera>
Status:	CLOSED ERRATA	QA Contact:	Jakub Haruda <jharuda>
Severity:	high	Docs Contact:	Mariya Pershina <mpershin>
Priority:	unspecified
Version:	---	CC:	djez, jharuda, jkucera, knemcova, mpershin, ovasik
Target Milestone:	rc	Keywords:	Rebase
Target Release:	8.3	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gpgme-1.13.1-3.el8	Doc Type:	Enhancement
Doc Text:	.`gpgme` rebased to version 1.13.1. The `gpgme` packages have been upgraded to upstream version 1.13.1. Notable changes include: * New context flags `no-symkey-cache` (has an effect when used with GnuPG 2.2.7 or later), `request-origin` (has an effect when used with GnuPG 2.2.6 or later), `auto-key-locate`, and `trust-model` have been introduced. * New tool `gpgme-json` as native messaging server for web browsers has been added. As of now, the public key encryption and decryption is supported. * New encryption API to support direct key specification including hidden recipients option and taking keys from a file has been introduced. This also allows the use of a subkey.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 02:00:56 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:
Bug Depends On:
Bug Blocks:	1819712

Description Tomas Mraz 2020-04-30 12:41:56 UTC

We are going to rebase gnupg2 to version 2.2.20 in RHEL-8. There were many bug fixes and security fixes since version 2.2.9. The gpgme 1.10.1 as of RHEL-8 does not work fully correctly with it so it needs to be rebased to the current upstream version.

Comment 1 Tomas Mraz 2020-04-30 13:16:08 UTC

Also please note that the current Fedora master branch contains one additional patch needed to make the gpgme test suite fully work with gnupg >= 2.2.19.

Comment 14 errata-xmlrpc 2020-11-04 02:00:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gpgme bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4548