Skip to content

introduce versioning for openssl #838

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

Merged
merged 1 commit into from
Jul 14, 2016
Merged

Conversation

brussee
Copy link
Contributor

@brussee brussee commented Jul 14, 2016

On Android versions lower than 6.0 the openssl library of the system is being loaded instead of the one provided with the app.
Adding the version to the name of the shared library file avoids the problem of the linker at runtime giving the wrong version of the library and provides a clear indication of what version you are using (good ensuring you use the latest version for security).

@brussee
Copy link
Contributor Author

brussee commented Jul 14, 2016

Without versioning m2crypto failed to load on Android 5.1.1 and lower.

@inclement inclement merged commit 990b49c into kivy:master Jul 14, 2016
@inclement
Copy link
Member

Looks good, thanks. Do you know why this wasn't happening before, is the system openssl a new addition?

@brussee
Copy link
Contributor Author

brussee commented Jul 15, 2016

It appears that unknowingly the system openssl was being used and cyanogenmod has a newer version installed than stock. I discovered this when the specific missing symbol turned out to be a new addition going from 1.0.1.l to 1.0.2.
So I think therefore that stock Android 6.0.1 has openssl 1.0.2 and Android 5.1.1 and lower have openssl 1.0.1 and cyanogenmod 12.1 has openssl 1.0.2.

@brussee brussee deleted the openssl-version branch July 15, 2016 13:37
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