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.
In FIPS mode:
Traceback (most recent call last):
> File "echo.py", line 23, in <module>
> ctx = SSL.Context('sslv3')
> File "/usr/lib64/python2.7/site-packages/M2Crypto/SSL/Context.py", line 47, in __init__
> map()[long(self.ctx)] = self
> TypeError: long() argument must be a string or a number, not 'NoneType'
sslv3 is disabled in FIPS mode, so it's fine that this doesn't work, however a TypeError is unexpected.
self.ctx == None should have been detected, and raised probably ValueError (like in the case of completely unknown method. Or is there a more useful error on the OpenSSL error stack that should have been picked up by the C bindings?
Version-Release number of selected component (if applicable):
m2crypto-0.21.1-9.el7.x86_64
Non-FIPS reproducer:
> >>> import M2Crypto
> >>> M2Crypto.m2.ssl_ctx_new(None)
# note the None returned with no exception, and the reason:
> >>> M2Crypto.m2.err_reason_error_string(M2Crypto.m2.err_get_error())
> 'null ssl method passed'
with FIPS, the error is 'only tls allowed in fips mode', which is fairly nice.
Expected behavior after the fix:
> >>> import M2Crypto
> >>> M2Crypto.m2.ssl_ctx_new(None)
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> M2Crypto.SSL.SSLError: null ssl method passed
... and a corresponding exception raised in the FIPS-mode test case.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
In FIPS mode: Traceback (most recent call last): > File "echo.py", line 23, in <module> > ctx = SSL.Context('sslv3') > File "/usr/lib64/python2.7/site-packages/M2Crypto/SSL/Context.py", line 47, in __init__ > map()[long(self.ctx)] = self > TypeError: long() argument must be a string or a number, not 'NoneType' sslv3 is disabled in FIPS mode, so it's fine that this doesn't work, however a TypeError is unexpected. self.ctx == None should have been detected, and raised probably ValueError (like in the case of completely unknown method. Or is there a more useful error on the OpenSSL error stack that should have been picked up by the C bindings? Version-Release number of selected component (if applicable): m2crypto-0.21.1-9.el7.x86_64