Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1618753 - Fedora's OpenSSL TLS minimum version is not comaptible with Python's test
Summary: Fedora's OpenSSL TLS minimum version is not comaptible with Python's test
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: python3
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Heimes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-17 13:39 UTC by Miro Hrončok
Modified: 2019-04-05 03:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Python 35045 None None None 2018-10-22 14:30:54 UTC

Description Miro Hrončok 2018-08-17 13:39:03 UTC
There is an upstream Python test that checks the minimum TLS version - test_min_max_version (test.test_ssl.ContextTests).

Fedora 29+ sets TLSv1 as explicit minimum version. Python's test suite assumes that the minimum protocol version is set to a magic marker.


FAIL: test_min_max_version (test.test_ssl.ContextTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-3.7.0/Lib/test/test_ssl.py", line 1084, in test_min_max_version
    ctx.minimum_version, ssl.TLSVersion.MINIMUM_SUPPORTED
AssertionError: <TLSVersion.TLSv1: 769> != <TLSVersion.MINIMUM_SUPPORTED: -2>


We currently workaround the problem by setting:

    export OPENSSL_CONF=/non-existing-file

This is a tracking bug to have this sorted in a better way, most likely upstream.

Comment 1 Petr Viktorin 2019-02-04 13:57:41 UTC
Will be fixed in the next 3.7 upstream release.


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