Bug 1829822 - Rebase gpgme to version 1.13.1 to accommodate gnupg-2.2.20
Summary: Rebase gpgme to version 1.13.1 to accommodate gnupg-2.2.20
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gpgme
Version: ---
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.3
Assignee: Jiri Kucera
QA Contact: Jakub Haruda
Mariya Pershina
Depends On:
Blocks: 1819712
TreeView+ depends on / blocked
Reported: 2020-04-30 12:41 UTC by Tomas Mraz
Modified: 2020-11-04 02:04 UTC (History)
6 users (show)

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.
Clone Of:
Last Closed: 2020-11-04 02:00:56 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4548 0 None None None 2020-11-04 02:00:59 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.