Self update error

[it-can]

The command phpunit --self-update will throw these errors:

Updating the PHPUnit PHAR ... PHP Warning:  file_get_contents(): SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed in phar:///usr/local/bin/phpunit/phpunit/TextUI/Command.php on line 849

Warning: file_get_contents(): SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed in phar:///usr/local/bin/phpunit/phpunit/TextUI/Command.php on line 849
PHP Warning:  file_get_contents(): Failed to enable crypto in phar:///usr/local/bin/phpunit/phpunit/TextUI/Command.php on line 849

Warning: file_get_contents(): Failed to enable crypto in phar:///usr/local/bin/phpunit/phpunit/TextUI/Command.php on line 849
PHP Warning:  file_get_contents(https://phar.phpunit.de/phpunit.phar): failed to open stream: operation failed in phar:///usr/local/bin/phpunit/phpunit/TextUI/Command.php on line 849

Warning: file_get_contents(https://phar.phpunit.de/phpunit.phar): failed to open stream: operation failed in phar:///usr/local/bin/phpunit/phpunit/TextUI/Command.php on line 849
 done

internal corruption of phar "phpunit-temp.phar" (truncated entry)

[ymhuang0808]

I also have the same problem.
The certification of phar.phpunit.de was changed, because, it is not the same with build/ca.pem

[hamdrew]

Also getting the same issue.

[sebastianbergmann]

Yes, the certificate for phar.phpunit.de was updated. Now I need to remember how that ca.pem file is created.

[theseer]

You don't "create" the ca.pem as that's been generated by the CA signing the new cert - Comodo in this case. For nginx's TLS handlanding you already have that in use as part of the chain/bundle pem file.

All you should have to do is replace the ca.pem file within the phar by the matching ca cert from comodo. And by matching i mean the one they use/supply for this type of certificate in use. For all practical means it should boil down to extracting the last cert section from the bundle-crt file into its own ca.pem file.

[sebastianbergmann]

Ah, now I remember. Hopefully will get around to do that tomorrow.

[sebastianbergmann]

Unfortunately extracting the last cert section from the bundle-crt file into its own ca.pem file does not seem to work.

[sebastianbergmann]

Nevermind, I found the correct PEM on Comodo's website.

[barbazul]

I am still geting this error

[ymhuang0808]

Hi, @barbazul
I think you should download the latest PHPUnit manually, because the PHPUnit 4.6.5 or later version contains the latest and correct SSL certificate.

[theseer]

Every "old" version of PHPUnit shipping with the old cert is bound to have the same issue.

Since it's not (yet?) possible to have two certificates for the same domain with https, there is no workaround other than downloading the newer version manually.

[MichaelHindley]

Got this while updating from 4.7 to 4.8 today

[sebastianbergmann]

@NihilNovi I cannot reproduce what you describe

$ wget https://phar.phpunit.de/phpunit-4.7.7.phar
--2015-08-07 11:12:02--  https://phar.phpunit.de/phpunit-4.7.7.phar
Resolving phar.phpunit.de (phar.phpunit.de)... 188.94.27.25
Connecting to phar.phpunit.de (phar.phpunit.de)|188.94.27.25|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3100940 (3.0M) [application/octet-stream]
Saving to: ‘phpunit-4.7.7.phar’

phpunit-4.7.7.phar  100%[=======================>]   2.96M  3.16MB/s   in 0.9s   

2015-08-07 11:12:03 (3.16 MB/s) - ‘phpunit-4.7.7.phar’ saved [3100940/3100940]


$ php phpunit-4.7.7.phar --self-update
PHPUnit 4.7.7 by Sebastian Bergmann and contributors.

Updating the PHPUnit PHAR ...  done


$ php phpunit-4.7.7.phar --version    
PHPUnit 4.8.0 by Sebastian Bergmann and contributors.

[MichaelHindley]

@sebastianbergmann try running self-update again afterwards

[sebastianbergmann]

That is a different (new) issue: #1815.

[MichaelHindley]

Ah ok, thank you for pointing that out, serves me right to get here by google search instead of the issue tracker