News for hackers. Stuff that matters.
Re:SSL and PHP Streams, Part 1 by RobAley on Thursday June 26, 2014 @10:28AM (#7949780)
Again the article is out of date, it's now parsed from the URL if you don't specify a CN_match (which you can still do if you need to).
Re:SSL and PHP Streams, Part 1 by viraptor on Thursday June 26, 2014 @11:09AM (#7950017)
This doesn't matter now. People don't (and sometimes cannot) upgrade quickly. Also, documentation for the latest version still says peer_verify defaults to false and CN_match doesn't mention being computed automatically.

Effectively if you write any code you're not going to deploy yourself, you have to specify the CN_match and verify_peer. Others will not know about the limitations, so this function is messed up until after 5.5 is EOLed.

Designing APIs is hard and bad defaults can hurt for many major versions after they're changed.

Re:SSL and PHP Streams, Part 1 by DaveRandom on Thursday June 26, 2014 @10:54AM (#7949927)
Not before 5.6 (where CN_match is actually deprecated in favour of peer_name)
Re:SSL and PHP Streams, Part 1 by chc on Thursday June 26, 2014 @11:25AM (#7950108)
It is? Which of the versions of PHP linked from the homepage of PHP.net do this? I didn't think any of them did.