Hacker News new | comments | ask | show | jobs | submit login

OK, great! Clicking the main page[1], see the top of README:

"build error".

Wait, what? You just released it, it should definitely work! Clicking that icon[2], checking the failed build[3]:

ERROR: no certificate subject alternative name matches

requested host name `pear.php.net'.

To connect to pear.php.net insecurely, use `--no-check-certificate'.

Really? See what's in http://pear.php.net/

> The server running pear.php.net had a fatal hard disk failure and gets replaced by a new machine this week. Until the new machine is setup, this page is up to let you continue installing PEAR packages via the PEAR installer.

In 2015? Cool.

Connecting to the https website ...

% openssl s_client -connect pear.php.net:443 ... Certificate chain 0 s:/CN=mail.cweiske.de

So you're using CN=mail.cweiske.de for pear.php.net. I don't even know what to say.. Well, happy hacking!

[1]: https://github.com/php/php-src [2]: https://travis-ci.org/php/php-src [3]: https://travis-ci.org/php/php-src/jobs/94372493




They didn't release it. They just tagged it in GitHub. The HN title is wrong.


> In 2015? Cool.

Do you actually think there's a point in time where mechanical hard drives are going to last forever? If so I have a bridge to sell you.


I'd wager it's commentary on the lack of redundancy that would allow such an important resource to be unavailable.

Hard disks fail, but if you're hosting something important on them, you might want more than one (to grossly oversimplify things).


> % openssl s_client -connect pear.php.net:443 ... Certificate chain 0 s:/CN=mail.cweiske.de

>So you're using CN=mail.cweiske.de for pear.php.net. I don't even know what to say.. Well, happy hacking!

Yeah, but it's cool that they used Let's Encrypt.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: