We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$ phive install phpunit Phive 0.2.0-91-g4dd3159 - Copyright (C) 2015-2016 by Arne Blankerts, Sebastian Heuer and Contributors Downloading repository list from https://phar.io/data/repositories.xml Downloading https://phar.io/data/repositories.xml [ 873 B / 873 B - 100% ] Downloading https://phar.phpunit.de/phive.xml [ 57.52 KB / 57.52 KB - 100% ] Downloading https://phar.phpunit.de/phpunit-5.3.1.phar [ 2.70 MB / 2.70 MB - 100% ] Downloading https://phar.phpunit.de/phpunit-5.3.1.phar.asc [ 819 B / 819 B - 100% ] Downloading key 4AA394086372C20A Trying https://hkps.pool.sks-keyservers.net [WARNING] Failed with status code 0: error setting certificate verify locations: CAfile: phar:///vagrant/phive/build/phar/phive-0.2.0-91-g4dd3159.phar/src/../conf/ssl/ca_certs/sks-keyservers.netCA.pem CApath: /etc/ssl/certs [ERROR] PublicKey 4AA394086372C20A not found on key servers
As @theseer found out this is due to the fact that Curl is unable to access files that lie within a PHAR (https://bugs.php.net/bug.php?id=69035).
The suggested workaround is to copy the .pem file to a temporary location (outside of the phar) and let Curl use that file instead.
The text was updated successfully, but these errors were encountered:
fixes #45: copy local certificates to temporary location
a236ac9
e4a5ba7
sebastianheuer
No branches or pull requests
As @theseer found out this is due to the fact that Curl is unable to access files that lie within a PHAR (https://bugs.php.net/bug.php?id=69035).
The suggested workaround is to copy the .pem file to a temporary location (outside of the phar) and let Curl use that file instead.
The text was updated successfully, but these errors were encountered: