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).
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)
"We must also specify the expected peer name on the presented certificate with the `CN_match` option, it will not be inferred from the URL and if it is not specified, the name on the certificate will not be validated."
WTF? Who ever got the idea that this is something that can ever hit production?