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

Guzzle dependency breaking SSL due to packaged cacert.pem file. #27

Open
RickKukiela opened this issue Sep 28, 2020 · 2 comments
Open

Comments

@RickKukiela
Copy link
Contributor

I don't know if this library is still being maintained or not but in case anyone else runs into this maybe I can save you from busting your head open against a wall like I did.

The packaged version of guzzle that this lib depends upon has included its own cacert.pem file which it stores in vendors/guzzle/guzzle/src/Guzzle/Http/resources/cacert.pem

This ca is old and not valid for the new first data / payeezy certificates and will throw a CURL 60 SSL error whenever you try to use this library.

I cannot see any way in the configuration to override this behavior from my code without manually overriding code in this library.

I am going to fork this library to fix this for myself. If the fix I come up with would work for the production code I'll supply a PR but I'm up against a time constraint on this so I'm not going to spend a lot of time on this.

@RickKukiela
Copy link
Contributor Author

RickKukiela commented Sep 28, 2020

So I just figured out that the MASTER branch of this repo is newer than the latest tag. The MASTER branch is using omnipay core v3 not v2, which uses the new version of guzzle that does not have this but.

If you are having SSL issues with your copy of this library and are using v2.4.1 execute the following commands to fix the issue:

composer remove omnipay/firstdata
composer require omnipay/firstdata:dev-master

As long as your system has an up to date ca bundle and is properly configured this will fix your issue.

@RickKukiela
Copy link
Contributor Author

Can we please get a tag for this release? I feel dirty requiring dev-master instead of an actual tag.

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

No branches or pull requests

1 participant