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
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. 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 |