Skip to content

Fix segfault when built with OpenSSL >= 1.0.1 #481

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

Closed
wants to merge 1 commit into from
Closed

Fix segfault when built with OpenSSL >= 1.0.1 #481

wants to merge 1 commit into from

Conversation

rdlowrey
Copy link
Contributor

@rdlowrey rdlowrey commented Oct 8, 2013

This commit fixes segfaults encountered when using ext/openssl built against OpenSSL >= 1.0.1. This newer version of OpenSSL is required for TLSv1.1 and TLSv1.2 support.

Note that this patch has no BC implications and should be safe to merge with 5.4 and 5.5 branches.

@m6w6
Copy link
Contributor

m6w6 commented Oct 8, 2013

How do I provoke the crash? A test the fails now and works woth the patch would be awesome!

@m6w6
Copy link
Contributor

m6w6 commented Oct 8, 2013

Oh well, I suppose the other PRs depend on this one and their tests would crash?

@rdlowrey
Copy link
Contributor Author

rdlowrey commented Oct 8, 2013

That's correct. I was unsure of how to add a test because it really just boils down to the extension using code that is no longer valid with newer versions of OpenSSL.

Just build against OpenSSL v1.0.1 and you'll get failed tests in the openssl suite without this patch.

@rdlowrey
Copy link
Contributor Author

rdlowrey commented Oct 8, 2013

You don't actually need to use any of the recent PRs to see this behavior. Simply build the existing master branch against OpenSSL 1.0.1 and you'll get failed tests (which are fixed by this PR).

php-pulls pushed a commit that referenced this pull request Oct 9, 2013
@m6w6
Copy link
Contributor

m6w6 commented Oct 9, 2013

Erm... did a patch instead of a cherry, so your have to close this PR yourself :) Sorry
b026993

@rdlowrey
Copy link
Contributor Author

rdlowrey commented Oct 9, 2013

No problem :)

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