Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔧 Properly handle openssl version > 1.0.X #365

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ryannowarm
Copy link

Handle the case when the major version is greater than 1 and the minor
version is greater than 0. For example, my current host uses openssl
1.1.1.

@madchutney
Copy link
Contributor

madchutney commented Sep 13, 2019

@ryannowarm Thanks for the fix. Can you please add a news file for the release notes, e.g. docs/news/20190913.bugfix and we'll get this in, thanks.

@madchutney madchutney changed the title Properly handle openssl version > 1.0.X 🔧 Properly handle openssl version > 1.0.X Sep 13, 2019
@ryannowarm ryannowarm force-pushed the fix_ssl_warning branch 2 times, most recently from 41d78a3 to 840f126 Compare September 13, 2019 12:54
Handle the case when the major version is greater than 1 and the minor
version is greater than 0.  For example, my current host uses openssl
1.1.1.
@ryannowarm
Copy link
Author

I've pushed a more elegant fix as well as the news entry.

@@ -107,7 +107,7 @@ def check_openssl_version():
minor = int(match.group(3))
patch = int(match.group(4))

if major >= 1 and minor >= 0 and patch >= 2:
if (major, minor, patch) >= (1, 0, 2):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice use of tuple comparison, hadn't though of doing that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants