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

error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number #16

Open
sebdesign opened this issue Oct 15, 2014 · 6 comments
Open

error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number #16

sebdesign opened this issue Oct 15, 2014 · 6 comments

Comments

@sebdesign
Copy link

Today when I run IPN::getOrder() I get a CurlRequestException with the following message:

cURL error: [35] error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number' in vendor/mike182uk/paypal-ipn-listener/src/PayPal/Ipn/Request/Curl.php:93

According to this question, Paypal has updated their SSL version due to the POODLE attack.

By default, the curlVerifier uses SSL v3, but it can be overrided with the forceSSLv3() method.

In the IPN::getOrder() method, when the $request handler is created we should do something like:

$request->forceSSLv3(FALSE);

It worked on my case. I can't make a pull request for the moment, but if you want you can do it.

Cheers!

@loranger
Copy link

@sebdesign Thank you so much for this workaround !
Maybe ther's a way to user ssl v4 with Symfony Request (which seems to be the curl client used by paypal-ipn) in order to keep the paypal ipn connection secure.

@adamkellett
Copy link

Thank you so much for this @sebdesign , we've been without this for days. 👍

@sebdesign
Copy link
Author

@loranger @adamkellett you're welcome!

P.S.: @loranger passe mon bonjour au joli Annecy!

@linuxcarl
Copy link

Hello!

I have already applied $ request-> forceSSLv3 (FALSE); but now I will throw this error, please help, urgent
LogicalGrape \ PayPalIpnLaravel \ Exception \ InvalidIpnException
PayPal as responded with INVALID

@RTC1 RTC1 mentioned this issue Nov 15, 2014
@dipesh008
Copy link

mike182uk has fixed this issue. if this repo can be updated with that code.

@dipesh008
Copy link

any help on this. URGENT

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 a pull request may close this issue.

5 participants