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.
DescriptionChristian Heimes
2022-01-21 15:01:42 UTC
Description of problem:
An API change between OpenSSL 3.0.0 and 3.0.1 broke cryptograhy's poly1305 tests. The issue was introduced by https://github.com/openssl/openssl/pull/16789
and was solved in https://github.com/pyca/cryptography/pull/6403
Version-Release number of selected component (if applicable):
openssl-3.0.1-1.el9.x86_64
python-cryptography-3.4.7-6.el9
How reproducible:
always
Steps to Reproduce:
1. build the package with OpenSSL 3.0.1
Actual results:
DEBUG: _______________________ TestPoly1305.test_invalid_verify _______________________
DEBUG: self = <tests.hazmat.primitives.test_poly1305.TestPoly1305 object at 0x7f30edb24c40>
DEBUG: backend = <cryptography.hazmat.backends.openssl.backend.Backend object at 0x7f30feab18b0>
DEBUG: def test_invalid_verify(self, backend):
DEBUG: poly = Poly1305(b"0" * 32)
DEBUG: poly.update(b"msg")
DEBUG: with pytest.raises(InvalidSignature):
DEBUG: > poly.verify(b"")
DEBUG: tests/hazmat/primitives/test_poly1305.py:96:
DEBUG: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
DEBUG: ../../BUILDROOT/python-cryptography-3.4.7-6.el9.x86_64/usr/lib64/python3.9/site-packages/cryptography/hazmat/primitives/poly1305.py:44: in verify
DEBUG: ctx.verify(tag)
DEBUG: ../../BUILDROOT/python-cryptography-3.4.7-6.el9.x86_64/usr/lib64/python3.9/site-packages/cryptography/hazmat/backends/openssl/poly1305.py:61: in verify
DEBUG: mac = self.finalize()
DEBUG: ../../BUILDROOT/python-cryptography-3.4.7-6.el9.x86_64/usr/lib64/python3.9/site-packages/cryptography/hazmat/backends/openssl/poly1305.py:56: in finalize
DEBUG: self._backend.openssl_assert(res != 0)
DEBUG: ../../BUILDROOT/python-cryptography-3.4.7-6.el9.x86_64/usr/lib64/python3.9/site-packages/cryptography/hazmat/backends/openssl/backend.py:242: in openssl_assert
DEBUG: return binding._openssl_assert(self._lib, ok, errors=errors)
DEBUG: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
DEBUG: lib = <module 'lib'>, ok = False
DEBUG: errors = [<cryptography.hazmat.bindings.openssl.binding._OpenSSLError object at 0x7f30edb248b0>]
DEBUG: def _openssl_assert(lib, ok, errors=None):
DEBUG: if not ok:
DEBUG: if errors is None:
DEBUG: errors = _consume_errors(lib)
DEBUG: errors_with_text = _errors_with_text(errors)
DEBUG:
DEBUG: > raise InternalError(
DEBUG: "Unknown OpenSSL error. This error is commonly encountered when "
DEBUG: "another library is not cleaning up the OpenSSL error stack. If "
DEBUG: "you are using cryptography with another library that uses "
DEBUG: "OpenSSL try disabling it before reporting a bug. Otherwise "
DEBUG: "please file an issue at https://github.com/pyca/cryptography/"
DEBUG: "issues with information on how to reproduce "
DEBUG: "this. ({0!r})".format(errors_with_text),
DEBUG: errors_with_text,
DEBUG: )
DEBUG: E cryptography.exceptions.InternalError: Unknown OpenSSL error. This error is commonly encountered when another library is not cleaning up the OpenSSL error stack. If you are using cryptography with another library that uses OpenSSL try disabling it before reporting a bug. Otherwise please file an issue at https://github.com/pyca/cryptography/issues with information on how to reproduce this. ([_OpenSSLErrorWithText(code=50331803, lib=6, reason=155, reason_text=b'error:0300009B:digital envelope routines::buffer too small')])
DEBUG: ../../BUILDROOT/python-cryptography-3.4.7-6.el9.x86_64/usr/lib64/python3.9/site-packages/cryptography/hazmat/bindings/openssl/binding.py:77: InternalError
Expected results:
No error
Additional info:
Failing build https://centos.softwarefactory-project.io/zuul/t/centos/build/981a623af8264a0dbbea842f38e40106
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 (new packages: python-cryptography), 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-2022:2580