Bug 1842850
Summary: | gnutls_set_default_priority() fails with a non-existing /etc/crypto-policies/back-ends/gnutls.config | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Martin Pitt <mpitt> |
Component: | crypto-policies | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED ERRATA | QA Contact: | Ondrej Moriš <omoris> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.3 | CC: | bgoncalv, nmavrogi, omoris, tmraz |
Target Milestone: | rc | Keywords: | Regression, Triaged |
Target Release: | 8.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | crypto-policies-20200610-1.git0ac8b1f.el8 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 01:58:45 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: | 1835661 |
Description
Martin Pitt
2020-06-02 08:16:11 UTC
Note that crypto-policies-scripts and thus /usr/bin/update-crypto-policies do *not* exist in the mock -- gnutls-devel does not require it, and also shouldn't -- there shouldn't be a need for setting a crypto policy *just* for building a package. Running ln -s /usr/share/crypto-policies/DEFAULT/gnutls.txt /etc/crypto-policies/back-ends/gnutls.config before the build works around the bug. This is regression from latest crypto-policies builds. There is a %post lua script that is supposed to create the symlinks but it does not work when the initial mock chroot is created. There is a potential fix in crypto-policies-20200527-5.git63fc906.el8. I'd ask you to test it once it gets into the composes. Martin, can you please verify that the problem is now fixed? Updated crypto-policies should be already in the buildroot. I confirm that this is fixed again in current nighlies. Thank you! I can't set the bug to VERIFIED officially (only QE is able to), but I vouch for it :-) 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 (crypto-policies 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:4536 |